SSH connnections from HP-UX to Windows 2000

[Robin King_1]

I have set up a number of scp commands in cron that allow me to transfer data securely between HP-UX servers. This was a pretty simple task, and I've not had any problems.

I'm now trying to do the same between HP-UX 10.20 and Windows 2000.

To try out the connection, I've been using:

/opt/openssh37/bin/ssh -p -l

I'm prompted for @ password, but it will not accept the password. "Permission denied, please try again."

The O'Reilly SSH Book mentions that password authentication can "mysteriously fail" if PAM isn't configured to use SSH. I'm a bit stuffed if this is the case, as PAM isn't supported on 10.20. I'm doubtful of this to a certain extent because I can connect betweem HP-UX servers without any problems.

Has anyone successfully got SSH working between HP-UX and Windows 2000 Server?

Any suggestions would be great, as I'm working to a tight deadline.

Thanks!

[Ganesh Babu]

Check this one..

http://status.lsu.edu/security/ssh.html#server

Ganesh

[Robin King_1]

Ganesh, are you suggesting installing a commercial server on Windows 2000?

[Matti_Kurkela]

What are you using as SSH server on Windows?

We have OpenSSH clients connecting to ssh.com SSH server version 3.2.0 on Windows 2000 server. Works fine, although I heard from the local Windows administrators that setting up the SSH server for Windows was rather challenging.

When access is denied, Unix sshd usually writes a syslog message that tells exactly why access was denied. On Windows, the equivalent place would be the Event Log system. Check there, and also check if the Windows user account has locked itself because of too many failed attempts.

Because Windows and HP-UX have very different user environment conventions, it may not be obvious where SSH key files and other per-user things should be placed. On our Windows-SSH server, the correct place was:
C:\Documents and Settings\\sshd2


The note about PAM configuration in the O'Reilly book is not really applicable to your case: only ssh server (sshd daemon) needs PAM. The ssh client won't know or care anything about PAM. Because your ssh connections between HP-UX servers are working, you obviously are not having that problem.