On 17/12/2011, at 5:22 AM, ltsp-discuss-requ...@lists.sourceforge.net wrote:
I'll top post, because there is so much stuff below that may be noise or very
important.
ssh needs a reverse lookup or it will take long.
Your client needs to have to have an entry, I aways have a domain dunno if you
Have you tried using the verbose flag with ssh? It spits out a lot of
information, but you could get some insight if it is getting caught up
with authentication or resolving hostnames.
I usually use it with three Vs:
ssh -vvv myserver
-Aaron
On 12/15/2011 06:34 AM, Rob Owens wrote:
> On Thu
On Thu, Dec 15, 2011 at 08:06:14AM +0100, Emmanuel Le Normand wrote:
> Hi,
> On Wed, 14 Dec 2011 20:46:24 -0500
> David Hopkins wrote:
>
> > I checked and resolv.conf had entries for IPv6 and also had a weird
> > entry of
> >
> > 127.0.1.1 ncslts3
> >
> > on the ncslts3 server. I commented out
Hi,
On Wed, 14 Dec 2011 20:46:24 -0500
David Hopkins wrote:
> I checked and resolv.conf had entries for IPv6 and also had a weird
> entry of
>
> 127.0.1.1 ncslts3
>
> on the ncslts3 server. I commented out all the IPv6 entries and also
> the above line. Logins still take about 25 seconds to au
Try putting the addresses of the clients in the hosts file
>
> client1 192.168.0.10 etc whatever range you have allocated.
>
Then take a look at dnsmasq
you may not have any other servers you need to reference so take those
lines out.
Peter
/etc/dnsmasq.conf file add the following options a
I checked and resolv.conf had entries for IPv6 and also had a weird entry of
127.0.1.1 ncslts3
on the ncslts3 server. I commented out all the IPv6 entries and also
the above line. Logins still take about 25 seconds to authenticate,
but that is less than the 30 second timeout limit so they are wo
I'm not sure what else to suggest except that you take a look at
/etc/resolv.conf and test lookups using the nslookup command.
-Rob
On Wed, Dec 14, 2011 at 07:38:44PM -0500, David Hopkins wrote:
> Yep .. that is exactly what mine looks like and it gets overwritten at
> each client though I do not
On Wed, Dec 14, 2011 at 07:05:05PM -0500, David Hopkins wrote:
> I am beginning to suspect this issue is because ssh isn't resolving
> names correctly? Timing
>
> ssh myserver
>
> from a shell (ALT-CTL-F2) takes about 30 seconds to resolve myserver.
> However, ssh any_other_server returns immedi
Yep .. that is exactly what mine looks like and it gets overwritten at
each client though I do not know how.
On the server that works, the login finishes in about 26 seconds ...
timed with a stopwatch. However, on the other systems, the 'no
response from server' message appears at 30 seconds .. so
On Wed, Dec 14, 2011 at 07:05:05PM -0500, David Hopkins wrote:
> All,
>
> I am beginning to suspect this issue is because ssh isn't resolving
> names correctly? Timing
>
> ssh myserver
>
> from a shell (ALT-CTL-F2) takes about 30 seconds to resolve myserver.
> However, ssh any_other_server retu
All,
I am beginning to suspect this issue is because ssh isn't resolving
names correctly? Timing
ssh myserver
from a shell (ALT-CTL-F2) takes about 30 seconds to resolve myserver.
However, ssh any_other_server returns immediately. So, why wouldn't
myserver resolve quickly? This is true from a
We are having a major issue with thin client authentication. It
started just after lunch time today. Authentication works fine from
console and on terminal, but ssh takes a very long time to connect.
One server (out of 5) can still connect though the login process takes
quite a while to complete.
12 matches
Mail list logo
