Re: Error testing net for thinclients
Hi,
[ I'm cc'ing my reply to the skolelinux administrators group where a few
more people might help out ]
On Fri, 03 Dec 2004, Axel Bojer wrote:
> I have tried to ask this on the norwegian list, but no one seemed to know:
> I am having a Problem with our Skolelinux Server; it simply do not want to
> work over the thinclient net (eth1).
I presume this is server is both a main and thin client server?
> I can ping to it, but the thinclients wont come up.
Do I presume you mean you can ping it from the thin client network not just
from the main network?
> The configuration ought to be OK because I have not changed it and it
> used to just pop up as it should before someone here moved the machine.
The thin client server has been moved? Being very cold about it, I'd say
then that these things could change:
* a different network patch cable is in use
* a different port on the switch is in use (is it definitely on the thin
client network?)
* the network cables have been replugged (possibly swapped around?)
> What I get now is: "searching for server (DHCP)...." And there it stops
> for days, and nothing more happens.
So the thin client gets no answer from the DHCP server. I presume this is
the case for all of your thin clients?
> What I have tried already:
> * Reboot the server and/or the thinclient
> * Try another thinclient
> * The diskettes should be OK too, they are booting.
> * A crossed cable direkt on the server to a client
> * Checked cables (since I can ping, they should be ok anyway though)
> * Ping from the server to some webadress or from another machine
> too eth1 and eth0 - and the connection is OK.
>
> Are there some more things to test?
Perhaps you should check a few things on the server (all of the commands
below should be typed into a command line, eg Konsole).
1. Is the DHCP server actually running? Type the command
ps aux |grep dhcpd
and if it's running you'll get a process like the first one here (you can
ignore the second one which is your command running):
root 24022 0.0 2.4 3120 1140 ? S Nov25 1:11 /usr/sbin/dhcpd3 -q eth1
root 25282 0.0 0.9 1332 424 pts/0 S 18:47 0:00 grep dhcpd
If it's not then something strange has happened with your config. The
reboot would have restarted it so it must have failed to start. Please
send us output of the above.
2. Is the network up on the thin client server? Type the command
/sbin/ifconfig
and send us the full output.
3. What happens if you plug a thin client onto your main network? I know
it sounds a bit silly, but make sure that doesn't work. Make sure neither
you nor the system has the network card roles swapped.
> Some testing tools to error proof that I have forgotten?
> It may be that the answear is very simple, but as of now I can see no more
> things too test. It dos not work, but ought too ...
>
> Some ideas anyone?
I know it sounds a little silly, but the network cards being swapped
strikes me as a possible explanation for much of the above.
> Greetings from AB, Norway
Many happy returns from Dublin, Ireland.
Gavin
Reply to: