ping 127.0.0.1 works. ping 192.168.0.1 (actual IP number) doesn't work.

[wrreisen]

Hi,

I have 2 XP SP2 professional computers (A and B)connected by a 20m long
cat5 cross over cable. Machine A can ping 127.0.0.1 but it can't ping
its 192.168.0.1 (actual IP address checked with IPCONFIG). What does
this point to. When I plug the two together it is reported that a
100Mbps network has started on machine A. When A tries to ping machine
B's I remember it working. I tried to map a network drive from A to B
and B to A it doesn't work. I try pinging A from B it says request
timed out. I thought I had disabled the firewall on the network
connection on both computers. On B it passed all the network diagnostic
checks from XP help. On A it failed the 192.168.0.1 part.

What can you advise please? Might it be the cable?

 

[N. Miller]

Hi,

I have 2 XP SP2 professional computers (A and B)connected by a 20m long
cat5 cross over cable. Machine A can ping 127.0.0.1 but it can't ping
its 192.168.0.1 (actual IP address checked with IPCONFIG). What does
this point to. When I plug the two together it is reported that a
100Mbps network has started on machine A. When A tries to ping machine
B's I remember it working. I tried to map a network drive from A to B
and B to A it doesn't work. I try pinging A from B it says request
timed out. I thought I had disabled the firewall on the network
connection on both computers. On B it passed all the network diagnostic
checks from XP help. On A it failed the 192.168.0.1 part.

What can you advise please? Might it be the cable?

It might be the cable. For computer to computer on Ethernet you need a
special cable called a "cross over" cable; regular patch cables won't work.

 

[Chuck]

Hi,

I have 2 XP SP2 professional computers (A and B)connected by a 20m long
cat5 cross over cable. Machine A can ping 127.0.0.1 but it can't ping
its 192.168.0.1 (actual IP address checked with IPCONFIG). What does
this point to. When I plug the two together it is reported that a
100Mbps network has started on machine A. When A tries to ping machine
B's I remember it working. I tried to map a network drive from A to B
and B to A it doesn't work. I try pinging A from B it says request
timed out. I thought I had disabled the firewall on the network
connection on both computers. On B it passed all the network diagnostic
checks from XP help. On A it failed the 192.168.0.1 part.

What can you advise please? Might it be the cable?

If Computer A is reporting a network connection, when you plug in the cable,
then I'd look elsewhere. Can Computer B ping Computer A successfully?

I'd look for the firewall (which one did you disable?), and for registry setting
restrictanonymous.
Misconfigured / non-disabled firewalls:
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
Registry setting restrictanonymous:
<http://nitecruzr.blogspot.com/2005/07/restrictanonymous-and-your-server.html>

 

[Himanshu]

no your cable is right, bcz u r able to ping A machine from B. Check
the A machine, try to uninstall lan card driver & re-install it.
127.0.0.1 is Loopback ip, checks the internal connectivity, tell me one
thing what do u get the messege when u try to ping machine A (might be
destination host un-reachble), If u will change ur Lan card I am sure u
will get the perfect solution.
Reagrds,
Himanshu

 

[wrreisen]

Thanks for your replies. I will try and apply your wisdom this Saturday
when I'm with those machines again!

Machine B can't ping machine A for some reason. The message was
"request timed out". I thought I had disabled the built in Windows XP
firewall on machine B and disabled the same firewall on A for the only
connection that shows up in the network connections dialogue (The LAN
connection). Machine A has AOL dialup modem software on it as well
(which works) But the dialup connection doesn't show up in the Network
Connections windows. The cable is a cat5 cross over cable not a patch
cable that has been in the cupboard for a few years but always worked
fine before that.

 

[wrreisen]

Thanks. Machine A had a Norton Internet Security on it with a firewall
I didn't know about. I just allowed the Norton Firewall a range of
network addresses access to this machine. Its now fine. Thank you.

 

[Chuck]

Thanks. Machine A had a Norton Internet Security on it with a firewall
I didn't know about. I just allowed the Norton Firewall a range of
network addresses access to this machine. Its now fine. Thank you.

Thanks for the update.