Re-Installing TCP/IP

[Information]

I have a machine that will not receive an IP from any router.

It was setup in one location with a DLink router...IP address was 0.0.0.0
Tried a repair, and recieved :

The following steps of the repair operation failed
Renewing the IP Address
Refreshing all DHCP leases and re-registering DNS names
Please contact your network admin...

We have moved the machine to aonther location, and it does not get an IP
address from a Netgear router.

Here is the list of everything we have currently tried

1) Confirmed TCP/IP is set to auto-assign for both address and DNS.
Disabled Windows Firewall.
2) Recovered from Winsock corruption (KB811259) article.
3) Installed 2nd NIC, 1st is integrated, and same issues.
4) Uninstalled Norton Internet Security 2007 and rebooted.
5) Repair install of Windows XP Home. It put it back to SP1, but I figured
it would cleanse the palette. Same issues.
6) Reset TCP/IP in Win XP (KB299357)

Looking for suggestions to resolve this short of saving data and
reformatting.

Any assistance is truly appreciated.

Dan

 

[Chuck]

I have a machine that will not receive an IP from any router.

It was setup in one location with a DLink router...IP address was 0.0.0.0
Tried a repair, and recieved :

The following steps of the repair operation failed
Renewing the IP Address
Refreshing all DHCP leases and re-registering DNS names
Please contact your network admin...

We have moved the machine to aonther location, and it does not get an IP
address from a Netgear router.

Here is the list of everything we have currently tried

1) Confirmed TCP/IP is set to auto-assign for both address and DNS.
Disabled Windows Firewall.
2) Recovered from Winsock corruption (KB811259) article.
3) Installed 2nd NIC, 1st is integrated, and same issues.
4) Uninstalled Norton Internet Security 2007 and rebooted.
5) Repair install of Windows XP Home. It put it back to SP1, but I figured
it would cleanse the palette. Same issues.
6) Reset TCP/IP in Win XP (KB299357)

Looking for suggestions to resolve this short of saving data and
reformatting.

Any assistance is truly appreciated.

Dan

Dan,

I'd repeat step 2, deeper. The "netsh reset" instruction is one of 5 possible
solutions to an LSP / Winsock problem, and none of them are 100% more effective
than the others.
<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

And have you checked router settings? I just finished a session with a guy in
another forum, where he finally came back with "I just checked MAC address
filtering on the router, and the problem is now solved.". DOHH.

 

[Information]

I have acquired some of the utilities and will attempt.

As far as the router is concerned, we have tried two, and each work for the
other computers on their network, just not the culprit.

Thanks for the quick response, and we'll begin using the utilities.

Dan

 

[Information]

I have tried all that apply to Windows XP SP1. Still in the same boat.

The netsh winsock reset catalog must not be available in SP1.

 

[AJR]

Question - Is windows assigning a private address?

 

[Information]

No, I cannot get any address, just:

The following steps of the repair operation failed
Renewing the IP Address
Refreshing all DHCP leases and re-registering DNS names
Please contact your network admin...

If I manually assign wih an acceptable IP, I still get nowhere.

 

[AJR]

Can you ping the computer - ping 127.0.0.1 or localhost? No results - no
TCP/IP. I do not recall in your post that you "reinstalled" TCP/IP.
Other than that I cannot help much.

 

[Chuck]

I have tried all that apply to Windows XP SP1. Still in the same boat.

The netsh winsock reset catalog must not be available in SP1.

No, "netsh winsock reset catalog" is not available in SP1. Did you actually try
all of the other tools though? Did any make any changes? If any tools make any
changes, then you have to repeat all other tools again. Sometimes, one tool
will fix one problem, and another problem may become visible.

And did you check the router, and MAC address filtering? Does the router have
the most current firmware?
<http://nitecruzr.blogspot.com/2005/05/dealing-with-physical-network-problems.html>
http://nitecruzr.blogspot.com/2005/05/dealing-with-physical-network-problems.html