If you didn't change anything at all (server side), that's weird. My first try would be to restart the nfs-server (while all clients are switched off) and then reboot them one by one.running dhclienttrying
Mounting root filesystem : /opt/ltsp/i386
Doing pivot root
NFS : server 192.168.0.253 not responding, still
NFS : server 192.168.0.253 not responding, stilltrying
NFS : task 62 can't get a request slotproblem persists.
I have three other clients perfectly booting.
I shutdown all three clients and even then the same
If you encounter the situation that your problem client won't boot, but one that you switched on after it does very well, it could be some network hardware problem. There were cases were switching the hub port of one client solved the problem! For excluding cabling & switch timing problems and the like, connecting the client to the server with a crossover cable seems a good idea. In the long run, switching those NICs for rtl8139 cheap 100MBit NICs (I currently buy them at less than 4 EUR) could be good idea as well.
HTH
Anselm
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&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
