Hi, I'be been checking you forum and I have found several notes with similar problems, however cant find a solution for this by looking at the others, could someone help me? I'm using SSH Secure Shell for Windows v 3.0.0 and when I attempt to connect to a Fedora system with OpenSSH, I successfuly log in, give my password, and after about 10-15 minutes it kicks me out with the message "The connection was closed by the server" on other computers happens the same thing except that the connection lasts less than a minute. I have done a ping -t while the connection was active, and it appears that the connection is never lost between the systems, I have also patched OpenSSH in the Fedora system here:
<broken link removed>
with the OpenSSH 3.9p1 securID patch. Also after i have been kicked out I cant log in again for a while because the SSH Secure Shell tells me that the IP address is "unreachable" Could someone please help? Thank You
So, the ping continues to be successful but each attempt to connect via SSH tells you that the host is unreachable?
The issue is almost certainly network related and not related to your client or server or any configuration or patch applied to either.
The reason you can't find a solution on this site is that network problems can arise from so many different places. Your network conditions are likely to be very unique and someone else's solution may not apply to you.
What you need is a method to begin isolating the source of the problem.
For example, to eliminate your client software a the potential source of the problem, try running two different SSH packages at the same time. If only one has this problem, then you know it is software related. If they both fail at the same time in the same way, then it is network related.
If you identify that it IS a network issue, and a 'ping -t' continues to succeed, start a second ping and see if it gets the 'unreachable' problem or does it succeed as well? Is the IP address in the first ping the same as the one in the second ping? Ping *should* get the same 'unreachable' message as the SSH connection. If it does not, then that is where you need to start your investigation.
Firewalls could be involved. I'd also suggest using keep-alive functionality if your client has one. This forum is for Celestial Software users, so I could recommend you try AbsoluteTelnet and see if it has the same issues.
Without more detailed info, I'm not sure how much help I can be.
Did you ever get this resolved?
Brian
Hello?