Re: Error testing net for thinclients
fredag 3. desember 2004, 20:08, skrev Gavin McCullagh:
| Hi,
Hi, and I`m sorry my answer to my own thread is late, but I only work on
fridays and have had exams to take care of, but now I am back in business :-)
| [ 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?
Yes.
| > 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?
From ifconfig I get the ip-adresses of both eth1 and eth0, and I pinged both
of them from my own laptop on the same net. I also can use ssh to enter the
server. And I can ping from the server to enywehere else.
Other test I could do? :-)
| > 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:
Yes.
| * 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?)
Yes, there were some problems here, this was the first thing I sorted out, but
this ought to be okay now. Or is there some way to be sure it it (except the
pinging and asking the peole who did this and the man in charge for the net
in this building)?
| > 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?
Yes.
| > 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
My output is:
otto:~# ps aux |grep dhcpd
root 839 0.0 0.1 2556 1492 ? Ss Nov26 0:01 /usr/sbin/
dhcpd3 -q eth0 eth1
and shuold be okay, as far as I understand.
| 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.
Here:
otto:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:02:A5:EC:8E:FF
inet addr:148.83.65.4 Bcast:148.83.0.65 Mask:255.255.255.224
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:146327 errors:0 dropped:0 overruns:0 frame:0
TX packets:157524 errors:0 dropped:0 overruns:0 carrier:10
collisions:28 txqueuelen:1000
RX bytes:16304686 (15.5 MiB) TX bytes:17615460 (16.7 MiB)
Interrupt:21 Base address:0xc000
eth1 Link encap:Ethernet HWaddr 00:02:A5:EC:8F:BB
inet addr:192.168.0.254 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:22 Base address:0xe000
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:54387556 errors:0 dropped:0 overruns:0 frame:0
TX packets:54387556 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3269305093 (3.0 GiB) TX bytes:3269305093 (3.0 GiB)
| 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.
Nothing, not even trying to connect to the DHCP-server.
| > 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.
Well, at least I have not changed anything in the machine, and I doubt anyone
else has. I even tried to use eth1 as thinclient-network, but, as mentioned,
this failed too (as it should), so I think this could not be so.
| > Greetings from AB, Norway
|
| Many happy returns from Dublin, Ireland.
|
| Gavin
:-)
AB
Reply to: