I'm 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. I suspect it is
a timeout issue with LDM. From a shell at the thin client I can ssh to
any system and authenticate, however this also takes up to a minute for
ssh to connect. The response at the GUI login screen is "no response
from server, restarting". I've already updated the sshkeys and
completely rebuilt the image but this hasn't resolved the issue. How
does LDM use ssh for authentication? Is there a reason ssh would have to
be routed?
Any help is greatly appreciated!
Jeff Donaldson
Newark Charter School
--
Regards,
Jeff Donaldson
Data Services Manager
Newark Charter School
(302) 369-2001 ext:425
jdonaldson@ncs.k12.de.us
--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
12-14-2011, 11:09 PM
Jeff Donaldson
Authentication Issue
So it seems the thin client console can ssh to any other server in less
than a second, but if I try to ssh from the thin client console back to
the ltsp server that it booted it's image from it takes 30-35 seconds. I
suspect that this is hitting a timeout and causing authentication to
fail. Question is, what would cause the thin client to be so slow
talking back to the server it booted from? Any ideas?
To: "Edubuntu Users Group" <edubuntu-users@lists.ubuntu.com>
Subject: Authentication Issue
Good Afternoon,
I'm 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. I suspect it is
a timeout issue with LDM. From a shell at the thin client I can ssh to
any system and authenticate, however this also takes up to a minute for
ssh to connect. The response at the GUI login screen is "no response
from server, restarting". I've already updated the sshkeys and
completely rebuilt the image but this hasn't resolved the issue. How
does LDM use ssh for authentication? Is there a reason ssh would have to
be routed?
Any help is greatly appreciated!
Jeff Donaldson
Newark Charter School
--
Regards,
Jeff Donaldson
Data Services Manager
Newark Charter School
(302) 369-2001 ext:425
jdonaldson@ncs.k12.de.us
--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
����������--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
you probably need to disable dns lookup on ssh server.
simply add "UseDNS no" in /etc/ssh/sshd_config
On Wed, Dec 14, 2011 at 7:09 PM, Jeff Donaldson <jdonaldson@ncs.k12.de.us> wrote:
So it seems the thin client console can ssh to any other server in less
than a second, but if I try to ssh from the thin client console back to
the ltsp server that it booted it's image from it takes 30-35 seconds. I
suspect that this is hitting a timeout and causing authentication to
fail. Question is, what would cause the thin client to be so slow
talking back to the server it booted from? Any ideas?
To: "Edubuntu Users Group" <edubuntu-users@lists.ubuntu.com>
Subject: Authentication Issue
Good Afternoon,
I'm 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. I suspect it is
a timeout issue with LDM. From a shell at the thin client I can ssh to
any system and authenticate, however this also takes up to a minute for
ssh to connect. The response at the GUI login screen is "no response
from server, restarting". I've already updated the sshkeys and
completely rebuilt the image but this hasn't resolved the issue. How
does LDM use ssh for authentication? Is there a reason ssh would have to
be routed?
Any help is greatly appreciated!
Jeff Donaldson
Newark Charter School
--
Regards,
Jeff Donaldson
Data Services Manager
Newark Charter School
(302) 369-2001 ext:425
jdonaldson@ncs.k12.de.us
--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
����������
--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
you probably need to disable dns lookup on ssh server.
simply add "UseDNS no" in /etc/ssh/sshd_config
On Wed, Dec 14, 2011 at 7:09 PM, Jeff
Donaldson <jdonaldson@ncs.k12.de.us>
wrote:
So it seems
the thin client console can ssh to any other server in less
than a second, but if I try to ssh from the thin client
console back to
the ltsp server that it booted it's image from it takes 30-35
seconds. I
suspect that this is hitting a timeout and causing
authentication to
fail. Question is, what would cause the thin client to be so
slow
talking back to the server it booted from? Any ideas?
To: "Edubuntu Users Group" <edubuntu-users@lists.ubuntu.com>
Subject: Authentication Issue
Good Afternoon,
I'm 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. I suspect it is
a timeout issue with LDM. From a shell at the thin client I can ssh to
any system and authenticate, however this also takes up to a minute for
ssh to connect. The response at the GUI login screen is "no response
from server, restarting". I've already updated the sshkeys and
completely rebuilt the image but this hasn't resolved the issue. How
does LDM use ssh for authentication? Is there a reason ssh would have to
be routed?
Any help is greatly appreciated!
Jeff Donaldson
Newark Charter School
--
Regards,
Jeff Donaldson
Data Services Manager
Newark Charter School
(302) 369-2001 ext:425
jdonaldson@ncs.k12.de.us
--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
����������
--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
--
Regards,
Jeff Donaldson
Data Services Manager
Newark Charter School
(302) 369-2001 ext:425
jdonaldson@ncs.k12.de.us
--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
Authentication Issue
