Re: Error testing net for thinclients

[Axel Bojer <axelb@skolelinux.no>]

mandag 13. desember 2004, 23:57, skrev Finn-Arne Johansen:
> On Mon, Dec 13, 2004 at 10:22:48PM +0100, Axel Bojer wrote:
> > fredag 10. desember 2004, 18:55, skrev Gavin McCullagh:
>
> Alot have been written, And I gave up following this thread. okay,
> seems like you still have problems, so I'll give it a shot.
>
> First, try to locate which NIC is eth0 and which is eth1.
>
> Normally, with new nics, you do get a message on the console when you
> disconnects the cable. check this first.
>
> using mii-tool and ethtool may also help you
>
> if this wont help, check led's on the nic and the switch. check that it
> actually lights up when connecting the cable.
>
> Using a crossed cable and a laptop also helps, when debugging networks.
>
> when you've located eth0, make sure you hav a connection to the default
> gateway, and if you uses dynamic ip on eth0, getting an ip adress from
> a dhcp server, make sure you get this.
>
> when you have found made sure which card is eth0, and hopefully have
> made a connection there, you may start start working on eth1, and the
> connection to the thin clients.
>
> Then, when you've made sure that the cables are working, you may start
> using tcpdump.

Yes, you are right! Wednesday night I double-checked everything physical and 
joined a thin client directly on the server, just 
to eliminate possible errors. And, voila, two faults was found:

* One cable I inserted was changed out by someone, and the new one did not 
work. I found the culprit (cable), and of course changed it.
A bit more embarrising though:
* There is an unused network plug on the server, I though I had tested wich 
one was the right, but, well, obviously not good enough.

So thank you all for all input,
now I am glad it finally works!

Conclusion: Double-checking pays off :-)

All the best
Axel.