An additional DHCP server is just out of the question. Our clients will be scattered across the network in different subnets, a dhcp server in every location a client exist is not worth it. Is this a limitation with the LTSP diskless client or are all diskless clients the same?
----- Original Message ----- From: "rob apodaca" <[EMAIL PROTECTED]> To: "Abdullah A. Al-Humaid" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, September 02, 2002 2:11 PM Subject: Re: [Ltsp-discuss] ThinClient does not communicate with DHCP - Additional info > On Mon, 02 Sep 2002 08:02:11 +0300 > "Abdullah A. Al-Humaid" <[EMAIL PROTECTED]> wrote: > > > > > Please note that each of the three parties on the production setup (DHCP SERVER, LTSP SERVER, and Diskless Client) are on a different subnets. Is there a problem in this kind of setup ? Are there any routing issues that I have to take care of? > > The diskless client needs to be able to broadcast to the dhcp server. So, if there is a router between your client and dhcp server, it won't work. Why not throw up a quick and dirty linux dhcp server on the same subnet as the diskless clients? > > It does not matter where the LTSP server is located. ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
