On Sat, 11 Jan 2003, richard lucassen said: > On Sat, 11 Jan 2003 09:15:51 +0100 > Ragnar Wisloff <[EMAIL PROTECTED]> wrote: > > > richard lucassen wrote: > > > On Fri, 10 Jan 2003 16:36:14 -0600 > > > "Bimal Adhikari" <[EMAIL PROTECTED]> wrote: > > > > > > > > >>Check your /etc/host.allow file > > > > > > > > > Nope. Even an "ALL: ALL" doesn't help. (the hosts.allow in > > > /opt/ltsp/i386/etc/ I presume) > > > > No, in the /etc/hosts.allow on the server. > > > > By doing the changes in the /opt/ltsp/i386 tree you affect the client, > > > > not the server. That is probably not what you want. > > Hmmm, I just tried it again (I just woke up and switched on the > LTSP-server) and it works. Strange, I wouldn't have thought to restart > something on the server, just a reset of the X-server of the > LTSP-client.
If it was indeed the change to the servers hosts.allow that did it, then yes it would make sense, as a restart of inetd would be necessary. But presumably you already had something in the servers /etc/hosts.allow for the client, because AFAIK, in order for the client to mount the necessary directories via NFS it needs tp have access - at least that's what I had to do on my SuSE server. ---------------------------------------------------------------- John Karns [EMAIL PROTECTED] ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _____________________________________________________________________ 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
