I've isolated the K12LTSP server from the network and it boots right up using the LTSP's DHCP server. This is brining me closer to calling it a network problem. The problem I have with the VLAN option is that my content filter needs to see the client IP addresses of each client on the whole network and that would require, as I understand it, segmenting the network and routing traffic which would make all the clients in a dorm appear to the content filter as the IP address of the switch. I can't block a particular TCP port on the switch as that is Layer 4. I'm still looking for options... Mel <div>On 9/27/07, Mel Wade <<a href="mailto:mel@melwade.com">mel@melwade.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I'm currently leaning toward a network hardware problem as the issue. I'll be doing some more testing today. I know that its not DNS as everything is called by IP and I would have other problems if DNS were an issue. I've also ordered a new procurve switch to replace my core switch which is old and needs to be replaced anyway. With that I will be looking a the vlan option of having new each building pull DCHP from their own server and having the DHCP server be the K12LTSP server. I've not done much with managed switches and vLANs before so this will be a bit of new territory. <div> -- Mel Wade "The real problem is not whether machines think but whether men do." - BF Skinner <a href="http://www.melwade.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> http://www.melwade.com</a> </div></blockquote></div> -- Mel Wade "The real problem is not whether machines think but whether men do." - BF Skinner <a href="http://www.melwade.com">http://www.melwade.com </a>