Avatar of harrgo
harrgo
 asked on

Cannot ping from one PC to another on a network - two PC's

I am trying to "fix" a pc for a friend. He has two PC's - one with XP Pro (PCXPPro) and one with XP Home (PCXPHome)

PCXPPro cannot ping PCXPHome and PCXPHome cannot ping PCXPProRO. Both can ping the loopbak (127.0.0.1) and both can ping themselves using their IP addresses (192.168.1.11/12 and 192.168.1.14 respectively.) Both detect when the cable is plugged in and when it is removed

When I connected my laptop to PCXPHomeE the laptop could ping it and PCXPHome could ping my laptop. Thus I know PCXPHome and the cable are both working.

PCXPPRO has supposedly never been conencted to the internet.
PCXPPRO has a network card on the motherboard and a PCI network card. Both NICs have been given a static IP addresses (192.168.1.12 and 192.168.1.12) and a netmask of 255.255.255.0

There is no firewall active on the PCXPPro and the firewall/ics and routing services have been turned off.

I have checked the PCXPPro has all its network components - plus unistalled and reinstalled them, used WINXP Socket fix, LSP, and netshell commands to try to fix the TCP/IP stack.

PCXPPro had no service packs installed when I started this process - and no legal disk so he has purchased XP Pro Service Pack 2 Update Version (he had a legal Windows 98 CD) and done un update install so he is now running a legitimate XPPro Service pack 2. (We did an up date as he no longer has some of his original disks thanks to a partner taking them with her when they broke up)

I have checked for viruses with NOD32, and checked for spyware with Spybot, Adaware and Ewido. Nothing found.

I have checked there are no other firewalls installed using MSCONFIG and a shareware program called Autoruns

Three other strange things
1. Both PC's have the NWLINK protocol installed and the PCXPHome can see the PCXPPro machine in network neighbourhood when that protocol is present. If the NWLINK IPX/SPX is removed it can no longer "see" the other machine.

2. PCXPPro cannot browse the workgroup (both PC has a workgroup of MSHOME - have tried changing it on both PCs but no change to problem) It responds that "you may not have premission to access the workgroup" even though I am logged on as an administrative user (and yes - I tried all these things with a new user as well - same behaviour)

3. The "add/remove" program list for PCXPPro has a large number of entries related to a sound card that have no description and no "REMOVE" button - in fact no button of any kind. In desperation I ran Reg Repair Supreme over it but this did not resolve any of the problems.

I could do a full install and I am sure that would "fix" the problem - but there must be some other way.

Can anyone help - thanks. (Sorry it was so long winded )
Windows Networking

Avatar of undefined
Last Comment
Fatal_Exception

8/22/2022 - Mon
Pete Long

>> (192.168.1.12 and 192.168.1.12)

both IP addresses need to be different change the latter to 192.168.1.13 (same subnet mask)
Pete Long

Networking XP

*****Most Networking Problems with XP*****

Are caused by Firewalls (either hardware or software)
If you have Zone Alarm, Black ICE Defender etc turn them off! If the problem goes away, you need to reconfigure the firewall. Also Windows XP by default has a built in firewall (ICF) to disable
1.  Open Network Connections (Click Start, click Control Panel, and then double click Network Connections.)
 
2.  Click the Dial up, LAN or High–Speed Internet connection that you want to protect, and then, under Network Tasks, click Change settings of this connection.
 
3.  On the Advanced tab, under Internet Connection Firewall, select the following:  Clear the Protect my computer and network by limiting or preventing access to this computer from the Internet check box. This disables the firewall; your computer and network are then vulnerable to intrusions.


*****Full Walkthrough of networking XP Home*****

How to Set Up a Small Network with Windows XP Home Edition (PART 1)
http://support.microsoft.com/default.aspx?kbid=813936
How to Set Up a Small Network with Windows XP Home Edition (PART 2)
http://support.microsoft.com/default.aspx?kbid=813937
How to Set Up a Small Network with Windows XP Home Edition (PART 3)
http://support.microsoft.com/default.aspx?kbid=813938
How to Set Up a Small Network with Windows XP Home Edition (PART 4)
http://support.microsoft.com/default.aspx?kbid=813939
How to Set Up a Small Network with Windows XP Home Edition (PART 5)
http://support.microsoft.com/default.aspx?kbid=813940
How to Set Up a Small Network with Windows XP Home Edition (PART 6)
http://support.microsoft.com/default.aspx?kbid=814003
How to Set Up a Small Network with Windows XP Home Edition (PART 7)
http://support.microsoft.com/default.aspx?kbid=814004
How to Set Up a Small Network with Windows XP Home Edition (PART 8)
http://support.microsoft.com/default.aspx?kbid=814005


Adding XP to a network

http://www.practicallynetworked.com/sharing/xp/addxp.htm

Windows XP Network troubleshooting

http://www.practicallynetworked.com/sharing/troubleshoot/
harrgo

ASKER
Thanks for the feedback so far
Petelong - you got me on a technicality - the two ip address of the two NICs are actually 192.168.1.11 and 192.168.1.12 - not 12.12 in both cases as I wrote - sorry.

