I've been doing some hardware experiments with LTSP 4.0, and I've found that if I use the on-board ethernet connection on either the server or the client, NFS doesn't work.
While the terminal is booting up, I keep getting messages like: nfs: server 192.168.1.250 not responding nfs: server 192.168.1.250 OK which repeats throughout the boot process. If I switch the terminal to a PCI NIC, the problem goes away. As an important note, the problem didn't surface until I replaced the network hub with a switch. With the hub I was getting constant network collisions and NICs running in half duplex. Just wondering if anyone had seen similar behavior. Todd __________________________________ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&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
