Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SYS A can ping SYS B - SYS B cannot ping SYS A 2

Status
Not open for further replies.

spear1head

Technical User
Sep 17, 2009
3
US
I have a two PC wired home network using a Linksys WRT54g V5 as my router. The OS on both systems is Windows XP SP 3. The router firmware is at the latest level V1.02.7. The router DHCP Table lists both systems. Both systems can connect with the internet thru the WRT54g OK.

The problem is the systems cannot share in both directions. System A (IP 192.168.1.107) can ping System B (IP 192.168.1.108), but System B cannot ping System A. NWlink NetBIOS and NWLink IPX/SPX/NetBIOS Compatable Transport Protocol are installed on both systems. The Windows Firewall is set "OFF" on both systems.

I called Linksys and they stated it was a Windows XP problem.
 
Is it all file sharing attempts or just ping that is the trouble?

If it is just ping, open the Windows Firewall, in the 'Advanced' tab of the Firewall, use the ICMP Settings box to enable ICMP echo requests.

Have you Shared files available on both computers?

Can you connect via "Safe Mode with Networking"?

How to troubleshoot TCP/IP connectivity with Windows XP

How to troubleshoot network connectivity problems

How to determine and recover from Winsock2 corruption

WinXP Connectivity Issues
faq779-4625

Some "funnies" over the last few months have involved the Bonjour Service from Itunes, and also certain Nvidia Network Cards. Many Anti Virus packages have hidden firewall included within too.

A Hidden Personal Firewall - The nVidia nForce Network Adapter
 
1. Try another cable...

2. make sure that SysA&B can ping the LinkSys...

3. then check again if SysA can ping SysB (from above it would seem that all is OK with SysA)...

4. then check if SysB can ping SysA, if that still does not work then give SysB a STATIC IP in the same network IP range and subnet mask, then try again...


Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"
 
-The problem is both ping and file sharing.
-ICMP is checked
-disk drives on both systems are set for sharing.
-Here's where it gets mysterious.
I set SYS A in safe mode in my user name and tried it - it failed.
I set SYS B in safe mode in my user name and tried it - it failed.
I set both systems in safe mode in my user name and it failed.
I set each system, separately in safe mode in Administrator account and they failed.
I shut down both systems and booted the systems in standard separately and tried it - it WORKED?????
I again shut down both systems and booted and it worked. I am able to see drives on both systems from the other and transfer files between them.
 
Just clarifying that Safe Mode is not suitable to test with, it must be "Safe Mode with Networking".
 
File Sharing turned on (ALLOWED EXCEPTIONS) in Firewall along with ICMP as suggested earlier - VERIFY.

Try turning both firewalls off and reboot to see if that makes a difference. Rule out the firewall by doing this.
 
Linney, Sorry I omitted that I did use "Safe Mode with Networking", as you suggested.

I also verified that all the Connection Protocols and Services were the same in both systems. They are:
Client for Microsoft Networks
File & Print Sharing for Microsoft Networks
QoS Packet Scheduling
Microsoft TCP/IP ver 6
NWLink NetBIOS
NWlink IPX/SPX NetBIOS Compatability Transport Protocol
AEGIS protocol (IEEE802.1x) v3.4.3.0
Internet Protocol (TCP/IP)

BigBadBen, In my initial tests with "pinging", I was able to ping the Linksys WRT54g (IP 192.168.1.1) from both systems. I also have a Linksys NAS200 Network Storage unit attached, via Cat5e, from the WRT54g and was able to ping it (IP 192.168.1.100) from both systems. Using the WRT54g's DHCP table I was able to verify that the IP addresses were all in range and working. Note: I didn't need the sledgehammer.

Goombawaho, I did testing with the "Firewalls" turned ON/OFF, with IMCP, on both systems and still had the failure. I left the Firewalls "OFF".

Using "Safe Mode with Networking" I still had failures, as stated above. That's all I did that was different. When I shut down the systems, ie: Power OFF, and re-booted in "Standard" mode everything worked in both systems, in both directions. (???) I added a third system "C" and it joined the network immediately. (???)

Evidentially using "Safe Mode with Networking" set or reset something.

My conclusions: The problem (?) was in System "A". And Microsoft OS works in mysterious ways.

Thanks for the help.

Case Closed!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top