Martin wrote:
>
> Thanks for the suggestions, letting the client see what windows server wants it to
>see
> seems the best idea! I don't really want to live with the Windows solution....
>eventually I
> want to transfer the bulk of my server activities over to linux... it was just a
>quick (?!) fix.
>
> The DHCP on the LTSP server I have set up seems extremely unreliable. It all works
>fine
> for several client requests, then appears to just die. The logs on the server show
>several
> DHCPDISCOVER and DHCPOFFER messages for the clients, but the clients just don't
> seem to be getting these, as they sit with the "searching for server (DHCP)" message.
>
> I've tried restarting the dhcp service, and indeed any network related services, to
>no
> avail. The only remedy is to reboot the machine. This is far too reminiscent of
>windows
> for my liking - and not stable enough for serving the entire network!
>
> In addition, my clients infrequently get stuck waiting for an nfs server, which they
>never
> get and eventually give up! Again, the only solution seems to be a server reboot!
>
> Could this be anything blindingly obvious? Any ideas much appreciated!!
I've seen this behavior when the client workstations have problems with
their network cards. rom-o-matic will let you build a custom Etherboot
image; try building one with CONFIG_PCI_DIRECT.
-David
_____________________________________________________________________
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.openprojects.net