However - you missed what I wrote about firewalls. I understand they are the cause of many network problems - bot not as manay as people think. IN this case there is NO firewall running anywhere - not Windows, Black Ice, Zone Alarm, NIS, Kerio, Tiny, Sygate, etc - no firewall period. And as I wrote - i have evened disable the firewall and routing services in Windows and checked what services are running (control panel-administrative tools-services) to make double sure. And I have checked the add remove programs list, and the programs folder to check even further. So
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
harrgo

ASKER
Please ignore the haning "so" on my response - bad typing :(
tim1731

What happen if you connect them via a cross over cable can they ping each other then if so this removes the PCs from the problem as I take it your are plugging them into a seperate router,hub,switch if not you need a cross over cable
harrgo

ASKER
Cable is cross over, no router, hub or switch in the equation. Cable worked between laptop and PCXPHome, but not from PCXPRo to PCXPHome. Have also tried two other cables - same result. Problem is fairly definately software related. Dont forget PCXPHome can "see" PCXPPro in network neighbourhood when using NWlink IPX/SPX but not when using TCP/IP only
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
amit_g

Could you please post the result of ipconfig /all from both XPPro and XPHome? Also What do you have on NetBIOS (enabled/disabled)? Check on both. Follow instructions on http://www.petri.co.il/disable_netbios_in_w2k_xp_2003.htm to see where to check. Do you have "Client for Microsft Network" checked on http://www.petri.co.il/images/w2k_netconfig1.gif ?
harrgo

ASKER
Will have to get ipconfig /all results from friend perhaps tomorrow. Netbios over TCP/IP is enabled on both PC's and so is both Client for Microsoft Network and File and Print Sharing for Microsoft Network.
trenes

It seems like you have a winsock corruption.
http://support.microsoft.com/kb/811259

Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
Fatal_Exception

This comment has  a clue in it:

1. Both PC's have the NWLINK protocol installed and the PCXPHome can see the PCXPPro machine in network neighbourhood when that protocol is present. If the NWLINK IPX/SPX is removed it can no longer "see" the other machine.

Since IPX does not use ARP to resolve MAC addresses (IPX addresses include MAC address information), I would assume that you have a problem with ARP broadcasts..  You could test this by placing a hub in between the PCs, adding your laptop running Ethereal, and watch for the ARP broadcasts and responses...

or

Check your arp cache (arp -a) and see if the MAC addresses are correct for each system, as it should display the connecting ip address and MAC address of the connecting computer...  If this information is not correct, you can statically assign the IPaddress to the correct MAC address using another switch:  arp -s

FE
harrgo

ASKER
THanks for mentioning ARP fatal exception as it was part of the puzzle and you may be on to something. Originally when I clicked on the network icon on PCXPPro and selected repair it would fail with the message cannot clear ARP cache. When I issued (and even now when I issue) an arp -a I am told the arp cache is empty. I turned off the Windows Firewall/Internet Connection Sharing and the Routing and Remote Access service the repair operation would complete. However I am still told the arp is empty. Does this help the diagnosis? It looks like it may be a clue. By the way - I take it the ipconfig is the most reliable way to determine the mac address of the adaptor?
harrgo

ASKER
PS - COuld the ARP cache problem also be casuing/contributing to the fact that I cant "browse" the workgroup on PCXPPro even though I am an administrator and there are shares set with appropriate permissions
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Fatal_Exception

Yes, using IPconfig /all the easiest way to find out the MAC address, as it is hardcoded on the NIC in the firmware..  as long as the card is working, that is..  :)

If you are running an entirely TCP network, you have to have ARP working correctly to resolve the IPaddresses of the devices on your network.,..  One way to see if it is working is to just ping an IPaddress and if successful, then take a look at the ARP cache...  if it is emtpy, then you have a problem...  although, you might find even pinging a remote address is not working due to the same problem..

Try adding a static ARP mapping and see if that allows you to find other resources...  That might help in the short run..  :)

FE
harrgo

ASKER
Please find attached the results of the ipconfig commands

PCXPPro
Windows IP Configuration
   Host Name . . . . . . . . . . . . : obi-3tgrok4mzru
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek RTL8139-810X Family PCI Fast Ethernet NIC
   Physical Address. . . . . . . . . : 00-0D-61-0E-32-57
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.1.12
   Subnet Mask . . . . . . . . . . . : 255.255.255.0

Ethernet adapter Local Area Connection 3:

   Media State                       : Disconnected
   Description . . . . . . . . . . . : D-LINK DFE-528TX PCI Adapter #2
   Physical Address. . . . . . . . . : 00-15-E9-7C-78-22


PCXPHome
Windows IP Configuration
   Host Name . . . . . . . . . . . . : tsunami
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter office:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Nvidia Nforce Networking Controller
   Physical Address. . . . . . . . . : 00-17-31-D9-67-34
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.1.10
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway                  :


I have entered two arp -s commands on PCXPPro to add the static routes for both card
  arp -s 192.168.1.12 00-0d-61-0e-32-57
  arp -s 192.168.1.10 00-17-31-d9-67-34
