Unable to resolve names

[Carl D]

My Windows XP Pro SP2 desktop recently developed a problem resolving IP
addresses. When I do an nslookup I am able to resolve the address, but
a ping (or web access) cannot find the host. Example:

C:\>ping microsoft.com
Ping request could not find host microsoft.com. Please check the name
and try again.

C:\>nslookup microsoft.com
*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.1

Non-authoritative answer:
Name: microsoft.com
Addresses: 207.46.130.108, 207.46.250.119

My network has a Leviton gateway which serves my 192.168.0.x subnet
with DHCP. There are other devices on the network that can access the
internet (Win XP Home, Win2K, TiVo series 2) and each other.

Enabling or disabling Windows Firewall has no affect on the ability to
resolve names. Stopping and starting the dns cache didn't help, nor
did an ipconfig /flushdns.

My question for the group is what could be going on, and how can I
trace the problem? What log should I enable to look at for clues?
Thanks!

ipconfig /displaydns follows.

Windows IP Configuration



cfdp133

----------------------------------------

Record Name . . . . . : cfdp133

Record Type . . . . . : 1

Time To Live . . . . : 523751

Data Length . . . . . : 4

Section . . . . . . . : Answer

A (Host) Record . . . : 192.168.0.67





1.0.0.127.in-addr.arpa

----------------------------------------

Record Name . . . . . : 1.0.0.127.in-addr.arpa.

Record Type . . . . . : 12

Time To Live . . . . : 523751

Data Length . . . . . : 4

Section . . . . . . . : Answer

PTR Record . . . . . : localhost





1.0.168.192.in-addr.arpa

----------------------------------------

Record Name . . . . . : 1.0.168.192.in-addr.arpa.

Record Type . . . . . : 12

Time To Live . . . . : 523751

Data Length . . . . . : 4

Section . . . . . . . : Answer

PTR Record . . . . . : leviton





67.0.168.192.in-addr.arpa

----------------------------------------

Record Name . . . . . : 67.0.168.192.in-addr.arpa.

Record Type . . . . . : 12

Time To Live . . . . : 523751

Data Length . . . . . : 4

Section . . . . . . . : Answer

PTR Record . . . . . : cfdp133





leviton

----------------------------------------

Record Name . . . . . : leviton

Record Type . . . . . : 1

Time To Live . . . . : 523751

Data Length . . . . . : 4

Section . . . . . . . : Answer

A (Host) Record . . . : 192.168.0.1





localhost

----------------------------------------

Record Name . . . . . : localhost

Record Type . . . . . : 1

Time To Live . . . . : 523751

Data Length . . . . . : 4

Section . . . . . . . : Answer

A (Host) Record . . . : 127.0.0.1

 

[Chuck]

My Windows XP Pro SP2 desktop recently developed a problem resolving IP
addresses. When I do an nslookup I am able to resolve the address, but
a ping (or web access) cannot find the host. Example:

C:\>ping microsoft.com
Ping request could not find host microsoft.com. Please check the name
and try again.

C:\>nslookup microsoft.com
*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.1

Non-authoritative answer:
Name: microsoft.com
Addresses: 207.46.130.108, 207.46.250.119

My network has a Leviton gateway which serves my 192.168.0.x subnet
with DHCP. There are other devices on the network that can access the
internet (Win XP Home, Win2K, TiVo series 2) and each other.

Enabling or disabling Windows Firewall has no affect on the ability to
resolve names. Stopping and starting the dns cache didn't help, nor
did an ipconfig /flushdns.

My question for the group is what could be going on, and how can I
trace the problem? What log should I enable to look at for clues?
Thanks!

ipconfig /displaydns follows.

<SNIP>

First, check for corruption in LSP / Winsock / TCP/IP.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

Will it ping, or browse, by IP address?
# Ping 66.94.230.33.
# Browse 66.94.230.33.
# Report success / exact text of error messages.

 

[Carl D]

Problem solved!

msinfo32 showed me I had some third party sockets (google desktop).
Removing them didn't immediately solve the problem, nor did netsh
winsock reset catalog or uninstall winsock in registry per linked MS
article above (http://support.microsoft.com/?id=811259). However the
WinSock XP Fix (http://www.spychecker.com/program/winsockxpfix.html)
did the trick.

Thanks for pointing me in the right direction.

 

[Chuck]

Problem solved!

msinfo32 showed me I had some third party sockets (google desktop).
Removing them didn't immediately solve the problem, nor did netsh
winsock reset catalog or uninstall winsock in registry per linked MS
article above (http://support.microsoft.com/?id=811259). However the
WinSock XP Fix (http://www.spychecker.com/program/winsockxpfix.html)
did the trick.

Thanks for pointing me in the right direction.

Carl,

Congrats on your persistence. And thanks for the feedback.