TCP/IP Stack not working

[Jon Miller]

I have a clients W2kP wkstn that as of yesterday the
tcp/ip stack does not work. I have removed and added the
tcp/ip protocol but this does not help. The client
stated they installed some icon editing tool and this
happened. I've checked their add/remove programs and
noticed that they also installed a Cisco VPN client
program. I've uninstalled all programs that were
recently installed and was able to get the computer to
reboot (it was booting and shutting down with a blue
screen) properply. It has only SP3 on it, should I apply
SP4 in hopes that the IP Protocol will repair itself?
There are no viruses on the PC.

Thanks.

 

[Steven L Umbach]

Hi Jon.

Try booting into safe mode with networking to see if it helps. If it does you have a
startup driver/application/service problem that you may be able to track down using
msconfig copied from an XP computer to \winnt\system32. You might also look into
repairing winsock as described in the KB link below. System File Checker running sfc
/scannow may be worth a try, being sure you have a W2K install cd handy. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;817571

 

[Herb Martin]

I have a clients W2kP wkstn that as of yesterday the
tcp/ip stack does not work. I have removed and added the
tcp/ip protocol but this does not help.

How do you know? What are the precise symptoms? (We can assume
we understand what "IP stack not working" means but that would really
be guessing.)

Can you ping 127.0.0.1 successfully?

If you can, then "IP is initiallized and bound to an adapter."

If not, the IP is not initiallized or isn't bound to an adapter?
It might be an adapter problem (driver, hardware etc.)

The client
stated they installed some icon editing tool and this
happened. I've checked their add/remove programs and
noticed that they also installed a Cisco VPN client
program. I've uninstalled all programs that were
recently installed and was able to get the computer to
reboot (it was booting and shutting down with a blue
screen) properply. It has only SP3 on it, should I apply
SP4 in hopes that the IP Protocol will repair itself?
There are no viruses on the PC.

SP4 is not likley to hurt and it's a good idea in almost every case
anyway.

It is more likely a Network DRIVER problem but that is impossible
to say definitively.

What does IPConfig /all show? Are you using a DHCP assigned address
or a manual one?

 

[Jon L. Miller]

After looking at some of the docos on the web I'm am now
able to ping the localhost address (127.0.0.1) and some
of the workstations on my network. I cannot however ping
anything past my gateway, nor can I resolve any locations.
I also cannot get a IP address from a DHCP server. The
IP address is the 169.254.xxx.xxx.
What I did is remove the NIC and all protocols and re-
installed the items.

Jon