En/na Luiz Guaraldo ha escrit: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Use the command as root: ltsp-update-sshkeys > > Maybe it help you... > > - -- > Atenciosamente, > > Luiz Guaraldo > Tec. Redes Computadores > CREA/RS 146230 > > > Telefones: > > Porto Alegre: 55-51-4063-9076 > 3024-3568 > São Paulo...: 55-11-4063-8864 > New York....: 1-212-202-1454 > > Eletrônicos: > > ICQ...: 256177778 > YID...: guaraldo_rs > MSN...: [EMAIL PROTECTED] > Jabber: [EMAIL PROTECTED] > E-mail: [EMAIL PROTECTED] > > > Propus Informática Ltda. > Rua Santa Rita, 282, 2o andar - Bairro Floresta > 90.220-220 - Porto Alegre - RS - Brasil > > > Alexandre Magaz Graça escreveu: >> En/na SZABO Zsolt ha escrit: >>> 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) >>> >> Ok, after adding the use-host-decl-names statement in dhcpd.conf, now >> the thin client gets the right host name, but it stills give me the same >> authentication message error. >> >>> And check the /etc/ssh/ dir. and maybe /root/.ssh on the thin-client... >>> >> > Good luck! >> > -- >> > Zsolt >> > >> >> I checked it and all seems correct. >> >> BTW, I've just discovered an ldm log file in the thinclient with this: >> >> LDM2 starting >> LDM2 running on ip address 192.168.0.40 >> Launching Xorg >> Spawning greeter: /usr/bin/ldmgtkgreet >> In get_userid >> Establishing a session with 192.168.0.4 >> Attempting ssh session as maikel >> In get_passwd >> ssh_chat: looking for ssword: from ssh >> expect saw: [EMAIL PROTECTED]'s password: >> ssh_chat: got it! Sending pw >> expect saw: >> Warning: No xauth data; using fake authentication data for X11 forwarding. >> LTSPROCKS >> >> Saw sentinel. Logged in successfully >> Established ssh session. >> Process returned no status >> Executing rc files. >> Beginning X session. >> >> I suppose the key of the problem is this xauth warning, but why is this >> happening? >> >> On the thin client there is a /root/.Xauthority generated by LDM when it >> launches. All seems correct here. >> >> On the server side, the user maikel also has an .Xauthority file. If I >> delete it, I still get the same warning. >> >> More ideas? >> >> Thanks, >> Àlex >>
I've already tried this, but still no luck... ------------------------------------------------------------------------- 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