See previous discussions on list. I have seen this caused by a network switch that doesn't handle 100Mb to 10Mb conversions robustly. UDP packets in NFS are fragmented and when a part gets lost Linux NFS does not seem to recover. Either try a hub or get a better switch that forces upstream collision when it is about to drop fragments.
On Thu, 2003-08-28 at 18:37, Marco Palominos wrote: > Hello: > > We have installed ltsp with RedHat 9 , we run ./lstp_initialize , and the > DHCP is running, it was tested with PC Windows 95 (client). > > And when a PC with Ltsp Etherboot , the machine display the following > message: > > me 192.168.0.101 > Doing the pivot_root > nfs: server 192.168.0.254 not responding still trying > nfs: server 192.168.0.254 not responding still trying > nfs: task 82 can't get a request slot > > All the configurations files are set like the Manual of LTSP. > > About the conections: > > Server Dual Pentium > eth1 connected to a cable modem > eth0 LAN > > Help Please > > Thanks > > _________________________________________________________________ > ¿Estás buscando un auto nuevo? http://www.yupimsn.com/autos/ > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _____________________________________________________________________ > 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 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _____________________________________________________________________ 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
