Need help with XP PC, DNS names don't resolve, nslookup works

[Guest]

My brother in law has a new clone PC running XP SP2. It uses DHCP over a
wired connection to a LinkSys router, It is receiving an IP address and DNS
servers of his ISP. When I use NsLookup to query names, the ISP DNS server
properly responds with the addresses. I can ping those supplied addresses
successfully. If I try to ping the name directly, the ping fails. Other PCs
on the same network, both wired and wireless, work correctly. Anyone have any
ideas? TIA.

 

[Chuck]

My brother in law has a new clone PC running XP SP2. It uses DHCP over a
wired connection to a LinkSys router, It is receiving an IP address and DNS
servers of his ISP. When I use NsLookup to query names, the ISP DNS server
properly responds with the addresses. I can ping those supplied addresses
successfully. If I try to ping the name directly, the ping fails. Other PCs
on the same network, both wired and wireless, work correctly. Anyone have any
ideas? TIA.

Look at the Node Type, in "ipconfig /all".
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>
http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html

And check to make sure that NetBT is explicitly enabled on all computers.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components

 

[Guest]

Look at the Node Type, in "ipconfig /all".
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>

And check to make sure that NetBT is explicitly enabled on all computers.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>

Chuck, Thanks for the reply. NetBT was enabled, but the problem wasn't that
simple. I learned that the PC was infected previously with spyware and my
nephew who 'cleaned' it told me that he thinks he remembers a message about
the WinSock system being broken. I opened a case with product support and the
ultimate answer was that the TCP/IP protocol stack needed to be reinstalled.
It's a neat trick, considering that you can't remove the protocol and it
doesn't show on the list of protocols to add. Basically, you have to Browse
at that point and point to the INF folder to reload it. It worked like a
charm!

Rick

 

[Chuck]

Chuck, Thanks for the reply. NetBT was enabled, but the problem wasn't that
simple. I learned that the PC was infected previously with spyware and my
nephew who 'cleaned' it told me that he thinks he remembers a message about
the WinSock system being broken. I opened a case with product support and the
ultimate answer was that the TCP/IP protocol stack needed to be reinstalled.
It's a neat trick, considering that you can't remove the protocol and it
doesn't show on the list of protocols to add. Basically, you have to Browse
at that point and point to the INF folder to reload it. It worked like a
charm!

Rick

Thanks for the update, Rick!