Cannot ping localhost

[Guest]

I have a small office network with 2 win2k operating systems and one XP
systems connected through a linksys router. The XP system will not recognize
the win 2k systems as part of the workgroup. While troubleshooting, I tried
to ping localhost for all systems. One win2k and the XP system ping
localhost fine. The other win2k system will not ping local host.

I uninstalled tcpip on the problem machine. After reinstalling, ping local
host works OK UNTIL I reboot the computer. After rebooting, the machine will
not ping localhost. What is going on?

 

[Lanwench [MVP - Exchange]]

I have a small office network with 2 win2k operating systems and one
XP systems connected through a linksys router. The XP system will not
recognize the win 2k systems as part of the workgroup. While
troubleshooting, I tried to ping localhost for all systems. One
win2k and the XP system ping localhost fine. The other win2k system
will not ping local host.

I uninstalled tcpip on the problem machine. After reinstalling, ping
local host works OK UNTIL I reboot the computer. After rebooting, the
machine will not ping localhost. What is going on?

Check your event logs for errors. TCP/IP is having problems - also check
your hosts file (by default, in c:\winnt\system32\drivers\etc) to make sure
localhost is still in there....can you ping 127.0.0.1 all the time even when
localhost fails?

 

[Guest]

Thank you for your post.

I repeated the process, uninstall tcpip, reboot, reinstall tcpip,
test ping localhost (OK),
Test ping 127.0.0.1, (OK)
Test ping router (OK),
test ping local client at 192.168.1.103 (OK) By local client I mean the
other win2k system;
then rebooted,
test ping local host (fail, timeout),
test ping 127.0.0.1 (fail, timeout),
test ping router (ok),
test ping local client at 192.168.1.103 (ok).
Checked local host file. The file is there and appears to be ok. In notepad
the local host is listed with address 127.0.0.1

Checked event log. No errors after the reboot.

However, earlier event recorded a warning: "The browser was unable to
retrieve a list of servers from the browser master \\E2-2 on the network
\Device\Nbf_{B478C3E1-F229-490A-9617-E77629920EAD}. The data is the error
code."
This was followed by an error: "The browser service has failed to retrieve
the backup list too many times on transport
\Device\Nbf_{B478C3E1-F229-490A-9617-E77629920EAD}. The backup browser is
stopping. "
TCPIP was uninstalled when these errors were logged, so I think these errors
were the result of trying to re-connect to a mapped share on E2-2 without
TCPIP.

 

[Herb Martin]

Thank you for your post.

I repeated the process, uninstall tcpip, reboot, reinstall tcpip,
test ping localhost (OK),
Test ping 127.0.0.1, (OK)

If you cannot ping 127.0.0.1 this means that IP is
did not initialize and bind to at least one adapter.

Reasons include corrupted stack (but that is uncommon
and you have already re-installed), failed adapters
(total failure, not just failure to communicate), and
duplicate IP address.

The last is the most common, easiest to cause and
easiest to fix so focus there first.

Anything that prevents the NIC from working or
that prevents IP from initializing causes this AND
if IP initializes and binds to an adapter you won't
see this problem.

Type IPConfig /all and post it here.

Look in Device Manager and make sure all of
your NIC adapters are working, without error.

 

[Guest]

Type IPConfig /all and post it here.
Look in Device Manager and make sure all of
your NIC adapters are working, without error

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : e2-1
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI TX
NIC
(3C905B-TX) #2
Physical Address. . . . . . . . . : 00-50-04-67-66-47
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 24.116.212.232
24.116.0.202
Lease Obtained. . . . . . . . . . : Tuesday, December 21, 2004
10:36:18
AM
Lease Expires . . . . . . . . . . : Thursday, December 23, 2004
10:36:18
AM

Also, Device Manager shows all devices working properly.

 

[Herb Martin]

And are you saying you cannot ping either 192.168.1.100
nor 127.0.0.1 FROM this same machine while it shows
this IPConfig?

When a machine shows such an IP then you almost have
to be able to ping itself.

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : e2-1
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI TX
NIC
(3C905B-TX) #2
Physical Address. . . . . . . . . : 00-50-04-67-66-47
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 24.116.212.232
24.116.0.202
Lease Obtained. . . . . . . . . . : Tuesday, December 21, 2004
10:36:18
AM
Lease Expires . . . . . . . . . . : Thursday, December 23, 2004
10:36:18
AM

Also, Device Manager shows all devices working properly.

 

[Guest]

Herb, thanks again for your post.

That is exactly the problem, I tried it all again just now, to make sure I
am not losing it.

Please note in my original post that it all works fine after reinstalling
TCPIP, that is until I reboot. Something is happening in boot to
disable/alter/or otherwise mess up the default TCPIP settings. So I suspect a
rogue registry value somewhere, but I do not know registry architecture well
enough to even know if I am making a valid guess.

If you come up with something, let me know.

 

[Guest]

OK, The plot thickens. I disabled Norton Antivirus and re-booted. I can
ping localhost, 127.0.0.1, and 192.168.1.100. It works fine until Noton
Antivirus/Internet protection is turned on. I quess turning off Norton should
have been the first thing.....

So, could norton be interfering with my attempts to network with XP? All
three machines have Norton antivirus/internet protection running. I will play
around and see.

Please let this thread die, and I will post a new thread regarding my other
problems.

Thanks again.

 

[Herb Martin]

Herb, thanks again for your post.

That is exactly the problem, I tried it all again just now, to make sure I
am not losing it.

Please note in my original post that it all works fine after reinstalling
TCPIP, that is until I reboot. Something is happening in boot to
disable/alter/or otherwise mess up the default TCPIP settings. So I suspect a
rogue registry value somewhere, but I do not know registry architecture well
enough to even know if I am making a valid guess.

If you come up with something, let me know.

Well then next time try those things before the reboot
to see which of them is true during the problem manifestation....

 

[Herb Martin]

OK, The plot thickens. I disabled Norton Antivirus and re-booted. I can
ping localhost, 127.0.0.1, and 192.168.1.100. It works fine until Noton
Antivirus/Internet protection is turned on. I quess turning off Norton should
have been the first thing.....

We sort of assumed that you didn't have any
firewall software running locally.

Generally you want to EXCEPT the local
addresses from such restrictions, maybe
even except some or all of the machines on
the same subnet for services you trust.