and confirmed they have been accepted vai and arp -a command on PCXPPro (192.168.1.12)
  arp -a
  Interface : 192.168.1.12 --- 0x10003
  Internet Address           Physical Address        Type
  192.168.1.12                00-0d-61-0e-32-57     Static
  192.168.1.10                00-17-31-d9-67-34     Static

I have then retried the ping from PCXPPro (192.168.1.12) to PCXPHome (192.168.1.12) and again the request times out.

Very strange isnt it :(
Fatal_Exception

You might try installing a different NIC on this system, to rule out bad hardware..  We worked on a similar problem a couple years ago, where a user's system could only connect using IPX..  never did come up with a solution, even though the discussion lasted over a month.. in fact, I think we had to break it into 2 threads it became so long..  :)
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
harrgo

ASKER
Just a quick thanks to all the contributions to date. I am going to try an ipx connection only connection today to see if they can at least talk that way. I have my doubts since the PCXPPro machine cant even access its own workgroup.

In terms of your last suggestion Fatal Exception - I have already install a new NIC (the one on the M/Board was the original and the PCI card I just installed. All tests have been tried using both card after swapping the cable.)

You dont perchance know the identity of the thread you had last year or can tell me how to locate it. Am currently reading everything I can find on "cant ping" but getting a lot of "turned firewall off and it all worked" - which I have already tried.
Fatal_Exception

This was actually a question asked by one of our top experts, before he fell ill, and could not post anymore..  we don't see him much, and always wish him well..  Crazyone..

https://www.experts-exchange.com/Operating_Systems/WinXP/Q_20834306.html

As you read down through his problem, you will find a lot of talk about IPX, although it was not until last year that I had to learn the deep secrets of IPX, since this is the standard we use at my company..

FE
harrgo

ASKER
PS - I dont like to display my ignorance but if I change the systems over to IPX/SPX, is there an equivalent to ping? (That uses mac addresses perhaps)
If I do find I can see everything using IPX/SPX then would all my fellow experts agree that this indicates TCP/IP is "broken" in some way - eg registry/dll? And if a WinSockFix and in place install doesn't fix it - what the heck would? Since microsoft says all the info on TCP/IP is in a limited area in the registry could I just copy all those keys from another working version of XPPro? Can I "force" windows to do a reinstall of XP - and I mean a real rinstall - like from scratch?
Am I being too simple minded here - or am I loosing my mind. Always thought of myself as pretty good with networks - at least the simple stuff - but this has me VERY confused :)
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Fatal_Exception

Ping will work with both IPX and TCP installed...  no worry there..

and yes, it does appear that it is broken..  if you have SP2 installed, you need to use the netsh command to rebuild the Winsock, instead of just relying on WinsockFix...  but I see you already tried this by your original question...

http://support.microsoft.com/kb/299357/

Never tried copying the registry keys...  Instead, since I can reload a system in a couple hours with all applications, I just wipe and reinstall...  :)  
harrgo

ASKER
Yeh - and I expect this is going to be the only solution here but - the guy is missing quite a number of application disks thanks to a messy personal break up. And not your every day stuff either - programs for music manipulation. Oh well - merrily we roll along. :) Keep the suggestions coming guys
johnb6767

Instead of only resetting teh winsock, try resetting the TCPIP stack in whole...

netsh interface ip reset c:\resetlog.txt

Netsh is a cool tool, can do a lot with it...I doubt this will eb a solve all to your problem though, just saw the reference to netsh above, and wanted to add...
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
harrgo

ASKER
OK - problems is resolved - but not solved.
Part of the problem is that I made some assumptions and they turned out not to be correct. You might note above that I connected my laptop to the new comptuer PCXPHome and could ping to that machine and get responses, and it could ping my laptop and get responses. So I "assumed" the problem was with the old PC. Just to be thorough I connected the laptop to the old pc PCXPPro yesterday via same crossover cable and would you believe it - it could ping my laptop, I could ping it from my laptop and I could brouse the network and access shares. Swapped cable to new PC PCXPHome and verified I could still ping it from my laptop and it could still ping my laptop. Yep - all go. Connect cable between two PC's PCXPPro and PCXPHome - no pinging between PCXPPro and PCXPHome. Tried another cable - crossover - same result. So I got a router, connected all 3 PC's and set all TCP/IP setting to "Obtain an IP Address Automatically". PCXPPro and laptop got addresses - PCXPHome did not get one - ended up with a 169 address. So - looks like the problem is with PCXPHome after all. Ran WinSock fix on it - no change. Deleted network card from system, redetected, and hooray - all is working fine. Pinging and browsing of network shares - all perfect. Removed the router, reset the static IP address mentioned above, reconnected the cross over cable and all still working. Friend it happy - netowkr works but I am still puzzled.
Can anyone suggest how both PC could ping to and recieve pings from my laptop (running XP Pro SP2) but would not ping each other?
Sorry that my assumption sent us all in the wrong direction - I wont make that mistake again. But would really like to understand what happened.
Thansk for all the help. I will allocate the points when I have a plausable explaination of how this could happen.
ASKER CERTIFIED SOLUTION
Fatal_Exception

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question