> On Wednesday 10 July 2002 11:36, Mandar Deodhar wrote: > > To boot up the thin clients i need to run dhcp on server > > machine. But i > > alreday have an NT machine running as DHCP server, which i > > dont want to > > touch. basically the NT admin wont let me touch it nor is > > he ready to > > make any changes
Just tell EtherBoot to look for the special string in the response, and tell the LTSP DHCP server to both provide that string and to only respond to MAC addresses that are hardcoded in its config file. From: Jan Humme <[EMAIL PROTECTED]> > Nop, you can only have one DHCP-server per segment. We're routinely running two, for failover redundancy. Both respond and the client picks one, mostly randomly. One of the network monitors makes sure that there are lots of IP addresses in both lease blocks in active use, so that we can detect when one server has failed. > In that case, Mandar would still need to talk to his > NT-admin, to set up such > communication between the DHCP-servers. It is best to set things up so that the two servers don't know about each other. That avoids mutual lockup oddities. > I would probably partition the network, or ask the NT admin to > either demonstrate that the NT tool can handle the > requirements of LTSP [hard -- unlikely to be as > straightforward or as capable as the ISC dhcp config file], or > agree to subordinate it to the *nux solution. If the NT admin is really unfriendly, you can probably hardcode the next server address into EtherBoot so that the DHCP response from the NT server is sufficient to let all your clients boot. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf _____________________________________________________________________ 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
