ping failed, but arp cache contains the right resolution

[Guest]

Hi!

I'm just networking 2 pcs. I just want to share directories from one to the
other.
I set what needed first in the Local Area Properties dialog box (File and
Printer sharing) and subsequent TCPIP Properties dialog boxes (DHCP obtained
address from a router, disable LMHOSTS lookup, default NetBIOS setting), and
second in the Share and Security dialog box for directories. No Windows
firewall, Kerio is off. When i try to map on B (192.168.0.2) a network drive
from A (192.168.0.1), everything is ok, i can write file on the remote
machine. But mapping on A from B doesnt work at all. Always getting "...
network path not found".
I check all what can be checked, but unsuccessfully.
When pinging A from B, it's ok, pinging B from A always ends in "Request
Timed Out". What i dont understand is why the arp cache on A contains the
right entry, even if i flush it before pinging :

192.168.0.2 00-12-79-cd-4c-3a dynamic

Anyone can help me ?

 

[Guest]

I forgot to say that A runs WinXP SP2 and B runs WinXP SP1.

 

[Ron Lowe]

Hi!

I'm just networking 2 pcs. I just want to share directories from one to
the
other.
I set what needed first in the Local Area Properties dialog box (File and
Printer sharing) and subsequent TCPIP Properties dialog boxes (DHCP
obtained
address from a router, disable LMHOSTS lookup, default NetBIOS setting),
and
second in the Share and Security dialog box for directories. No Windows
firewall, Kerio is off. When i try to map on B (192.168.0.2) a network
drive
from A (192.168.0.1), everything is ok, i can write file on the remote
machine. But mapping on A from B doesnt work at all. Always getting "...
network path not found".
I check all what can be checked, but unsuccessfully.
When pinging A from B, it's ok, pinging B from A always ends in "Request
Timed Out". What i dont understand is why the arp cache on A contains the
right entry, even if i flush it before pinging :

192.168.0.2 00-12-79-cd-4c-3a dynamic

Anyone can help me ?

I'm 99.99999999% certain this is a firewall problem on the unpingable
machine.
No, I'll re-consider that. I'm 100% sure

It's common for a machine running a host-based firewall to respond to ARP
requests, but then block any TCP / UDP / ICMP traffic.

Try un-installing, rather than disabling, any firewalls.
Often, these don't disable very cleanly.

Also, be aware that firewalls are sometimes hidden in other software, for
example VPN clients usually have a firewall component in them.