edcirh Posted May 13, 2010 Posted May 13, 2010 and I'm getting really frustrated now. We run a Windows network in the school, with one 2K3 Server serving all our PCs. I want to build a Linux thin-client solution for the new library we've just had (for many reasons). I've built 2 servers (1 root server, 1 application server) as per instructions here, here, and here. The client would pick up the Linux server, but then (after much tweaking with network settings/dhcp configs/nbd-server configs/etc, it got to the point where it would ignore the static IP addresses I'd allocated & pick one from my Win dhcp server. So I then uninstalled dhcp3-server on my Linux server, and tweaked dhcp on my Windows server (instructions here, dhcp settings attached). Now, I'm stuck with the client requesting an IP address & just being ignored by the dhcp server. I know that it's going to be me missing a tiny config setting somewhere, but I'm out of ideas (&so's Google!). Any help you could give me would be great. Many thanks Ian
webman Posted May 13, 2010 Posted May 13, 2010 I'm not sure if it's just a typo on the Wiki page, but the PXE filename on the Windows instructions isn't prefixed with a forward-slash, like the other one is: filename "/ltsp/i386/pxelinux.0"; https://help.ubuntu.com/community/UbuntuLTSP/LTSP-Cluster Try changing option 67 to /ltsp/i386/pxelinux.0 I take it the workstations are on the same physical network segment as your Windows server?
dhicks Posted May 13, 2010 Posted May 13, 2010 I want to build a Linux thin-client solution for the new library we've just had (for many reasons). You mean you want the thin clients on the same network as the Windows machines? Is there any way you can put the thin clients on their own switch hooked directly to a second network interface on your LTSP server? That would make things a whole lot simpler. -- David Hicks
edcirh Posted May 13, 2010 Author Posted May 13, 2010 Hi webman, I've tried putting the / at the start of option 67, tried the paths to the 3 pxelinux.0 files I've got on the server, and also tried prefixing the root path with the server name, but still no joy. Hi David, I don't have a spare switch I could use, or second NICs for the servers, I haven't been given my budget yet so can't buy the kit, and the Head wants this working last week!
webman Posted May 13, 2010 Posted May 13, 2010 Are all IP addresses and client reservations correct? E.g. Is 10.172.4.1 the server that is hosting the PXE files? Do the MAC addresses match up?
dhicks Posted May 13, 2010 Posted May 13, 2010 I don't have a spare switch I could use, or second NICs for the servers If you PM me your address I have a spare D-Link 1/100 16-port 19"-rack-mountable switch and a boxed, wrapped Belkin PCI 10/100 network card that you can have. -- David Hicks 1
edcirh Posted May 13, 2010 Author Posted May 13, 2010 David, what an extremely generous offer, thank you. I've PMd details. webman, yep, all correct...
dhicks Posted May 13, 2010 Posted May 13, 2010 With two NICs, one attached to a switch which each thin client is then attached to, LTSP server setup simply becomes insert install disk, select LTSP install, done. -- David Hicks
edcirh Posted May 13, 2010 Author Posted May 13, 2010 With two NICs, one attached to a switch which each thin client is then attached to, LTSP server setup simply becomes insert install disk, select LTSP install, done. -- David Hicks I can hardly wait!!! I'd still like to crack this one as well, though - must be the masochist in me!! :-D
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now