DHCP and TCP/IP not working

[DH]

My windows xp machine was working fine as a DHCP client
on the network.
At a certain point after a reboot, it stopped working
properly. The DHCP client is not able to get an address
for the machine even though the Ethernet connection is up.



When I try to Ping the router I get the following error:
"Unable to initialize Wondows socket Interface, Error
code 0"

In the Event log:
Dhcp: posted event 1004 - It shut itself down.

Any ideas on how to bring my TCPIP connectivity back?

 

[Mike]

I am having the same problem. I have tried to reload
SP1a. Reinitialize TCP/IP. I am Baffled. Even when I
put in a static IP address it does not use the default
gateway. I am able to Ping address but not use DNS. If I
try to use DHCP it uses the 169.x.x.x class of address.

 

[Guest]

I also tried changing the TCP/IP configuration in
different ways, nothing worked. For some reason the DHCP
and TCP/IP are stuck and will not change back to normal
behaviour.

In my case the machine will not ping itself (127.0.0.1)
which means that the protocol stack is not working.

 

[Ken Wickes [MSFT]]

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\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
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

 

[DH]

Ken,

Thank you for your input.

I found a program which fixes the problem, before I saw
your input.

The program is called "WinsockXPFix" its actions are
similar to your suggestion.

It fixed my problem.

FYI:

I believe my problem was caused during the process of
removing Mcafee 7.0

-----Original Message-----
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\Wins ock

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Wins

ock2
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.

I also tried changing the TCP/IP configuration in
different ways, nothing worked. For some reason the DHCP
and TCP/IP are stuck and will not change back to normal
behaviour.

In my case the machine will not ping itself (127.0.0.1)
which means that the protocol stack is not working. If
I

.