On Wed, 31 Oct 2007, Alexandre Magaz Graça wrote:
> The DHCP server is in another machine (192.168.0.1). This is its dhcpd.conf
>
> ddns-update-style interim;
> ignore client-updates;
> authoritative;
>
> default-lease-time 10800;
> max-lease-time 21600;
>
> subnet 192.168.0.0 netmask 255.255.255.0 {
> ...
> }
I guess, something like this is missing:
use-host-decl-names on;
or ...
> host ltsp1 {
> hardware ethernet 00:16:e6:52:a8:d0;
> fixed-address 192.168.0.40;
> option subnet-mask 255.255.255.0;
> option broadcast-address 192.168.0.255;
> option routers 192.168.0.4;
> option domain-name-servers 192.168.0.4;
> option domain-name "udl.net";
> get-lease-hostnames true;
> next-server 192.168.0.4;
> option root-path "/opt/ltsp/i386";
> option tftp-server-name "192.168.0.4";
> filename "ltsp/i386/pxelinux.0";
> }
... from above an
option hostname "ltsp1";
> On the client:
> hostname -> ltsp (it should be ltsp1, I don't know where this ltsp is
> from ˙˙?)
Maybe this is the clue... try to get ltsp1 (the suggestions written
previously should help)
And check the /etc/ssh/ dir. and maybe /root/.ssh on the thin-client...
Good luck!
--
Zsolt
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.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.freenode.net
