Thank You, I will consider it Clodoaldo From: Dieter Kroemer <[EMAIL PROTECTED]> Re: LTSP 4.0 connection refused 2003-12-28 10:54
Am Sonntag, 28. Dezember 2003 19:40 schrieb Clodoaldo Pinto Neto: > (I'm not good enough with Linux) I had to do a reinstall. This time > the most current distro I had at hand was Fedora Core 1. So I > installed it and as I was doing it all fresh why not try the new > LTSP 4.0? If you want to use Fedora you can download k12ltsp, it's working with ltsp4.0 out of the box and the installation is very very ... easy :-) -- Viele Grüße/kind regards (o_ (o_ Dieter //> (o_ (o_ //\ http://www.linux-in-der-schule.de V_)_ (/)_ (\)_ V_/_ From: <[EMAIL PROTECTED]> LTSP 4.0 connection refused 2003-12-28 10:40 Hello, I was running LTSP in a Mandrake 9.1 server and 3 workstations. Local application [EMAIL PROTECTED] It was working fine until 2 days ago when the server motherboard died. Causa mortis: stuffed capacitors. Since I could not make the installed system work with another board (I'm not good enough with Linux) I had to do a reinstall. This time the most current distro I had at hand was Fedora Core 1. So I installed it and as I was doing it all fresh why not try the new LTSP 4.0? Installation was mostly easy. Just a little confused about the kernel install. After or before? Did it after. Configuration was not all that hard. Now I can ping the workstations, can get to a bash shell on then, but can't get into telnet session from the WS to the server neither login from the server into the WS that is the only thing I need since the WS do not have monitors and keyboards as they are just number crunchers. The message I get is connection refused: ----------------------------------------- [EMAIL PROTECTED] ssh]# ssh w01 ssh: connect to host w01 port 22: Connection refused [EMAIL PROTECTED] ssh]# telnet w01 Trying 192.168.0.4... telnet: connect to address 192.168.0.4: Connection refused telnet: Unable to connect to remote host: Connection refused ---------------------------------------------------- I'm getting to the server session (also monitor less and dEskless) by ssh from a Windows machine. Could this fact be impeding the correct authentication? I followed the instructions about the ssh key in the documentation. -------------------------------------------------- When I'm booting the WS I get the messages: mounting root filesystem doing the pivot_root nfs: server 192.168.0.2 OK nfs: server 192.168.0.2 not responding, still trying -------------------------------------------------- The last two lines are repeated for some time until it gets to the bash prompt and sometimes after that also. There are many other messages but unless there is a log (which I couldn't find) I can't read and take note as they are too fast. There is one thing I suspect is causing problems. It is the NIS domain name configuration. I don't know how to do it and if is it important. So I configured the hosts with localdomain as the domain name: ------------------------------------------------ [EMAIL PROTECTED] etc]# cat hosts 127.0.0.1 s00 localhost.localdomain localhost 192.168.0.1 vta5.localdomain vta5 192.168.0.2 s00.localdomain s00 192.168.0.3 w00.localdomain w00 192.168.0.4 w01.localdomain w01 192.168.0.5 w02.localdomain w02 192.168.0.6 w03.localdomain w03 --------------------------------------------------------- [EMAIL PROTECTED] etc]# cat exports /opt/ltsp 192.168.0.0/255.255.255.0(ro,no_root_squash,sync) /var/opt/ltsp/swapfiles 192.168.0.0/255.255.255.0(rw,no_root_squash,async) /home/cpn/fah 192.168.0.0/255.255.255.0(rw,no_root_squash,async) ------------------------------------------------ [EMAIL PROTECTED] etc]# pwd /opt/ltsp/i386/etc [EMAIL PROTECTED] etc]# cat lts.conf [Default] SERVER = 192.168.0.2 XSERVER = auto X_MOUSE_PROTOCOL = "PS/2" X_MOUSE_DEVICE = "/dev/psaux" X_MOUSE_RESOLUTION = 400 X_MOUSE_BUTTONS = 3 USE_XFS = N SCREEN_01 = shell RUNLEVEL = 3 LOCALAPPS = Y NIS_DOMAIN = localdomain NIS_SERVER = 192.168.0.2 ---------------------------------------------------------------- This are the last lines of /var/log/messages: Dec 28 15:56:37 s00 dhcpd: DHCPDISCOVER from 00:0b:6a:02:48:6e via eth0 Dec 28 15:56:37 s00 dhcpd: DHCPOFFER on 192.168.0.4 to 00:0b:6a:02:48:6e via eth0 Dec 28 15:56:39 s00 dhcpd: DHCPREQUEST for 192.168.0.4 (192.168.0.2) from 00:0b:6a:02:48:6e via eth0 Dec 28 15:56:39 s00 dhcpd: DHCPACK on 192.168.0.4 to 00:0b:6a:02:48:6e via eth0 Dec 28 17:56:39 s00 in.tftpd[4901]: tftp: client does not accept options Dec 28 15:56:45 s00 dhcpd: DHCPDISCOVER from 00:0b:6a:02:48:6e via eth0 Dec 28 15:56:45 s00 dhcpd: DHCPOFFER on 192.168.0.4 to 00:0b:6a:02:48:6e via eth0 Dec 28 15:56:47 s00 dhcpd: DHCPREQUEST for 192.168.0.4 (192.168.0.2) from 00:0b:6a:02:48:6e via eth0 Dec 28 15:56:47 s00 dhcpd: DHCPACK on 192.168.0.4 to 00:0b:6a:02:48:6e via eth0 Dec 28 15:56:47 s00 rpc.mountd: authenticated mount request from w01.localdomain:690 for /opt/ltsp/i386 (/opt/ltsp) -------------------------------------------------------- Please let me know what are the missing information missing. TIA Clodoaldo Pinto Neto Brasília, Brasil ______________________________________________________________________ Conheça a nova central de informações anti-spam do Yahoo! Mail: http://www.yahoo.com.br/antispam ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _____________________________________________________________________ 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
