ssh problem "server unexpectedly closed network connection"
SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
ssh problem "server unexpectedly closed network connection"
Hi,
I'm remotely connecting to SUSE 10 system using OpenSSH_4.2p1 from PUTTY. My problem is that my session to the server was getting disconnected after some time. when i'm giving "exit" command, it is giving the message "server unexpectedly closed network connection". Also it is showing my last login wrongly. what went wrong from sshd side i dont know.could any one help me regarding this.
My problem is that my session to the server was getting disconnected after some time.
Disconnection can happen for different reasons ranging from flaky network connections and shell session timeouts to load problems and admins forcing you out...
Quote:
Originally Posted by sunilvadranapu
when i'm giving "exit" command, it is giving the message "server unexpectedly closed network connection".
If ending your session from a GNU/Linux workstation works OK then maybe that's just a PuTTY-specific informational message?
Quote:
Originally Posted by sunilvadranapu
Also it is showing my last login wrongly.
You didn't show is what's "wrong" and what would be "right"?
when i directly did ssh from my windows system to remote linux system "testhy" through PUTTY, my session was got disconnected after 1 hour(i connected at 10:15am and session got disconnected at 11:15am).
But when i first PUTTY to some other Linux system and did ssh from there to "testhy", session was not disconnected. does the problme with PUTTY on my windows system? but others also getting same problem.
i could not figure out whether the problem is with SSH server or SSH client? is there any specific SSH configuration for PUTTY.
There's several timeout settings like the one in the login shell (e.g. "tmout" in 'man bash') and SSH (search 'man ssh_config' for "timeout") you could check for?
i have tried it by setting "keepAlive" for 5-min in putty and stopped firewall on server system(sshd), but still both idle and using sessions are becoming inactive after 1-hour. please suggest me if anything else need to be checked.
I can only suggest to run your sshd with triple "-d" and "-v" and do the same with a GNU/Linux client, resulting in lots of logging which together with syslog information around the time of forced logout and maybe searching for running applications or scripts that force logout could show some lead. With the amount of information provided it'll just be searching for clues. At least from my point of view.
My PuTTY Log says - "Event Log: Initiating key re-exchange (timeout)", so I think problem is with key re-exchange. when key exchange is initiated by ssh client(PuTTY) testhy(server) is not responding in time and hence connection becomes inactive.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.