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.
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.
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!