Some added information that may help with troubleshooting. I can do a direct
login on the server itself, and I can use the same account remotely through a
terminal using ssh on the default port (22) from a machine running DSL
installed on the HD(only permitting commandline access to the server.) It's
only when I load the LTSP client using the Etherboot disk (overiding the DSL
loading) that I get the issue that no accounts that exist on the server want to
load on the client. The LTSP client seems to load fine and presents with a
graphical login on F7 and the commandline login on F1. I have used the
ltsp-update-sshkeys command on the server already.
I know that DHCP is set up correctly (since it's loading the NBI image with
no trouble), and NFS is working properly...(Able to remote mount the /Music
directory on DSL as well as the LTSP chroot is availiable to the Etherboot
system). As stated before, ssh is working properly on the server on port 22.
Currently the server doesn't have any firewalls enabled until after all
services are confirmed working properly, then the unused ports will be locked
down. The only thing I can figure is there's some authentication issue that
the user accounts may need to be opened up for remote access...but I'm not sure
how to go about doing that yet.
If any other ideas come through I will be very open to suggestions.
Thanks!
Michael Kosovic
Date: Sun, 12 Aug 2007 23:16:08 -0500
From: "Jim Kronebusch"
Subject: Re: [Ltsp-discuss] Unable to Login to server Remotely
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=iso-8859-1
> If I swap over to the shell that's running on F1, it
> gives me the Server Name, and distro version followed
> by the login prompt (as it should), but none of the
> username/password combinations that exist on the
> server work on the client. It continually returns
> login error. Is there some setting that I am
> overlooking?
You may have done something really stupid like I did last week :-)
I moved my ssh port to a non-standard port to thwart it being detected via
external
portscans (I was going to open things up so external users could use an SCP
client to
access their home folders). I did this on a Friday and had a long weekend, the
next
week I could log into clients, took almost a full day of troubleshooting before
it
dawned on me that LTSP5 relies entirely on ssh being on port 22, changed it
back and
things worked perfectly.
I only make this sort of stupid mistake publicly known so future users can find
this
solution via google and not have to ask such a question on the list :-)
Jim
Note to self, Fridays are now off limits for server modifications.
--
This message has been scanned for viruses and
dangerous content by the Cotter Technology
Department, and is believed to be clean.
---------------------------------
Got a little couch potato?
Check out fun summer activities for kids.-------------------------------------------------------------------------
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
