IP Stack Problems

  • Thread starter Thread starter Dan
  • Start date Start date
D

Dan

I did a virus sweep on a XP Home system and removed a ras
dialer virus and eventually the new.com process from. In
the process I seem to have broken the DHCP / DNS
functionality.

I have both a wireless connection and when I drag cable
thru the house a hardwired connection. With the wireless
I can see the access point and status shows that packets
are actually being exchanged. If I use dhcp, packets go
outbound but none come inbound. If I use a static ip I
get bi-directional packet exchange. In this mode I can
ping the router and other locations on the Internet.

I have repeated process with hardwired connection to rule
out wireless or nic issues. Other systems use the router
in dhcp mode without a problem, so I am confident the
issue lies on the possessed box.

If I try to telnet to the router, I get a resource
error. If I try to ping to a domain address, I get a
name lookup failure.

I have re-installed XP (using upgrade path), re service
packed it and nothing has changed. I have done a netsh
ip reset and nothing changed.

Short of wiping the box clean and starting over, which I
am hesitant to do because it means dealing with the SONY
restore procedure, I am at a loss as to whats wrong. The
System File Checker says that all the microsoft files are
valid.

Spybot and McAfee both show the box is clean.

The XP firewall is turned off. I have tried this with
Zonealarm Pro on and off and it doesn't make a difference.

Any thoughts?
 
Another thread contained the following response by Ken
Wickes:



I have traced several of these problems to improperly
configured winsock
LSPs. Run "winmsd" and go to
Components/Network/Protocol. Look at the
names in the list, anything with "MSAFD" in it or
the "RSVP xxx Service
Provider" should be fine. Anything else is suspect, and
uninstalling the
owning program might help.
If that fails or your provider list is empty, you may need
to rebuild the
catalog from scratch. The following instructions will
rebuild your catalog
for TCP/IP. If you are using any other transports (If you
don't know, then
you probably aren't) then you will have to reinstall them
as well.

1. Backup and delete the following registry keys
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsoc
k
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsoc
k2
2. Reboot
3. Go to the network connections folder, right click the
icon for your
network connection, and select properties.
4. Click install, choose "protocol", and click "add..."
5. Click "Have Disk...", enter "\windows\inf", click OK
6. Select "Internet Protocol (TCP/IP), click OK
7. When the process in complete, reboot



--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and
confers no rights.



This corrected the problem I was having. Turns out that
new.net stores some packed data in this particular
registry key and if the software behind it has been
deleted causes the problem.
 
Back
Top