can't ping other PCs on LAN

[simke]

G'day. I encounter this problem with Open Suse
10.2. I need your help & advice.
Can't seem to ping other PCs on LAN. I attached here
the output from command prompt:

linux-m2al:~ # ifconfig
eth0 Link encap:Ethernet HWaddr
00:19:21:34:97:31
inet addr:192.168.0.2 Bcast:192.168.0.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500
Metric:1
RX packets:969 errors:0 dropped:0 overruns:0
frame:0
TX packets:21 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:1000
RX bytes:252461 (246.5 Kb) TX bytes:1630
(1.5 Kb)
Interrupt:177 Base address:0xc800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0
frame:0
TX packets:9 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:0
RX bytes:919 (919.0 b) TX bytes:919 (919.0
b)

linux-m2al:~ # ifstatus eth0
eth0 device: VIA Technologies, Inc. VT6102
[Rhine-II] (rev 7
eth0 configuration: eth-bus-pci-0000:00:12.0
eth0 is up
2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc
pfifo_fast qlen 1000
link/ether 00:19:21:34:97:31 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.2/24 brd 192.168.0.255 scope global
eth0
eth0 IP address: 192.168.0.2/24
Configured routes for interface eth0:
default 192.168.0.1 - -
169.254.0.0 - 255.255.0.0 eth0
Active routes for interface eth0:
192.168.0.0/24 proto kernel scope link src
192.168.0.2
169.254.0.0/16 scope link
default via 192.168.0.1
1 of 2 configured routes for interface eth0 up
linux-m2al:~ # iptables -F
linux-m2al:~ # iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination


Chain FORWARD (policy ACCEPT)
target prot opt source destination


Chain OUTPUT (policy ACCEPT)
target prot opt source destination

linux-m2al:~ # ping -c 4 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.2: icmp_seq=2 Destination Host
Unreachable
From 192.168.0.2 icmp_seq=2 Destination Host
Unreachable
From 192.168.0.2 icmp_seq=3 Destination Host
Unreachable
From 192.168.0.2 icmp_seq=4 Destination Host
Unreachable

--- 192.168.0.1 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100%
packet loss, time 3003ms
, pipe 3
linux-m2al:~ # ping -c 4 192.168.0.100
PING 192.168.0.100 (192.168.0.100) 56(84) bytes of
data.
From 192.168.0.2: icmp_seq=1 Destination Host
Unreachable
From 192.168.0.2 icmp_seq=1 Destination Host
Unreachable
From 192.168.0.2 icmp_seq=2 Destination Host
Unreachable
From 192.168.0.2 icmp_seq=3 Destination Host
Unreachable

--- 192.168.0.100 ping statistics ---
3 packets transmitted, 0 received, +4 errors, 100%
packet loss, time 2008ms
, pipe 3
linux-m2al:~ # ping -c 4 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.2: icmp_seq=1 Destination Host
Unreachable
From 192.168.0.2 icmp_seq=1 Destination Host
Unreachable
From 192.168.0.2 icmp_seq=2 Destination Host
Unreachable
From 192.168.0.2 icmp_seq=3 Destination Host
Unreachable

--- 192.168.0.1 ping statistics ---
3 packets transmitted, 0 received, +4 errors, 100%
packet loss, time 2010ms
, pipe 3
linux-m2al:~ # ping -c 4 192.168.0.199
PING 192.168.0.199 (192.168.0.199) 56(84) bytes of
data.
From 192.168.0.2: icmp_seq=2 Destination Host
Unreachable
From 192.168.0.2 icmp_seq=2 Destination Host
Unreachable
From 192.168.0.2 icmp_seq=3 Destination Host
Unreachable
From 192.168.0.2 icmp_seq=4 Destination Host
Unreachable

--- 192.168.0.199 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100%
packet loss, time 2999ms
, pipe 3
linux-m2al:~ # ping -c 4 192.168.0.3
PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.

--- 192.168.0.3 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss,
time 3008ms

linux-m2al:~ # ping -c 4 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.

--- 192.168.0.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss,
time 3000ms

linux-m2al:~ # ping -c 4 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2000
ms

--- 192.168.0.1 ping statistics ---
4 packets transmitted, 1 received, 75% packet loss,
time 3009ms
rtt min/avg/max/mdev =
2000.146/2000.146/2000.146/0.000 ms, pipe 3
linux-m2al:~ #

Thank you.

[robshan]

have you looked at the network security settings on the hosts that you are trying to ping??

there is possible firewall issues.

check that you have allowed connections from the IP ranges of the network hosts or allow ICMP pings

[simke]

Thank you for your post robshan. The host firewall setting is ok, other PCs (Windows & Fedora) on the LAN can ping without problem. Apart from iptables, is there any other security config file(s) that I should be aware of in Suse?
Thanks.

[simke]

I think it's the mother board chipset issue here! Biostar (S775) P4M800 Pro-M7 with VIA chipset! Can't seem to find any Linux support info for it on the Net! Does anyone have any idea?
Thanks.

[swerdna]

Have you tried with Suse firewall off? Suse firewall will block samba by default. Quick check is to turn off then ping.

Swerdna

[simke]

Have you tried with Suse firewall off? Suse firewall will block samba by default. Quick check is to turn off then ping.

Swerdna

G'day Swerdna, thank you for your reply. As you can see in my command prompt output list attached in my original 1st post:

[/QUOTE]
linux-m2al:~ # iptables -F
linux-m2al:~ # iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination


Chain FORWARD (policy ACCEPT)
target prot opt source destination


Chain OUTPUT (policy ACCEPT)
target prot opt source destination

linux-m2al:~ # ping -c 4 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.2: icmp_seq=2 Destination Host
Unreachable
From 192.168.0.2 icmp_seq=2 Destination Host
Unreachable
From 192.168.0.2 icmp_seq=3 Destination Host
Unreachable
From 192.168.0.2 icmp_seq=4 Destination Host
Unreachable

--- 192.168.0.1 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100%
packet loss, time 3003ms
, pipe 3
[/QUOTE]

I had the firewall set off then ping but...

[simke]

Yep, it was the Biostar motherboard that caused the problem!
Changed to an Intel motherboard & solved the problem. I just wanna share this info with everyone, that's all. Thanks.