Can't Ping Linux CentOS 5.3 Machine to XP SP2 Windows Machine

Moderns · 10-31-2009, 04:37 PM

Dear Mates,

I have two machines, one has XP service pack2, second one has CentOS 5.3 (Linux), they are connected through crossover cable.

I have configured everything fine but don't know why till now can't ping!

A. Windows machine settings as follows:

IP Address: 192.168.1.3
Subnet Mask: 255.255.255.0
Default Gatway: 192.168.1.1
+ Firewall is turned OFF.

B. For Linux machine, I will list everything stored in network files, logged as [root@localhost ~]# :

1. /etc/sysconfig/network:

ifconfig eth0 192.168.1.4 netmask 255.255.255.0 up
route add -net 192.168.1.0 netmask 255.255.255.0 eth0
route add default gw 192.168.1.1 eth0
NETWORKING = yes
NETWORKING_IPV6=no
HOSTNAME=localhost.localdomain

2. /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE="eth0"
IPADDR="192.168.1.4"
NETMASK="255.255.255.0"
ONBOOT="yes"
BOOTPROTO="yes"

3. /etc/resolv.conf

nameserver 192.168.1.4
search locadomain

4. I restarted network service using this command:

/etc/init.d/network start

everything is fine.

When checking using ifconfig command.

I get the following:

eth0 Link encap: Ethernet HWaddr 00:08:0D:EE:19:66
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr:........
UP BROADCAST RUNNING......
RX....
TX....
collisions:0........
RX bytes:0 (0.0 b) TX bytes:......

lo Link encap: Local Loopback
inet addr: 127.0.0.1 Mask:255.0.0.0
inet6 addr:........
UP LOOPBACK RUNNING......
RX....
TX....
collisions:0........
RX bytes:0 (0.0 b) TX bytes:......

I mean I assigned the IP: 192.168.1.4 to Linux machine (Eth0).

I did everything above and can't ping till now, when pinging from windows or Linux I get a message "destination host unreachable" restarted Linux many times but same result. NETWORK CABLE is working fine I tested it.

Please advise me.

Thanks guys.

Moderns · 10-31-2009, 05:50 PM

CentOS 5.3 commands are similar to Redhat commands.

I hope to find answer soon here, waiting you.

Thanks.

bathory · 11-01-2009, 09:35 AM

In case of 2 computers connected through a crossover cable you don't need a gateway and specifically in your case, you have defined a gateway (192.168.1.1) that is not reachable by any of the 2 boxes.
If you want, you can set each gateway to the ip of the specific box, but leaving it blank it's not going to do any harm either.

Regards

dxqcanada · 11-01-2009, 09:41 AM

Try running this

Code:

# mii-tool -v

If you have this utility it will show you if there is an active link

Moderns · 11-01-2009, 03:58 PM

Quote:

Originally Posted by bathory

In case of 2 computers connected through a crossover cable you don't need a gateway and specifically in your case, you have defined a gateway (192.168.1.1) that is not reachable by any of the 2 boxes.
If you want, you can set each gateway to the ip of the specific box, but leaving it blank it's not going to do any harm either.

Regards

I removed this line: "route add default gw 192.168.1.1 eth0" from the file: /etc/sysconfig/network.

I can't ping from windows to Linux

even from Linux to windows can't.

Moderns · 11-01-2009, 04:03 PM

Quote:

Originally Posted by dxqcanada

Try running this

Code:

# mii-tool -v

If you have this utility it will show you if there is an active link

Yes this utility is working with me and I got positive results..

eth0: negotiated 100baseTx-FD flow-control, link ok
product info: vendor....
.
.
.
.

Moderns · 11-01-2009, 11:35 PM

Also I removed this line: "route add -net 192.168.1.0 netmask 255.255.255.0 eth0" from the file: /etc/sysconfig/network.

It doesn't work yet!

AdnanShaheen · 11-02-2009, 12:26 AM

Use the trace route from windows (tracert) to Linux (traceroute) and vice versa. Post the result, may be that help any one.

If you can not ping, you must not be able to trace the route as well. Most important thing about CentOS is its security. Also check if you are allowed to ping to/from your Linux

