B
Brian Foster
I've been managing networks for over five years, but I've come across
something that's got me baffled.
I have a Windows XP machine (SP2) on a workgroup network of 4
computers. This one computer cannot ping anything else (including the
default gateway), and cannot be pinged from any other machine on the
network. This causes problems for applications I run on the machine
that rely on ICMP to test for the presence of particular machines. But
the wierd thing is that except for pinging, XP's device manager
reports the network card functioning correctly, the machine in
question has full internet connectivity, and it can be found if you
put its name or IP address directly into a run box e.g.
\\192.168.1.101\c$
Some more info:
On the machine in question Ping itself works, because the machine can
ping 127.0.0.1 and it's own IP address but cannot see the gateway
192.168.1.1 to which it is connected by Ethernet (a Linksys WRT54g).
I've confirmed it's not the cabling or the router setup, because
connecting another machine to the same ethernet cable and hub port
works, and when I do that, the new machine connected by the same cable
can indeed ping the router and other machines.
All wireless machines on the network can also ping the router via
Wireless. So it's just this one computer that's driving me nuts.
Here's what I've tried:
* Releasing and getting a new IP address from the router (a DHCP
server). No effect.
* Forcing a manual IP address. No effect.
* Changing the ethernet cable. No effect.
* Changing the network card, to one that's been known to work on the
same network. No effect.
* Reinstalling the network card drivers.
* Opening firstly the ICMP and then all ports on the machine's SP2
firewall, and then even including disabling the entire firewall. No
effect.
* Running a netsh int reset to reset the protocol. No effect.
* Turning off the router's firewall. No effect.
Any ideas? Am I looking at reinstalling the TCPIP files off the SP2
CD? Or a full reinstall? Suggestions welcomed!
something that's got me baffled.
I have a Windows XP machine (SP2) on a workgroup network of 4
computers. This one computer cannot ping anything else (including the
default gateway), and cannot be pinged from any other machine on the
network. This causes problems for applications I run on the machine
that rely on ICMP to test for the presence of particular machines. But
the wierd thing is that except for pinging, XP's device manager
reports the network card functioning correctly, the machine in
question has full internet connectivity, and it can be found if you
put its name or IP address directly into a run box e.g.
\\192.168.1.101\c$
Some more info:
On the machine in question Ping itself works, because the machine can
ping 127.0.0.1 and it's own IP address but cannot see the gateway
192.168.1.1 to which it is connected by Ethernet (a Linksys WRT54g).
I've confirmed it's not the cabling or the router setup, because
connecting another machine to the same ethernet cable and hub port
works, and when I do that, the new machine connected by the same cable
can indeed ping the router and other machines.
All wireless machines on the network can also ping the router via
Wireless. So it's just this one computer that's driving me nuts.
Here's what I've tried:
* Releasing and getting a new IP address from the router (a DHCP
server). No effect.
* Forcing a manual IP address. No effect.
* Changing the ethernet cable. No effect.
* Changing the network card, to one that's been known to work on the
same network. No effect.
* Reinstalling the network card drivers.
* Opening firstly the ICMP and then all ports on the machine's SP2
firewall, and then even including disabling the entire firewall. No
effect.
* Running a netsh int reset to reset the protocol. No effect.
* Turning off the router's firewall. No effect.
Any ideas? Am I looking at reinstalling the TCPIP files off the SP2
CD? Or a full reinstall? Suggestions welcomed!