Hi! I have windows server 2008 R2 and vmware server 2.0.1 on it. I also have 2 VM with linux (SSHd is enabled). But when i use Putty to connect to VM i receive an error "Network error: software caused connection abort". I can connect with telnet to 22 (sshd port). Firewall is disabled, the server not in domain. I can connect from 1 VM to 2 VM (with ssh). I feeling that problems in Windows server 2008 R2 policies, because i have the same solutions on Windows Server 2008 and 2003, and there are no errors with putty there. Maybe anyone know how to solve that problem.Best regards

Hi, Please check if the following information can fix the issue for you. 4.13.1 Using keepalives to prevent disconnection If you find your sessions are closing unexpectedly (most often with `Connection reset by peer') after they have been idle for a while, you might want to try using this option. Some network routers and firewalls need to keep track of all connections through them. Usually, these firewalls will assume a connection is dead if no data is transferred in either direction after a certain time interval. This can cause PuTTY sessions to be unexpectedly closed by the firewall if no traffic is seen in the session for some time. The keepalive option (`Seconds between keepalives') allows you to configure PuTTY to send data through the session at regular intervals, in a way that does not disrupt the actual terminal session. If you find your firewall is cutting idle connections off, you can try entering a non-zero value in this field. The value is measured in seconds; so, for example, if your firewall cuts connections off after ten minutes then you might want to enter 300 seconds (5 minutes) in the box. Note that keepalives are not always helpful. They help if you have a firewall which drops your connection after an idle period; but if the network between you and the server suffers from breaks in connectivity then keepalives can actually make things worse. If a session is idle, and connectivity is temporarily lost between the endpoints, but the connectivity is restored before either side tries to send anything, then there will be no problem - neither endpoint will notice that anything was wrong. However, if one side does send something during the break, it will repeatedly try to re-send, and eventually give up and abandon the connection. Then when connectivity is restored, the other side will find that the first side doesn't believe there is an open connection any more. Keepalives can make this sort of problem worse, because they increase the probability that PuTTY will attempt to send data during a break in connectivity. (Other types of periodic network activity can cause this behaviour; in particular, SSH-2 re-keys can have this effect. See section 4.19.2.) Therefore, you might find that keepalives help connection loss, or you might find they make it worse, depending on what _kind_ of network problems you have between you and the server. Keepalives are only supported in Telnet and SSH; the Rlogin and Raw protocols offer no way of implementing them. (For an alternative, see section 4.13.3.) Note that if you are using SSH-1 and the server has a bug that makes it unable to deal with SSH-1 ignore messages (see section 4.24.1), enabling keepalives will have no effect. For more information, please refer to the following links: http://winscp.net/eng/docs/message_software_caused_connection_abort http://the.earth.li/~sgtatham/putty/0.59/puttydoc.txt If the issue persists, please contact Putty support for further assistance. As you know, Microsoft has less information regarding third party software. Thanks for your understanding! Regards, Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.