"This workstation is not authorized to connect to the server"

[Tom Haddon]

After running ltsp-build-client, I am able to PXE boot and get a login prompt from a test client. However, I then get a message saying "This workstation is not allowed to connect to the server".

I am running gutsy beta:

$ dpkg --list | grep ltsp
ii ltsp-server 5.0.39 Basic LTSP server environment
ii ltsp-server-standalone 5.0.39 Complete LTSP server environment
ii ltspfs 0.5-0ubuntu2 Fuse based remote filesystem for LTSP thin c

[Oliver Grawert (ogra)]

run ltsp-update-sshkeys and ltsp-update-image, apparently there were no ssh keays in place for the interface you use ltsp on while you were building the client (i.e. the interface wasnt up or teh IP changed after the client was built), the two commands (run in that order) above fix that.

[Tom Haddon (mthaddon)]

I verified that the interface is up (eth0):

mthaddon@rhapsody:~$ ip link
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:0f:b0:45:f0:c5 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:90:4b:b7:5d:39 brd ff:ff:ff:ff:ff:ff

I then ran sudo /usr/sbin/ltsp-update-sshkeys && sudo /usr/sbin/ltsp-update-image but I still get the same message about not being authorized to connect to the server.

I notice that the ltsp-update-image script says it relies on an nbd server being served from inetd. I have the following line in my /etc/inetd.conf

2000 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/nbdrootd /opt/ltsp/images/i386.img

I don't see any nbd process or netstat -a listing for it. Not sure if that's normal...

[Oliver Grawert (ogra)]

nbd is used to boot, so if you have the login screen in front of oyu you dont have to care about dhcp, tftp or nbd anymore
did you follow the quickinstall guide from https://help.ubuntu.com/community/UbuntuLTSP/QuickInstall ?
is your ssh server up and running while you try to log in ?

[Tom Haddon (mthaddon)]

Seems it was the same issue that was biting me with bug 150419. If I add a trailing slash to the line that finds subdirectories under /opt/ltsp in ltsp-update-sshkeys, then it seems to work as advertised :)

[Oliver Grawert (ogra)]

thats pretty weird, since i cant reproduce it on any machine here and havent seen any other user report anything that remotely looks like it, the trailin / shouldnt have any impact at all

[Tom Haddon (mthaddon)]

Mystery solved. My /opt/ltsp is actually a symlink to /data/ltsp. This seems to be causing me the issue. I'll workaround.