It is normal for the thin clients to "count down" on the DHCP assigned IP addresses on my installation of Edubuntu (not sure why!) I believe Gavin was referring to two cards on the client machines, not on the server which is, of course, requires two. I've seen this kind of problem when there is more than one DHCP server on the network. You don't have any other computers on this 10.0.0.0 network do you? Make sure the switch your using is not connected to some other network switch. No matter what, the "tcpdump" scan that Gavin recommends you run on your server should be helpful in diagnosing this problem. Have you had any luck running that?
On 5/6/07, Ted Moore <[EMAIL PROTECTED]> wrote:
Thanks for your reply. I could not get any responses using the chatroom. I am using two network cards; one to the school setup and the other to the outside world. My outside world address is 192.168.0.100 and my school setup uses dhcp 10.0.0.20 - 10.0.0.250. When my thin clients do connect they all seem to be starting at 10.0.0.250 and counting down. Does that provide any additional info you can help me with? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gavin McCullagh Sent: Sunday, May 06, 2007 10:36 AM To: [email protected] Subject: Re: Uprade to 7.04 On Sun, 06 May 2007, [EMAIL PROTECTED] wrote: > I am running a small (12 terminals) system and have recently upgraded > to 7.04. Before upgrading the 12 terminals would connect in about 3 - > 5 minutes. Since the upgrade, only about three terminals come up in 3 > minutes. The rest seem to hang up and I have to reboot several times. > After about one hour or more, all the terminals will eventually > connect. Is there something about 7.04 that I am unaware of that might > cause this behavior. The messages I get from the non-connecting > terminals is "Searching for DHCP", then "NO IP", repeated many times. Strange, it sounds like your DHCP clients are not getting a response from the server. That's sort of strange, particularly if you're using PXE network booting (which would imply you had already got a response from the dhcp server once). To check what's happening, you can run tcpdump somewhere on the network (say on the server) as the machine boots up. You should be able to see requests and responses. This command will do that for you: sudo tcpdump -i eth0 | grep DHCP assuming eth0 is the network interface the dhcp is happening on. One thing that has happened to me a few times is that where there are two network cards in a machine, the PXE network card boots up and does the first DHCP, at which point the linux kernel comes up and attempts to get its IP address by DHCP on the other network card. It might be worth checking you only have one network card. Gavin -- edubuntu-users mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users -- edubuntu-users mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
-- edubuntu-users mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
