Computer is on the Network, but is not pingable

I have a computer that I need to remotely administer. The computer can get to all network resources, and is functioning just fine as far as the user is concerned. When I try to connect to the computer via pcAnywhere or Remote Desktop, I receive the error "the client could not connect to the remote computer".  When I ping the computer by name or by IP, I get request timed out. I made sure the Microsoft Firewall was turned off. Any help would be appreciated.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Fatal_ExceptionSystems EngineerCommented:
Well, we need a little more information..  Is this client on the same LAN?  If there are routers between you and the client, you need to port forward 3389 to that PC's IPAddress...  

So, what is your network like?
jrstxAuthor Commented:
The client is on the same LAN, and there are many other clients on the same LAN as well. The are not routers in between me and the client. The clients here are Windows XP Sp1 and Sp2.

Try changing the IP address of the client computer. Als: make sure the NIC and the switch port it terminates to use the same methods for connection (100/full, automatic negotiation, etc. ).


Become a Microsoft Certified Solutions Expert

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

any other firewalls enabled at all on the box? if not try a reset

netsh int ip reset c:\reset.txt
Fatal_ExceptionSystems EngineerCommented:
Can any other client ping this computer?  Got to be something stopping the ICMP packets...  perhaps resetting the stack may help (Jay)..  but it sure appears like a firewall stopping this connection..
i would agree :)
Just in case, Win XP has its builtin firewall enabled by default and ICMP (pings) are automatically blocked, to unblock

go to the Win XP box and ...

Go to START > Control Panel > Network Connections > your active NIC > Properties > Advance > Windows Firewall > Settings >* Advance, choose "Allow Incoming ECHO Request".  Click OK, OK, OK, etc until you are back at the desktop

*Note see in the General Tab radio button for Firewall is ON by default

jrstxAuthor Commented:
Windows Firewall is turned off, but I will try these other suggestions later this morning, and report back. Thanks for taking the time!
Steve AgnewSr. Systems EngineerCommented:
What are the IP addresses of the machines and check the subnet mask.. if the subnet mask got put in wrong then it can cause responses to go to the default gateway and it would act like this. (if using DHCP then this probably isn't a solution as DHCP is automatic)
then biggest question becomes what is preventing you from connecting and at the same time permits a user to 'see normal operations' from the user perspective.

A side question becomes: if the user PC is assumed to be a known good PC, can the user RDP or remote in using PCAny?

jrstxAuthor Commented:
Ok, before I answer any more of the questions I found that this computer did at one time have Black Ice installed on it. It has been uninstalled, so I am not sure what version or much more details than that. Is it possible Black Ice didn't completely uninstall, or made some changes that didn't revert back to the pre-blackice state? Thanks
Fatal_ExceptionSystems EngineerCommented:
Yes, it very well could have broken the stack...  Have seen this with a variety of products, including Norton and McAfee Security....  As I just  mentioned in another thread, I know of NO LAN administrator that would allow something like this on their networks...

Did you try resetting the stack as Jay mentioned above?
jrstxAuthor Commented:
First I tried giving it a static ip address (different than what DHCP was issuing), and that didn't work. I then tried resetting the stack, and that didn't fix it either. I rebooted the machine, but before I did I ran ping -t
As the computer was coming back up I started getting replies, so I thought the problem was fixed. As soon as I logged in, it began
timing out again. I wanted to make sure there wasn't something wrong with my profile, so I tried it again with the local admin account.
Same symptoms, request timed out.  I also deleted the NIC, and reinstalled it to no avail. Would it be worth installing Service Pack 2?
Steve AgnewSr. Systems EngineerCommented:
Sounds more like a tcp/ip configuration issue than anything else.. remember that networking like ping and the like have abs. nothing to do with windows permissions...

Steve AgnewSr. Systems EngineerCommented:
I would take a look at your running services as well and check the windows event log (system & application) mostly and see if you are logging any types of errors..
jrstxAuthor Commented:
I just booted up in safe mode with networking, and after logging in, I am getting replies. I don't know what this means, but thought it might be good information.
Fatal_ExceptionSystems EngineerCommented:
you are getting Ping replies?  Safemode on what system?  If you logged in on your client that is trying to RDP to the remote system, then something else is causing the problem..  can you RDP to any other remote client out there?  Try using msconfig to turn off everything that starts at bootup, and see if you can get anywhere..

jrstxAuthor Commented:
I put the troubled client in safemode and I am then able to ping it. I didn't try to remote desktop into it, because the user needed to leave for the weekend. I'll resume Monday.  Thanks
I did see one thread with a command to reset the firewall,

"any other firewalls enabled at all on the box? if not try a reset

netsh int ip reset c:\reset.txt"
That justs resets the TCPIP stack, not the firewall...

netsh firewall reset

resets the firewall in the stack...
Fatal_ExceptionSystems EngineerCommented:
Yea, if you can ping the remote client while it is in safe mode, but not when fully booted, there is something lingering in there stopping ICMP and RDP..  Try to reset the firewall with John's command first, but I wonder if Black Ice seriously broke something on it..
Steve AgnewSr. Systems EngineerCommented:
I'd look for running services .. stop the windows firewall service and any other antivirus/firewall services (including Black Ice) if it still shows up.. if something tried to uninstall but doesn't.. often it will still show up in services (that's how it starts) and you can stop it and disable it from there.  Safe mode doesn't run any 'extra' services that windows doesn't need and would suggest that this could be your problem..

It could be something broken, but if there were the case, I wouldn't think safe mode would make it work.. but possible.. just unlikely.
jrstxAuthor Commented:
Resolved by reinstalling the OS. Thanks for your efforts anyway.
Do I need to close this thread, and if so, how?

- John
PAQed with points refunded (500)

EE Admin

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
We had this EXACT same problem, every symptom:

Computer can hit email and file servers
Computer can access internet (we use a proxy server)
Computer gets IP leases, but is not pingable
Continuous ping replies when computer first boots into Windows, but drops off after about 10 replies.

We fixed this by turning off the Stateful Firewall in the Cisco VPN Client.
jrstxAuthor Commented:
Wow! That is very interesting. Where were you two and a half years ago? J/K
We used to use Cisco VPN Client, but I was not aware of it's firewall being on. This was the only machine we had this problem on, and Cisco was installed on a dozen others. The end-user was one of those "knows enough to be dangerous" types around a PC. Thanks for the info. Can hopefully save someone else from banging head against wall.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.