Hmmm...I have 2 NIC cards on the server, and from what I understand (admittedly not much) it shouldn't be possible for other computers around campus to find that server for IP addresses since it's serving the sub network only. In any case, I went around yesterday and very methodically reconnected everything back up that the district guy and I had disconnected on Wednesday. The lab is again up and running and all the other classroom LTSP setups are running fine too. I renewed IP addresses on a few machines and got good numbers along the way so maybe it WAS just a coincidence. Thanks for the quick reply in any case. I took my first CCNA course last night so I'm on my way to knowing what I'm talking about. Cheers -joe
On Wed, Sep 9, 2009 at 8:08 PM, ekul taylor <[email protected]> wrote: > It sounds more like the dhcp daemon on your edubuntu server is causing the > problem. You should check the options to ensure the server only binds to > the network card associated with the thin clients. On ubuntu the files to > check are /etc/default/dhcp3-server, /etc/dhcp3-server/dhcpd.conf and > possibly /etc/ltsp/dhcp.conf. You want the dhcp server to only listen on > the card your thin clients are attached to. > > If you only have 1 network card in your edubuntu server then you should > setup your existing dhcp server to serve pxe boot information (based on MAC > address likely) to your thin clients and disable the dhcp server in edubuntu > >
-- edubuntu-users mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
