<div dir="ltr">David,<br>I am starting a new message because it is rather difficult to sift through the digest to find your answers. If you are only subscribed to the digest, you may want to update you subscription to get the individual posts. It makes getting help easier and more timely.<br>
<br>If I understand your response, your /etc/ltsp/dhcpd.conf file is the default:<br><font face="T3Font_1" size="1"><font face="T3Font_1" size="1">
<p align="left"><font color="#0000bf" size="2">##</font></p>
<p align="left"><font color="#0000bf" size="2">Default LTSP dhcpd.conf config file.</font></p>
<p align="left"><font color="#0000bf" size="2">#</font></p>
<p align="left"><font color="#0000bf" size="2">authoritative;</font></p>
<p align="left"><font color="#0000bf" size="2">subnet <a href="http://192.168.0.0/" target="_blank">192.168.0.0</a> netmask <a href="http://255.255.255.0/" target="_blank">255.255.255.0</a> {</font></p>
<p align="left"><font color="#0000bf" size="2">range <a href="http://192.168.0.20/" target="_blank">192.168.0.20</a> <a href="http://192.168.0.250/" target="_blank">192.168.0.250</a>;</font></p>
<p align="left"><font color="#0000bf" size="2">option domain&name "<a href="http://example.com/" target="_blank">example.com</a>";</font></p>
<p align="left"><font color="#0000bf" size="2">option domain&name&servers <a href="http://192.168.0.1/" target="_blank">192.168.0.1</a>;</font></p>
<p align="left"><font color="#0000bf" size="2">option broadcast&address <a href="http://192.168.0.255/" target="_blank">192.168.0.255</a>;</font></p>
<p align="left"><font color="#0000bf" size="2">option routers <a href="http://192.168.0.1/" target="_blank">192.168.0.1</a>;</font></p>
<p align="left"><font color="#0000bf" size="2"># next&server <a href="http://192.168.0.1/" target="_blank">192.168.0.1</a>;</font></p>
<p align="left"><font color="#0000bf" size="2"># get&lease&hostnames true;</font></p>
<p align="left"><font color="#0000bf" size="2">option subnet&mask <a href="http://255.255.255.0/" target="_blank">255.255.255.0</a>;</font></p>
<p align="left"><font color="#0000bf" size="2">option root&path "/opt/ltsp/i386";</font></p>
<p align="left"><font color="#0000bf" size="2">if substring( option vendor&class&identifier, 0, 9 ) = "PXEClient" {</font></p>
<p align="left"><font color="#0000bf" size="2">filename "/ltsp/i386/pxelinux.0";</font></p>
<p align="left"><font color="#0000bf" size="2">} else {</font></p>
<p align="left"><font color="#0000bf" size="2">filename "/ltsp/i386/nbi.img";</font></p>
<p align="left"><font color="#0000bf" size="2">}</font></p>
<p><font color="#0000bf" size="2">}</font></p></font></font>
<div style="font-size: 13px; font-family: arial,helvetica,sans-serif;"> So the next three things to look at are<br>(1) Is the server physically connected to the thin client network (all lights on NICs and switches are green)? It sounds silly, but I have personally spent hours tracking down a layer 1 issue by troubleshooting at layers 4-7. <br>
(1) IP configuration of your box - Have you configured the interface that serves the thin client network in the <a href="http://192.168.0.0">192.168.0.0</a> subnet <a href="http://255.255.255.0">255.255.255.0</a> range?<br>
(2) contents of /var/log/daemon.log - just the lines that come in as you try to boot a client. Pardon me if you know this already, but you can <br>#sudo tail -f /var/log/daemon.log to watch what is happening as you boot a client.<br>
<br>Charles<br></div><br></div>