Cannot Ping

[andrew playford]

I am having problems pinging my windowz machine. and my windowz machine has problems pinging my linux box

this is my set up

Windows

192.168.0.1
255.255.255.0
192.168.0.1

Linux

192.168.0.2
255.255.255.0
192.168.0.2

all firewalls are disabled and are allowing icmp. I have had it working a couple of times but now it wont work at all. Its definantly a crossover cable aswell. it is really driving me mad!!

[cuiq]

If someone doesn't offer a quicker answer, you can always have a look here.

http://www.linuxquestions.org/linux/...Small_Home_LAN



Peace V

[beachboy]

another place you can check out is www.dnsstuff.com there you can find out alot of different information on your ip address.

[gtmtnbiker98]

Is the network cable home made? If so, is it wired correctly? If it is commercial, did you buy the right cable? Make sure that the twisted pair is actually opposite on both ends, if not, then it is wired as a straight through.

[AlexK]

@ andrew playford
In your post you had this:
192.168.0.1
255.255.255.0
192.168.0.1

my question is what are these fields, I know one is ip address and the 2nd is netmask, but what is the third?

Also if you are not connecting through a switch or router, make sure you use a crossover cable instead of a normal twisted pair.

[anomie]

A couple other ideas to tack on to this thread:

• The switch/router you're using should allow ICMP echo requests between machines on the network. (Perhaps you can check in the admin tool to see if they're being dropped.)
• What kinds of firewalls? Zone alarm on Windows? An iptables front-end for the Linux box? Both may be dropping ICMP echo requests by default.
• Post the results of

  ifconfig

  for the Linux box, and

  ipconfig

  for the Windows box. Just double check even if you think they're correct.
• Can both boxes ping to the switch/router?

If you have gone through all the physical cable checks, pinging the router succesfully, etc. and still can not ping one another then download and install nmap. Then try from the Linux box:

nmap -P0 windows_ip_here

This will hit it with lots of different requests (not just ICMP echo) and should get a response if one is possible.

[andrew playford]

well this is my result for windows ipconfig

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.


Windows IP Configuration


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 2002:accb:61de:4:913e:e3d1:8ebc:e534

IP Address. . . . . . . . . . . . : 2002:accb:61de:4:211:5bff:fe8f:fe10
IP Address. . . . . . . . . . . . : fec0::4:211:5bff:fe8f:fe10%2
IP Address. . . . . . . . . . . . : fe80::211:5bff:fe8f:fe10%4
Default Gateway . . . . . . . . . : 192.168.0.1

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Autoconfiguration IP Address. . . : 169.254.2.36
Subnet Mask . . . . . . . . . . . : 255.255.0.0
IP Address. . . . . . . . . . . . : fe80::211:f5ff:fe3f:6bad%6
Default Gateway . . . . . . . . . :

PPP adapter AOL ADSL:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 172.203.97.222
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 172.203.97.222

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5
Default Gateway . . . . . . . . . :

Tunnel adapter 6to4 Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 2002:accb:61de::accb:61de
Default Gateway . . . . . . . . . : 2001:620:0:c000::a
2002:c058:6301::c058:6301
2002:836b:213c:1:e0:8f08:f020:8

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.1%2
Default Gateway . . . . . . . . . :

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5efe:172.203.97.222%2
Default Gateway . . . . . . . . . :

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5efe:169.254.2.36%2
Default Gateway . . . . . . . . . :


This is my result for linux box is

eth0 link encap: Ethernet hwaddr 00:30:bd:b6:d2:02
inet addr :192.168.0.2 bcast 192.168.0.255 mask :255.255.255.0
inet6 addr: fe80::bdff:feb6:d202/64 scope:link
up bradcast running multicast mtu :1500 metric:1
RX packets:2 errors:0 dropped:0 overruns:0 fram:0
TX packets :5 errors:0 dropped:0 overruns:0 carrier: 0
collisions:0 txqueuelen:1000
RX bytes:332 (332.0 b) TX bytes:390 (390.0 b)
interupt:10 basic address:0xa000

[anomie]

Ok, so they have ethernet adapters that appear to be on the same network. I would go through the rest of the steps suggested on this thread...

[andrew playford]

well i have managed to get a bit further but now my Windows Machine Crashes when i send a ping request to my linux box and my linux box says Destination Unreacheable when sending a ping request to my Windows Box. Tried all the steps i beleive i have even used a different cable and Network card but still the same response. Any more i deas guy's? i have had this working once.

Thanks for all your help and suggestions.

[mattoid]

your windowz box has the same IP for the gateway; is that going to work, or should it be the IP of the linux nic? They may be doing a loopback kind of thing and looking into their own belly-buttons. so to speak... Try setting the gateways as the IP of the other machine's nic.

Tell me what happens, cos i've got a windoes box that ping the linux one, but not vice-versa.

all in the fun of it!

mattoid