I have a strange problem: When I'm using PuTTY with SSH connecting to a Linux server hosted in VMware on my local Windows 7, I often get the error saying "Network error: Software caused connection abort"
and then the PuTTY SSH window is inactive. Usually I can login in the server with PuTTY and do something, but after a random time (about one or two minutes) I get that error. And sometimes I even can't login, getting an error saying timeout.
I guess there's something wrong with my VMware Player, because I have another Ubuntu desktop hosted in VMware as a code repository server, and it more often than not has a timeout error when I do an SVN update/commit. However, I also guess Windows 7 has some quirk because the same Ubuntu server hosted in VMware as a code repository works very well when on Windows Vista! It seems all the bad things happen after I moved from Windows XP to Windows Vista and then Windows 7!
What could be the reason for this problem and how can it be fixed?
Supplement:
I did a Google search and applied all methods to help, including:
- Enable sshd
TCPKeepAlive
- Set sshd
ClientAliveInterval
to900
andClientAliveCountMax
to3
- Set the PuTTY connection setting 'seconds between keepalives' to
5
.
But these all don't work! And the SSH session in PuTTY still breaks after sometime!
I turned off both the Linux server firewall and Windows 7 client firewall, but login still times out! It is really annoying!
It seems sometimes I can log in, but sometimes login times out! I really don't know why. It drives me crazy!
One thing I have to mention is that when I'm using PuTTY SSH connecting to a remote server, and it's all OK!
When I failed to log in, ping failed too! But, how can that happen? I use VMware player to host the Linux server on my local machine!
No comments:
Post a Comment