On network but can't be ping'd

January 25, 2006 at 06:27:20
Specs: XP Pro w/ SP2, P4 512MB
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.

See More: On network but cant be pingd

Report •

January 25, 2006 at 07:52:40
Disable the windows firewall and any other firewall that may be running on the PC.

Report •

January 25, 2006 at 11:14:25
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.

Report •

January 25, 2006 at 14:25:05
Your symptoms are consistent with the firewall on. Are you positive the Windows XP built-in firewall isn't enabled?

Soylent Green is PEOPLE!!!

Report •

Related Solutions

January 25, 2006 at 15:32:54
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.

Report •

January 25, 2006 at 15:34:37
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.

Report •

January 26, 2006 at 05:42:32
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?

Report •

January 26, 2006 at 14:24:38
I'll apologize for sounding so harsh to my fellow posters firstly.

Secondly, Repost your problem. Add in additional information to include more about the system. For example is it a lan or wan and are there any routers or bridges or maybe even modems involved. Are there smart switches or vlans or any high end network devices.

From your last statement I must assume that you are trying to contact a computer behind a type of home router. Repost exact situation.

Report •

February 7, 2006 at 05:22:39
Additional Information:
Its a Dell D600 laptop running Windows XP Pro with SP2. We have developed our own image for these machines which include various applications. The machine in question connects to a hard-wired LAN which helps answer the following questions: LAN or WAN? Are there any routers or bridges or maybe even modems involved. Are there smart switches or vLANs or any high end network devices.
We do have high end managed switches and routers on the network but even on a basic ad-hoc network (simple DSL router dishing out IP's via DHCP and a built in hub) the machine is not 'visible'. Its on, it does what it needs to do, I can connect to other machines and resources but nothing can connect to it.
As for IP's: It's not using the standard windows-sanity IP address of 169.254.X.X. It gets a real legit IP of 10.x.x.x, 172.[16-31].x.x, 192.168.x.x or whatever it is that it is connected to.
As for the new Microsoft tool (http://support.microsoft.com/kb/832919/en-us) I have not had a chance to load it onto the machine as it is not currently in my posession. Will give that a shot to see if there is something funky loaded on the system which we have not yet identified.

Report •

February 21, 2006 at 03:11:08
I had the same problem, i thought it was a currupt tcp/ip stack , but it turned out to be the firwall that was part of the vpn client had been turned on, Also i found the anti virus package also blocked certain port, so check that too,

If you are intrested the following will allow you to reinstall you tcpip stack

run regedit

delete keys winsock and winsock2 from
local machine/system/currentcontrolset/services

delete winsock and winsock2 keys

go to network properties and install protocol

click have disk and select c:\winnt\inf

select tcpip (not verswion 6 )

install internet protocol tcpip ( not ip6 )


good luck



Report •

Ask Question