Name resolution hassles

[Tosis]

Hey there all,

I've a small problem and I hope someone can point me towards a resolution.
A client brought his PC to me in the hopes that I might be able to help him
out. He had multiple spyware infections (easily cleared up using a variety of
utils) but I'm left with one hassle - the machine can't resolve network names.

If I connect it to my office network the DHCP server fails to allocate it an IP
address;
If I manually allocate an IP address the machine is able to ping 127.0.0.1 as
well as the manual IP;
The system cannot ping localhost, the error message reads "Ping request could
not find host localhost. Please check the name and try again"

The system can ping my workstations / server IP addresses;
It cannot ping their DNS or NetBIOS names, the error message reads "Ping
request could not find host <chosen_target>. Please check the name and try
again"

I can establish network connections to shares and printers on other systems if
I use their IP addresses instead of their names.

It looks to me, in my limited understanding, like some kind of WinSock 2.0
problem. Can anyone make a suggestion where to look for an answer?

Many thanks,
Justin

 

[Robert L [MS-MVP]]

this may help, quoted from http://www.ChicagoTech.net

How to Recover from Winsock2 corruption
To resolve this issue, delete the corrupted registry keys, and then reinstall the TCP/IP protocol.

Step 1: Delete the corrupted registry keys
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. In Registry Editor, locate the following keys, right-click each key, and then click Delete:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
4. When you are prompted to confirm the deletion, click Yes.

Step 2: Install TCP/IP

1. Right-click the network connection, and then click Properties.
2. Click Install.
3. Click Protocol, and then click Add.
4. Click Have Disk.
5. Type C:\Windows\inf, and then click OK.
6. On the list of available protocols, click Internet Protocol (TCP/IP), and then click OK.
7. Restart the computer.


Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
I recommend Brinkster for web hosting!

Hey there all,

I've a small problem and I hope someone can point me towards a resolution.
A client brought his PC to me in the hopes that I might be able to help him
out. He had multiple spyware infections (easily cleared up using a variety of
utils) but I'm left with one hassle - the machine can't resolve network names.

If I connect it to my office network the DHCP server fails to allocate it an IP
address;
If I manually allocate an IP address the machine is able to ping 127.0.0.1 as
well as the manual IP;
The system cannot ping localhost, the error message reads "Ping request could
not find host localhost. Please check the name and try again"

The system can ping my workstations / server IP addresses;
It cannot ping their DNS or NetBIOS names, the error message reads "Ping
request could not find host <chosen_target>. Please check the name and try
again"

I can establish network connections to shares and printers on other systems if
I use their IP addresses instead of their names.

It looks to me, in my limited understanding, like some kind of WinSock 2.0
problem. Can anyone make a suggestion where to look for an answer?

Many thanks,
Justin

 

[Chuck]

Hey there all,

I've a small problem and I hope someone can point me towards a resolution.
A client brought his PC to me in the hopes that I might be able to help him
out. He had multiple spyware infections (easily cleared up using a variety of
utils) but I'm left with one hassle - the machine can't resolve network names.

If I connect it to my office network the DHCP server fails to allocate it an IP
address;
If I manually allocate an IP address the machine is able to ping 127.0.0.1 as
well as the manual IP;
The system cannot ping localhost, the error message reads "Ping request could
not find host localhost. Please check the name and try again"

The system can ping my workstations / server IP addresses;
It cannot ping their DNS or NetBIOS names, the error message reads "Ping
request could not find host <chosen_target>. Please check the name and try
again"

I can establish network connections to shares and printers on other systems if
I use their IP addresses instead of their names.

It looks to me, in my limited understanding, like some kind of WinSock 2.0
problem. Can anyone make a suggestion where to look for an answer?

Many thanks,
Justin

Justin,

This is a common problem after spyware removal.

DNS resolution is affected by the LSP / Winsock subsystem.
http://support.microsoft.com/?id=318584
http://support.microsoft.com/?id=811259

If XP RTM or Service Pack 1:
1. Backup and delete the following registry keys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
2. Reboot.
3. Open the network connections folder, right click your network connection, and
click Properties.
4. Click Install | Protocol | Add.
5. Click "Have Disk...", type "\windows\inf" in the box, and click OK.
6. Click "Internet Protocol (TCP/IP)", then click OK.
7. Reboot.

If XP SP2:
1. Start - Run - "cmd".
2. Type "netsh winsock reset catalog" into the command window.

Give LSP-Fix <http://www.cexx.org/lspfix.htm>, WinsockFix
<http://www.tacktech.com/display.cfm?ttid=257>, or WinsockXPFix
<http://www.spychecker.com/program/winsockxpfix.html> a shot.

If no help yet, reset TCP/IP.
http://support.microsoft.com/?id=299357

Start - Run - "cmd". Type "netsh int ip reset c:\netsh.txt" into the command
window.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.

 

[Tosis]

<snip>

Chuck, Robert,
My thanks for the help

Justin

 

[Chuck]

<snip>

Chuck, Robert,
My thanks for the help

Justin

YW, Justin. Please let us know which item(s) resolve your problems, when you
have resolution.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.