[K12OSN] Users can't login

Brian Fristensky bfristen at shaw.ca
Wed Dec 1 20:59:39 UTC 2010


Thanks for all your suggestions. I have listed the
results below. I hope something below clicks. I am
certain this is the result of one tiny setting, but
the question is, which one?


 >Do an edit to your /etc/hosts file again.
 >If your servername is server1 and your domain name is domain1
 >your line should look like this.
 > localhost.localdomain localhost server1.domain1 server1
 >   orpheus # Added by NetworkManager       localhost.localdomain   localhost       localhost4 
::1     orpheus localhost6.localdomain6 localhost6      orpheus.localdomain 

( the lines beginning and ::1 were wrapped by the mailer, but
are each one line.)

 >Reboot server. Try an TC login after this.
 >See what happens.

No change after reboot.

Note that there really isn't a correct hostname.domainname for the server.
This is because it's a home internet connection where the router
is directly connected to the service provider. So the name
in the hosts file above really refers to the router. The router
forwards port 22 to the server, so it is possible to ssh to
the server from the outside world.

The server has a single NIC and an ltsp bridge, the latter
automatically created by LTSP.

There is no internal DNS, so the server itself doesn't
really have a name, other than orpheus.localdomain, which
is already in the file.

The static IP address of the server (
is in the dhcpd.conf file.

I have used this dhcpd.conf file successfully with LTSP
under Fedora 11. The problem arose when I did a clean
install of F13 and then installed LTSP.

 >Are you able to vnc into this server from any machine on your network?
 >Doesn't make any difference if it is windows or a linux machine.
I am writing this message on a vnc session, running on the
server and displaying on a Linux laptop.

 >You do have the default vnc server setup via ltsp,correct?
No. I have never used the vnc server in ltsp.

 >Do you have iptables stopped also?
I have tried stopping both iptables and ip6tables, with
no change after restarting the network.

 >Can root log into a thin client successfully?

%ssh -l root
ssh: connect to host port 22: Connection refused
PING ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=64 time=0.251 ms
64 bytes from icmp_seq=2 ttl=64 time=0.247 ms
64 bytes from icmp_seq=3 ttl=64 time=0.249 ms
64 bytes from icmp_seq=4 ttl=64 time=0.246 ms
64 bytes from icmp_seq=5 ttl=64 time=0.241 ms
--- ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4672ms
rtt min/avg/max/mdev = 0.241/0.246/0.251/0.020 ms

BTW - I hadn't initially realized one could login to the
thin client, but I guess it's just another Linux machine.
One presumes that before you do that, you would have to
set the root password in the chroot, and then rebuild the
image? I have not explicitly set any password in the chroot,
up to now, and it is not part of the documented LTSP setup.

 >Do the following two commands .
 >nmap localhost
Starting Nmap 5.21 ( http://nmap.org ) at 2010-12-01 14:38 CST
Nmap scan report for localhost (
Host is up (0.0000090s latency).
rDNS record for localhost.localdomain
Not shown: 990 closed ports
22/tcp   open  ssh
25/tcp   open  smtp
111/tcp  open  rpcbind
631/tcp  open  ipp
2000/tcp open  cisco-sccp
2049/tcp open  nfs
5901/tcp open  vnc-1
6000/tcp open  X11
6001/tcp open  X11:1
9220/tcp open  unknown

Nmap done: 1 IP address (1 host up) scanned in 0.14 seconds

 >nmap -sU localhost,
Starting Nmap 5.21 ( http://nmap.org ) at 2010-12-01 14:39 CST
Nmap scan report for localhost (
Host is up (0.000012s latency).
rDNS record for localhost.localdomain
Not shown: 992 closed ports
67/udp   open|filtered dhcps
69/udp   open|filtered tftp
111/udp  open          rpcbind
123/udp  open          ntp
177/udp  open          xdmcp
631/udp  open|filtered ipp
2049/udp open          nfs
5353/udp open|filtered zeroconf

Nmap done: 1 IP address (1 host up) scanned in 1.30 seconds

More information about the K12OSN mailing list