[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: Login Timeout Problems



Try to fix a valid DNS server in /etc/resolv.conf
or just add the client ip in /etc/hosts like:

10.10.10.22  Client-ssh-PC

Because before letting you to open telnet-ssh or ftp connection Linux do a ReverseDNS lookup.

Good luck

-----Message d'origine-----
De : Kevin Goddard [mailto:kevin realmworx com]
Envoyé : vendredi 27 février 2004 06:27
À : redhat-list redhat com
Objet : Re: Login Timeout Problems


Hi Pete,
Thanks for the response. 
It's not a network problem. I have 3 other computers (running older versions of Red Hat Linux) on the same network that don't have the problem.  Also this is happening on two identical machines 
running Red Hat 9.0.  I did check to make sure keep alive was on in sshd_config, it is.  I'll try to SSH to another computer and see what happens. I don't have any direct access to the server easily, 
but I will try and send someone down to login and try it.  The 131 seconds is from the /var/log/messages reports. I'm thinking it might be 120 seconds, and the 11 seconds is just a delay writing to 
the log (maybe?).  
I'll poke around some more, I just figured there must be some variable somewhere to stop people from idling in a window.
Thanks
Kevin


On Thu, 26 Feb 2004 18:45:09 -0800, Pete Nesbitt wrote:

>On February 26, 2004 10:26 am, Kevin Goddard wrote:
>> First, I apologize for immediatly subscribing to this list and then
>> emailing it, not really knowing if this is the appropriate place. However,
>> I am kind of desperate for some help and this was the best bet I could
>> find. I am running two machines with RedHat 9.0.  Both of them will log
>> out an idle user after 131 seconds.  This is less then helpful, as I tend
>> to login to a machine via SSH and move between windows.  Also, it will
>> even log out a SCP or FTP connection.  For the life of me I cannot find
>> where I can increase (or remove) this idle timeout. If anyone can point me
>> in some direction, it would be really helpful.
>> Thanks
>> Kevin Goddard
>
>
>Hi Kevin,
>
>Is this only via remote logins or does it also happen at a console?
>
>131 seconds, thats pretty quick. It sounds more like a networking issue than a 
>system thing simply because if you changed the settings to time out an 
>account on both systems, I'm sure you'd know it.
>sshd has "keep alive" on by default in /etc/ssh/sshd_config
>
>account timeout is set in /etc/profile or ~/.bash_profile using the var 
>"TMOUT=xxxx", with xxxx being the number of seconds of inactivity before 
>logout. It is not set by default (so won't time-out) but you can add it. 
>
>If it is only via remote access with ssh etc and not affecting local logins, 
>you could try:
>ssh localhost
>ssh to a third host
>ssh from a third host
>if possible remove any hubs/switches and use a crossover cable to test
>  (or try alternate ports in hub/switch)
>telnet (just to test)
>do not su to another user once logged in (?)
>flakey nic
>
>There is likely a single item causing the failure so try and bypass one thing 
>at a time. A third system would really help find fault point. Sounds painful 
>but you need to isolate things to find the problem. (and keep good notes for 
>a truth-table of what combo's work and what fails)  
>
>Sorry I don't have anything more specific, but hopefully it gives you some 
>things to look at.
>-- 
>Pete Nesbitt, rhce
>
>
>-- 
>redhat-list mailing list
>unsubscribe mailto:redhat-list-request redhat com?subject=unsubscribe
>https://www.redhat.com/mailman/listinfo/redhat-list





-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request redhat com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]