<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.12.1"> </HEAD> <BODY> This is a bit older (from my 6.06 server, not 6.10; the format changes a bit for Edgy) but this is what works in our production environment. The necessary DHCP options to set on a Windows-based DHCP server to enable clients to find the server are: <TT>017 (root path)</TT> <TT> /opt/ltsp/i386</TT> <TT>066 (server address)</TT> <TT> x.x.x.x</TT> <TT>067 (tftp file)</TT> <TT> ltsp/pxelinux.0</TT> This can be set as part of a scope (if a separate VLAN has been put in place for a group of computers) or as part of an individual reservation for a known MAC address. (Bit of a shorter read than the reference Gavin gave, but if you want the full details, Gavin's link is excellent!) ~Clay On Thu, 2006-14-12 at 22:04 +0000, Gavin McCullagh wrote: <BLOCKQUOTE TYPE=CITE> <PRE> On Thu, 14 Dec 2006, Gavin McCullagh wrote: > Alternatively, you can probably get windows to serve the DHCP > network booting information -- I'm not experienced with this myself but I'm > sure I've heard of someone doing it. This appears to document how you might do this. <A HREF="http://diet-pc.sourceforge.net/windows/etherboot-w2k.html">http://diet-pc.sourceforge.net/windows/etherboot-w2k.html</A> Personally, I'd prefer to use the linux dhcp server but it's really a matter of taste and what suits your particular network. If you're using windows for dynamic dns, I imagine you need to use the windows dhcp server too. Gavin </PRE> </BLOCKQUOTE> </BODY> </HTML>