Anselm Martin Hoffmeister wrote:
I do not at all understand what is going on in the packet log you sent earlier. This does not look like DHCP packets to me. Are your clients running etherboot, or (Intel/...) PXE or some proprietary "boot agent" that might try to do its own discovery method? Where did the client (seems to be the .198, if I figure that right) get that address from in the first place? If your problems persist, a dump right from the moment of powering on the thin client could shed some light onto this.
Well, I finally realized what I was doing wrong -- I had TFTP running on three servers which was probably confusing things, and once I trimmed it to one, corrected my firewall, and set next-server in dhcpd.conf, everything is good.
Still, I dont understand why the TFTP server was sending responses on those ports. The clients in this case do have Intel motherboards + network cards -- does that make a difference? It looked like it was booting PXE 2.0 or something.
Steve ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _____________________________________________________________________ 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.freenode.net