Moderns · 11-02-2009, 12:54 AM

Quote:

Originally Posted by AdnanShaheen

Use the trace route from windows (tracert) to Linux (traceroute) and vice versa. Post the result, may be that help any one.

If you can not ping, you must not be able to trace the route as well. Most important thing about CentOS is its security. Also check if you are allowed to ping to/from your Linux

Thanks Adnan, I will check tracert 192.168.1.4 (linux IP) and traceroute 192.168.1.3 (windows IP) and will post results here when I go to home as I am at work now.

Also I will check pinging from / to Linux and will inform you when I reach.

Many thanks.

culaterout · 11-02-2009, 01:13 AM

Look first disconnect your Internet connection... From your router or other wise your router is going to try and send it out over the Internet... Since this is more then likely not a Cisco router... Just a cheap cable router its not going to recognise the local account and send it out over the world wide web.... No Cable company is going to give direct access to there network..

Moderns · 11-02-2009, 01:25 AM

Quote:

Originally Posted by culaterout

Look first disconnect your Internet connection... From your router or other wise your router is going to try and send it out over the Internet... Since this is more then likely not a Cisco router... Just a cheap cable router its not going to recognise the local account and send it out over the world wide web.... No Cable company is going to give direct access to there network..

Thanks Culaterout for your comment.

Actually I was pinging from windows while connecting wireless to internet, will this cause problem? only I have crossover cable connecting both laptops.

Thanks.

Moderns · 11-02-2009, 01:28 AM

Please if I have any mistakes in network files let me know.

culaterout · 11-02-2009, 02:36 AM

Quote:

Originally Posted by Moderns

Thanks Culaterout for your comment.

Actually I was pinging from windows while connecting wireless to internet, will this cause problem? only I have crossover cable connecting both laptops.

Thanks.

No problem related...Ops sometimes I forget we have wireless???

Not a very secure measure is wireless so I stay away from it... Seeing

how I log into my bank account via internet...

later

Moderns · 11-02-2009, 04:49 AM

Quote:

Originally Posted by culaterout

No problem related...Ops sometimes I forget we have wireless???

Not a very secure measure is wireless so I stay away from it... Seeing

how I log into my bank account via internet...

later

Actually I didn't get you, by the way, when I go to home after 3 hours, I will check solutions suggested by mates above and will report it here.

Thanks.

Moderns · 11-02-2009, 09:17 AM

Quote:

Originally Posted by AdnanShaheen

Use the trace route from windows (tracert) to Linux (traceroute) and vice versa. Post the result, may be that help any one.

If you can not ping, you must not be able to trace the route as well. Most important thing about CentOS is its security. Also check if you are allowed to ping to/from your Linux

for Linux: the command will be in bold color

[root@localhost ~]# traceroute 192.168.1.3 //windows ip
traceroute to 192.168.1.3 (192.168.1.3) 30 hops max, 40 byte packets
1 (192.168.1.4) 2999.519 ms !H 2999.490 ms !H 2999.456 ms !H

[root@localhost ~]# traceroute 192.168.1.4 // linux ip
traceroute to 192.168.1.4 (192.168.1.4) 30 hops max, 40 byte packets
1 (192.168.1.4) 0.083 ms 0.021 ms 0.019 ms

Also I can ping Linux IP address 192.168.1.4

[root@localhost ~]# ping 192.168.1.4
64 bytes from 192.168.1.4: icmp_seq=1 ttl=64 time=0.051 ms
64 bytes from 192.168.1.4: icmp_seq=2 ttl=64 time=0.053 ms
64 bytes from 192.168.1.4: icmp_seq=3 ttl=64 time=0.051 ms
64 bytes from 192.168.1.4: icmp_seq=4 ttl=64 time=0.052 ms
64 bytes from 192.168.1.4: icmp_seq=5 ttl=64 time=0.049 ms
64 bytes from 192.168.1.4: icmp_seq=6 ttl=64 time=0.051 ms
.
.
.
.
.

Also I can ping in windows to same windows IP 192.168.1.3