I have a strange problem: when I'm using putty 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 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 vmare as a code repo server and it more often than not has a timeout error when I do a svn update/commit. However, I also guess windows-7 has some quirk because the same ubuntu server hosted in vmware as a code repo works very well when on windows-vista! It seems all the bad things happen after I moved from xp to vista then win7!
Can anyone give me some tips and hints? Thanks in advance!
Supplement:
I did a google search and applied all methods to help, including:
- enable sshd TCPKeepAlive
- set sshd ClientAliveInterval to 900 and ClientAliveCountMax to 3
- set 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 is still timeout! Really annoying!
It seems sometimes I can login but sometimes login is timeout! 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 it's all OK!
When I failed to login, ping failed too! But, how can that happen? I use vmware player to host the linux server on my local machine!
