Ping problem

[Guest]

I have two XP-SP2 pc's networked. I've had them networkd wireless, wired,
combination, and through two different LinkSys routers. Even with firewall
disabled, including shutting down the Firewall & ICS service the same result
holds true. One PC is in a workgroup, the other is part of a domain that is
not available on this network. I've been at this for a good 20 hours trying
all sorts of things to no avail. IP has been checked, rechecked etc. Here's
what happens:
I can ping the GW from both PC's. I can ping external addresses (yahoo.com,
etc). The PC at address 192.168.1.101 can ping and receives a reply from the
PC at address 192.168.1.102. The reverse doesn't work however. Using arp -
a I can see that the .102 PC has the correct mac of the .101 PC after
replying to its echo request. Still, from 102 I cannot ping 101. Note that
the 101 PC is the PC in the domain, although I don't think it matters... On
the domain we can ping anything/everything.

--Mark

 

[Steve Winograd [MVP]]

I have two XP-SP2 pc's networked. I've had them networkd wireless, wired,
combination, and through two different LinkSys routers. Even with firewall
disabled, including shutting down the Firewall & ICS service the same result
holds true. One PC is in a workgroup, the other is part of a domain that is
not available on this network. I've been at this for a good 20 hours trying
all sorts of things to no avail. IP has been checked, rechecked etc. Here's
what happens:
I can ping the GW from both PC's. I can ping external addresses (yahoo.com,
etc). The PC at address 192.168.1.101 can ping and receives a reply from the
PC at address 192.168.1.102. The reverse doesn't work however. Using arp -
a I can see that the .102 PC has the correct mac of the .101 PC after
replying to its echo request. Still, from 102 I cannot ping 101. Note that
the 101 PC is the PC in the domain, although I don't think it matters... On
the domain we can ping anything/everything.

--Mark

Domain vs. workgroup membership has nothing to do with pinging a
computer using its IP address.

Domain vs. workgroup membership could affect pinging a computer using
its computer name. If the domain computer only uses DNS or WINS for
name resolution, it wouldn't be able to resolve computer names in a
workgroup.

If the domain computer can ping the workgroup computer by IP address
but not by computer name, it's a name resolution problem.

Otherwise, it's likely that a firewall on the PC at address
192.168.1.101 is blocking pings from the other computer.

Don't shut down the Firewall and ICS service manually. Enable the
service, and use the GUI interface to disable XP's built-in firewall.

Un-install all other firewall programs (ZoneAlarm, Norton Internet
Security, etc) while troubleshooting. Run Msconfig, go to the Startup
tab, and disable any firewall remnants (e.g. ZA's TrueVector) that the
un-install procedure might have left behind.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Guest]

Hi,
the TCP/IP PING command will not work on XP sp2 computes without first
telling the computer to accept incoming echo request.

To do this, navigate to network connection's properties page, from the
advanced tab select settings, then click on ICMP tab, then check "Allow
incoming echo request" accept with OK then close all property sheets and try
to ping again.