Unable to connect to DA server from client

• Saturday, December 08, 2012 7:15 PM

   

   
  

  0

  Below are details:-

  RED: Corporate connectivity is not working.
  Windows is unable to resolve corporate network names.  Please contact your administrator if this problem persists.
  8/12/2012 19:2:42 (UTC)

  
  Probes List
  PASS  PING: 2002:405a:eb12::405a:eb10
  FAIL  HTTP: http://xyx.com

  DTE List
  PASS  PING: 2002:405a:eb12::405a:eb10
  PASS  PING: 2002:405a:eb12::405a:eb13

  Tunnel adapter iphttpsinterface:

     Connection-specific DNS Suffix  . :
     Description . . . . . . . . . . . : iphttpsinterface
     Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
     DHCP Enabled. . . . . . . . . . . : No
     Autoconfiguration Enabled . . . . : Yes
     IPv6 Address. . . . . . . . . . . : 2002:405a:eb13:8100:29d0:421:7315:78ba(Preferred)
     Temporary IPv6 Address. . . . . . : 2002:405a:eb13:8100:4007:111:9fa6:79ef(Preferred)
     Link-local IPv6 Address . . . . . : fe80::29d0:421:7315:78ba%32(Preferred)
     Default Gateway . . . . . . . . . : fe80::8497:a9cf:65c6:4ad3%32
     NetBIOS over Tcpip. . . . . . . . : Disabled

  
  Name Resolution Policy Table Options
  --------------------------------------------------------------------

  Query Failure Behavior                : Always fall back to LLMNR and NetBIOS
                                          if the name does not exist in DNS or
                                          if the DNS servers are unreachable
                                          when on a private network

  Query Resolution Behavior             : Resolve only IPv6 addresses for names

  Network Location Behavior             : Never use Direct Access settings

  Machine Location                      : Outside corporate network

  Direct Access Settings                : Configured and Disabled

  DNSSEC Settings                       : Not Configured

  • Reply
  • Quote