Sorry about the delay, i've been busy with a few things. Anyway heres the info:
eth0 Link encap:Ethernet HWaddr 00:00:E8:8B:7E:66
inet addr:192.168.3.200 Bcast:192.168.3.255 Mask:255.255.252.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:691566 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:7 Base address:0xf000
eth1 Link encap:Ethernet HWaddr 00:90:27:73:DB:FC
inet addr:10.0.40.2 Bcast:10.0.41.255 Mask:255.255.254.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:64 errors:0 dropped:0 overruns:0 frame:0
TX packets:33 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:1386 (1.3 Kb) Interrupt:5 Base address:0x1060 Memory:fa104000-fa104038
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:205 errors:0 dropped:0 overruns:0 frame:0 TX packets:205 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:20696 (20.2 Kb) TX bytes:20696 (20.2 Kb)
All that's really needed is the ip address, netmask and broadcast. The rest simply serves to confuse. (No point listing lo either.)
PING 192.168.3.200 (192.168.3.200) from 192.168.3.200 : 56(84) bytes of data. 64 bytes from 192.168.3.200: icmp_seq=1 ttl=255 time=0.180 ms 64 bytes from 192.168.3.200: icmp_seq=2 ttl=255 time=0.113 ms 64 bytes from 192.168.3.200: icmp_seq=3 ttl=255 time=0.115 ms 64 bytes from 192.168.3.200: icmp_seq=4 ttl=255 time=0.114 ms 64 bytes from 192.168.3.200: icmp_seq=5 ttl=255 time=0.117 ms 64 bytes from 192.168.3.200: icmp_seq=6 ttl=255 time=0.118 ms
There is little point with this, since it will use the loopback interface anyway.
PING 192.168.3.201 (192.168.3.201) from 192.168.3.200 : 56(84) bytes of data.
From 192.168.3.200: icmp_seq=1 Destination Host Unreachable From 192.168.3.200 icmp_seq=1 Destination Host Unreachable From 192.168.3.200 icmp_seq=2 Destination Host Unreachable From 192.168.3.200 icmp_seq=3 Destination Host Unreachable From 192.168.3.200 icmp_seq=4 Destination Host Unreachable From 192.168.3.200 icmp_seq=5 Destination Host Unreachable
PING 10.0.40.2 (10.0.40.2) from 10.0.40.2 : 56(84) bytes of data. 64 bytes from 10.0.40.2: icmp_seq=1 ttl=255 time=0.137 ms 64 bytes from 10.0.40.2: icmp_seq=2 ttl=255 time=0.119 ms 64 bytes from 10.0.40.2: icmp_seq=3 ttl=255 time=0.113 ms 64 bytes from 10.0.40.2: icmp_seq=4 ttl=255 time=0.115 ms 64 bytes from 10.0.40.2: icmp_seq=5 ttl=255 time=0.117 ms
Ditto
PING 10.0.40.1 (10.0.40.1) from 10.0.40.2 : 56(84) bytes of data.
From 10.0.40.2: icmp_seq=1 Destination Host Unreachable From 10.0.40.2 icmp_seq=1 Destination Host Unreachable From 10.0.40.2 icmp_seq=2 Destination Host Unreachable From 10.0.40.2 icmp_seq=3 Destination Host Unreachable
Kernal IP Routing Table
Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.40.0 0.0.0.0 255.255.254.0 U 0 0 0 eth1 192.168.0.0 0.0.0.0 255.255.252.0 U 0 0 0 eth0 0.0.0.0 10.0.40.1 0.0.0.0 UG 0 0 0 eth1
Presumably 192.168.0.0/255.255.252.0 and 10.0.40.0/255.255.254.0 are physically separate ethernet segments. You are absolutly sure you have the leads the right way around? Try the pings to 192.168.3.201 and 10.0.40.1 with the leads swapped. Also if possible try pinging from 10.3.40.1 to 10.3.40.2 and from 192.168.3.200 to 192.168.3.201 -- Mark Evans St. Peter's CofE High School Phone: +44 1392 204764 X109 Fax: +44 1392 204763