OK, Hardware list:

Qwest DSL router modem (set with DHCP (192.168.0.1)).

Opensuse pc acting as server (set with DHCP for thin clients(kiwi-ltsp) (192.168.0.xxx from DSL DHCP)).

Regular pc with no hard drive, no cd-rom, no flash drive, blah, blah, blah. Only a PXE bootable nic for booting the kiwi-ltsp.


Problem: Thin client boots initial kernel for network booting with server at IP address 192.168.0.xxx, (perfect).

Thin client then looks at DSL router IP address 192.168.0.1 for the tftp server to load the kiwi-ltsp OS.

Solution: I don't know.

I know that I can change my router to non-DHCP and manually enter IP addresses for my network machines. But I feel as though that is just a bandaid fix. There has to be a way for the thin clients to know which server to look to for the appropriate information.

If anyone has the answer to this, I would REALLY appreciate it!

Thanks, Anthony

Why can't the server hand out the DHCP addresses itself? Why does the router have to do it at all?

Have to admit, you got me there. I am overlooking the obvious on that one.

BUT, after thinking about this for a minute,

A: I sometimes bring down the linux server for service, during which time it cannot provide DHCP information to clients.

B: The DSL router is acting as an internet server for the clients, which I am trying to keep seperate from the other server.

C: I have read through the DHCPD man pages, it does have options in there for allowing it to be a boot server, which I have tried, but as I said before, when looking for the TFTP server portion, the client automatically goes for the DSL router.

Thanks for replying, unless I can get it to work, your idea will be my fallback.