Unsolved

This post is more than 5 years old

11645

November 5th, 2006 09:00

cannot ping the address of another computer on my home network

I have a home network with a Belkin router/dsl modem connected to two PC's.
The router seems to be configured properly, and both PC's are able to access the internet.
The setup of a local network is a problem.
 
I have run Network Setup Wizard on both computers.
Computer A can see shared files on computer B, but computer B cannot see shared files on computer A.
Computer A can ping computer B, but computer B cannot ping computer A ("request timed out").
 
What is the procedure to continue testing to diagnose and correct the local network problem?
 

2 Intern

 • 

14.4K Posts

November 5th, 2006 12:00

sounds like a malconfigured firewall problem to me.

try temporarily disabling both firewalls and see if it then works.

November 5th, 2006 15:00

Even with both firewalls switched off the ping only works in one direction.

2 Intern

 • 

887 Posts

November 5th, 2006 17:00

again, make sure XP firewall is off, any/all software firewalls are off (ZA, etc), anitvirus firewall is off (Norton worm protection etc), Norton Internet Security, McAfee, etc etc. are all off for now.

Make sure file and print sharing is checked on for the network adapters on each pc (wired and wireless). Use the same workgroup name on each pc.

Reboot both and retest.

2 Posts

December 5th, 2006 04:00

I have a very similar problem and would like to know things to try. It is driving me CRAZY!
Turned off firewalls - check
Really turned off firewalls - check
Turned off firewall service on computer A - check
pinged by IP address and by name, same result
replaced Computer A (see intial description) with another computer, problem went away
put back Computer A problem returned
Am going through services and turning them off one at a time.... still no luck
IT guy at work suggested I reformat my HD and reinstall Windows (no kidding!)
 
Like original poster - Running XP SP2 on both systems.
 
Any suggestions appreciated

December 5th, 2006 18:00

My problem is solved in the mean time.
What has happened is the following:
On the computer that could not be reached via the ping procedure, there was also Cisco VPN client software installed with the option "Stateful Firewall (always on)" enabled.
I found in a manual of the Cisco VPN client software that this option enabled the built-in firewall and applied such a strict safety level that "not any inbound session was allowed".
This means that the only communication that works from this computer is communication where the initiative is taken by the computer itself.
A simple request by a network peer for printer access is considered as an inbound session and did not work.
A ping session from this network peer was not answered, but the ping session in the other direction worked fine.
Turning off the option "Stateful Firewall (always on)" made my network work perfectly.
 
It is amazing how many firewalls and hidden firewalls are active in a networked computer!
 
I hope this experience is of any use for you!
 
JM-Belgium

2 Posts

December 17th, 2006 00:00

Jim,
 
That was it! Not only did your advice get my network running, it saved me from reinstallation . Too bad my company IT guy did not know about this (yeah the same one that told me to install the VPN client in the first place and the same one who suggested the cure was to reformat my hard drive). He will now....
 
Thanks!!!
 
Stan
 
 

Top