I have followed thse instructions for setting up an SSH Server on Windows 7 without problem many times: http://www.geek-republic.com/wp-content/uploads/2009/02/securing-windows-remote-desktop-with-copssh.pdf The only difference is that I am using PuTTY Portable instead of a desktop version. Recently I have installed Windows SBS 2011 and done a clean install on all the Windows 7 machines. All the Windows 7 machines on on a domain instead of a workgroup - that is the only difference. Installing the SSH Server and creating the keys have been flawless just like before, however this time when I try to log in using Putty, it closes the shell right away. Searching google for a couple of days did not come up with anybody even having this problem, let alone how to solve it.

Try run as administrator ....

The SSH Server has been started by "run as administrator" and putty has been started by "run as administrator". Still closes right away. I have tried copSSH and FreeSSHd with the same results.

The only difference is that I am using PuTTY Portable instead of a desktop version. Installing the SSH Server and creating the keys have been flawless just like before, however this time when I try to log in using Putty, it closes the shell right away. Since we're not familiar with this PuTTY Portable, I suggest contact their support for further research. It seems the issue is related with Putty. Thanks for your understanding and cooperation! Regards, MiyaThis posting is provided "AS IS" with no warranties, and confers no rights. | 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.

I run putty with no difficulty on Windows 7 Renee

I had to play musical computers so everything (SBS and W7) have a clean install. Before I put a W7 machine on the domain, I installed the newest version of CopSSH 4.10, went made new keys, blah blah blah, and this time it worked. Afterwards, I changed WORKGROUP to the domain, restarted and it seems to be working now. My only guess is that either the ssh sever needed to be updated or it needs to be installed while on a workgroup.