One machine connects to all others, one is selective...

[andycrofts]

Hi
Bit of a weird one that's got me stumped.
OK. Network setup - 4 machines.
1) LORDI. 2 NIC's - one ppp to internet, one for lan 192.168.0.1. Gateway, and minor stuff (DHCP, et. al.) CentOS 4. Usually runlevel 3, unless I need KDE for CD/DVD burn.
2) AWA. 192.168.0.1. Centos 4, runs runlevel 3, Apache (oululife.com), FTP, torrent. 192.168.0.100.
3) NIMBUS. Laptop, SuSE 10.2. Dhcp'd - gets 192.168.0.34 from LORDI. Desktop use.
4) KITA. Suse 10.2. Dhcp'd - gets 192.168.0.31 from LORDI. Desktop use (to replace NIMBUS when ths is sorted)
All connected by a cheap hub. Connected to LORDI's second NIC. Cheap, but reliable. Bought in a tobacconist shop (!!) in Beijing.

Problem: using terminal from NIMBUS, I can SSH - not as root, I've disabled root login - to LORDI or AWA at leisure (ssh 192.168.0.1 or --100). Fine.
BUT, from KITA. I can only ssh to LORDI direct (--1). If I try AWA (--100) I get 'no route to host'...most of the time. From LODI I can then conect to AWA OK.
Occasionally, I have ssh'd to AWA direct.
Cables swapped, but max. length 5 metres (most of the rest are 0.5 metres). NIC in KITA is new, but I haven't a replacement to try...

-Any clues? It's driving me nuts!!! (Using IP addy's not hostnames at all times)
-Thanks
-Andy

[andycrofts]

Rebuilt entire network (neater, only physical changes, no software modifications) with new data cables throughout.
Damn thing works now.
But, things that go away by themselves can come back by themselves.....
-Weird!
I'm betting one of the cables was 'iffy' - maybe bad earth connection, or something. They're in the trash now.
Worth trying for 'network oddities' I guess.
-Andy