Try checking rpcinfo -p localhost
and see if your mountd and other networking related daemons are running. If not, that would be the problem. the Professor ----- Original Message ----- From: "Martin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 21, 2002 4:31 AM Subject: [Ltsp-discuss] Re: Windows DHCP? > 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!! > > > > >> From: Martin <[EMAIL PROTECTED]> > >> Date: Wed, 20 Feb 2002 10:28:31 -0000 > >> > >> Made the change as suggested... it now goes to the correct > >>server... BUT.... despite only > >> specifying the "Root Path" as below, the client tries to > >mount /opt/ltsp/i386000. > >> I've tried putting it in quotes and various other things, > >but it always appends "000" to > >> the end! Has anyone else seen anything similar? > > > >Not that I want you to have to continue living with that MS > >DHCP server, but... > > > >What about `ln -s /opt/ltsp/i386 /opt/ltsp/i386000`? Will > >NFS export a symlink? If not, would a hard link work where > >a soft link wouldn't? > > > >And, if all of your clients are going to be served this way > >and no form of symlinking will work, just move (rename) the > >whole directory to /opt/ltsp/i386000! Then, for the sake of > >any scripts or future LTSP upgrades, create the link in the > >other direction so that the original directory exists and > >points to the new one. > > > >Jason > > > >_____________________________________________________________________ > >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 > > > > > _____________________________________________________________________ > 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 _____________________________________________________________________ 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
