I have a laptop here running XP Pro that can login to the network, process/run login scripts, access the internet, mail servers, shared drives and other various network resources however the laptop in question cannot be pinged, accessed or otherwise be seen on the network (i.e.: \\Laptop\Share$, \\IP.ADD.RE.SS\Share$; ping IP or host = request timed out) The routing tables look fine, it is authenticating as it should, we've tried two different subnets, releasing and renewing the IP, even used a hard coded IP but the machine could not be pinged or otherwise accessed. I thought maybe the TCP/IP stack might've been corrupted some how so I removed all of the protocols and clients for that NIC however TCP/IP would not disappear from the list. I removed the device from device manager and upon Windows reinstalling the device, after a reboot of course, there was no change. Aside from reimaging the machine, what else do you suggest I try.

Disable the windows firewall and any other firewall that may be running on the PC.

There are no firewalls on the machine or snffing/DNE drivers loaded. Does have WiFi and 1394 but disabling both in device manager doesn't help.

Your symptoms are consistent with the firewall on. Are you positive the Windows XP built-in firewall isn't enabled? Soylent Green is PEOPLE!!!

Do NOT disable firewalls. Sheeze. Ping has little to do with anything that you need. Since you can log into the network you KNOW the connection is not only working it is working all the way up the osi model. Diag your authentication, and authorization. Your connection is great! Like you said, you can log in. That by it's self proves the entire network from the Nic to Nic.

Well, OK, you could in some way have it locked down with a firewall. Lemme change that. The solution is not to disable it however.

First off I'd like to say thank you to those brave few who replied; I greatly and sincerely apprecaite everyone's suggestions. The built-in firwall in XP is enabled but not setup to block ICMP & there is no change when we turn it off. This is a very strange problem: If the machine cannot be reached via net use, ping, tracert, \\machine-name\share$ or \\IP\share$ nor are we able to view the event logs remotely etc, how could the network possibly communicate with it? It boggles the mind! Again, the only problem we have is that we are unable to effectively assist the client remotely. When said client has a problem, we cannot remote into their machine or map a drive to copy files (which happens every so often). However, as far as we and the client are concerned, the machine is functioning as it should. Can anyone recommend any additional or third-party tools or tests to better diagnose this problem?