A
Andy Fish
Hi,
I have a problem with an XP Pro box with resolving external (fully
qualified) domain names. After leaving the box alone for a while, it seems
that TCP/IP apps can't resolve hostnames via DNS, but nslookup works
correctly. Here's an example:
nslookup www.google.com
==> returns 216.239.59.99
ping 216.239.59.99
==> works OK
ping www.google.com
==> "ping request could not find host www.google.com. Please check the
name and try again"
This is using a PC with several network adapters, all are disabled except
one. The PC is inside a NAT router. releasing and renewing the IP address
does not work; disconnecting and reconnecting the network adapter
occasionally works but usually a reboot is required.
I have looked at the flowchart diagram called "DNS Query Process" on the MS
web site and it seems that for a fully qualified domain name, any name
lookup should go straight to DNS.
Anyone got the foggiest idea what's going on here? - I'm stuck
Andy
I have a problem with an XP Pro box with resolving external (fully
qualified) domain names. After leaving the box alone for a while, it seems
that TCP/IP apps can't resolve hostnames via DNS, but nslookup works
correctly. Here's an example:
nslookup www.google.com
==> returns 216.239.59.99
ping 216.239.59.99
==> works OK
ping www.google.com
==> "ping request could not find host www.google.com. Please check the
name and try again"
This is using a PC with several network adapters, all are disabled except
one. The PC is inside a NAT router. releasing and renewing the IP address
does not work; disconnecting and reconnecting the network adapter
occasionally works but usually a reboot is required.
I have looked at the flowchart diagram called "DNS Query Process" on the MS
web site and it seems that for a fully qualified domain name, any name
lookup should go straight to DNS.
Anyone got the foggiest idea what's going on here? - I'm stuck
Andy