Windows 7 - SSH on windows 7?

This works as I just installed it. I have Windows 7 x64 professional

OpenSSH for Windows - Browse /OpenSSH for Windows - Release/3.8p1-1 20040709 Build at SourceForge.net

Thats confusing

Are you runiing as a service or as an application.

I think I know what might be going on....

This is just a guess mind when i run it as a application under the user name of brian it works and remembers settings
Then I ran it as an application as administrator and it worked but had lost the settings
and the same as when I run it as a service...

I think it might be windows 7 mapping the file request dependant ho you are logged it.

Anyway thats my 2 pennies worth.

Update
Just started it as a service with my account rather than local system and it works.... so that seem s to confirm my guess. as you have to configure it from a front end as a user so therefore local system cannot find the configured files.

I installed the client only, not the ssh server. However, both work just fine. I then open a dos prompt and type: ssh user@ipaddress and I am in.

mreine, the problem isnt the client, I guess thats why you havent had any issues
I now know not to run it as localsystem I will create a user SSHXXX and give it a complex password and only use that user to configure ssh

have fun

brian

I tried FreeSSHd and had the same results. As long as you were logged into the server desktop and had it running as a docked applet, you could login to the machine remotely over ssh. However, if you logged out of the desktop (which closes the interactive application) and just left it with the freeSSHd service running, I could never get it to connect. Actually, I DID finally get users I added to connect, but it would immediately disconnect because something about the users privileges (with the sshd server running as a service) were not right. I gave up on freeSSHd.

I tried MobaSSH, and at first I had the same issue that I couldn't login. However, realize that the usernames are case-sensitive! ssh administrator@somewinserver.whatever will NOT work...ssh Administrator@somewinserver.whatever WILL work. Once I figured out that the admin username was case-sensitive, the rest was really easy.

The ssh key authentication works fine too for password-less logins....just create a .ssh directory, copy the users rsa.pub key into that directory as a file called authorized_keys. Both ssh and scp work fine.

Same as CopSSH mentioned above, you get the (Linux) bash shell when you login. If you want the Microsoft Windows command line instead, just type "cmd" and you'll get cmd.exe shell instead. Windows command that are seperate programs will work from the bash shell (like tasklist, taskkill, net start, net stop, etc.)...commands that are part of the cmd.exe shell (like copy, dir, del, etc.) obviously will not work from the bash shell.

HTH,
Dave

I'm now on the latest version of CopSSH as mentioned on page 1 of this thread, and to add to the above, you can set specific users to default to the bash prompt or the Windows command shell, as you prefer. I generally leave it as bash, because I know my way around bash as well as cmd.exe, and I also know how to switch between the two. It also helps that most people who might see my shell open on the machine won't know what a bash shell is or does, which is "security through obscurity" but hey, every little helps :-)