topic Re: SSH Windows Client Cannot Connect to HP-UX SSH Client/Server in Operating System - HP-UX

SSH Windows Client Cannot Connect to HP-UX SSH Client/Server

RIACDC — Thu, 30 Jun 2005 11:10:18 GMT

Gentleman,

Anvil corrected my issue with using secure shell to login into an HP-UX client to server and reverse. I can successfully login using ssh fom HP-UX client to HP-UX Server, but I new issue has surfaced.

I just attempted to login into this server using a windows based ssh client, but this client fails to connect to the server. Is there a similiar command set to faciliate windows ssh client to HP-UX server connectivity. My windows client can ping my HP-UX ssh server.

Re: SSH Windows Client Cannot Connect to HP-UX SSH Client/Server

RAC_1 — Thu, 30 Jun 2005 11:16:55 GMT

Another thread by you. Just because windows system can ping to hp-ux system does not mean that ssh/telnet will work. How you have configured the ssh client on windows. Which client?? What is the method that you use to authenticate ssh??

Do you see anything in syslog?

Again, on hp-ux server stop sshd and start it as follows.
/usr/sbin/sshd -ddd
Now try connecting to hp-ux server using ssh client. Post sshd log.

Anil

Re: SSH Windows Client Cannot Connect to HP-UX SSH Client/Server

Devesh Pant_1 — Thu, 30 Jun 2005 21:41:38 GMT

Please provide the ssh client you are using on the windows side since there are some that do not support ssh2.
Also, were you asked to accept the public key when you tried to connect ?

Devesh

Re: SSH Windows Client Cannot Connect to HP-UX SSH Client/Server

Michael Selvesteen_2 — Fri, 01 Jul 2005 01:00:25 GMT

Please check the following

1. Check whether your windows client connect to correct port where SSHD runs. Default is port 22.

2. Ensure the authentication type you selected in windows client is supported by SSH server.

3. If you use public key, check that your key type is accepted by the server

4. Check for any DNS lookup problem

5. HP Secure Shell by default supports only SSH protocol version 2, check whether your client is configured to use protocol version 2

6. Did telnet works from your client?

8. Check whether your host is allowed to login. Server may have access lists.

7. Still have problems, send the server and client debug messages.

All the Best

Re: SSH Windows Client Cannot Connect to HP-UX SSH Client/Server

Makesh Annamalai — Wed, 20 Dec 2006 10:37:00 GMT

Same issue here

Please find the Output after running the cmd as mentioned...

# /usr/sbin/sshd -ddd
debug2: load_server_config: filename /opt/ssh/etc/sshd_config
debug2: load_server_config: done config len = 280
debug2: parse_server_config: config /opt/ssh/etc/sshd_config len 280
debug1: TOKEN IS protocol
debug1: TOKEN IS kerberosauthentication
debug1: TOKEN IS usepam
debug1: TOKEN IS x11forwarding
debug1: TOKEN IS x11uselocalhost
debug1: TOKEN IS subsystem
debug3: RNG is ready, skipping seeding
debug1: sshd version OpenSSH_4.3p2-hpn [ HP-UX Secure Shell-A.04.30.017 ]
debug3: Not a RSA1 key file /opt/ssh/etc/ssh_host_rsa_key.
debug1: read PEM private key done: type RSA
debug1: private host key: #0 type 1 RSA
debug3: Not a RSA1 key file /opt/ssh/etc/ssh_host_dsa_key.
debug1: read PEM private key done: type DSA
debug1: private host key: #1 type 2 DSA
debug1: rexec_argv[0]='/usr/sbin/sshd'
debug1: rexec_argv[1]='-ddd'
debug2: fd 4 setting O_NONBLOCK
debug1: Bind to port 22 on ::.
debug2: fd 4 setting O_NONBLOCK
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
debug1: fd 4 clearing O_NONBLOCK
debug1: Server will not fork when running in debugging mode.
debug3: send_rexec_state: entering fd = 8 config len 280
debug3: ssh_msg_send: type 0
debug3: send_rexec_state: done
debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 8
debug1: inetd sockets after dupping: 4, 4
setsockopt SO_KEEPALIVE: Socket operation on non-socket
debug1: getpeername failed: Socket operation on non-socket
debug1: get_remote_port failed
#

Someone help me!!!

Re: SSH Windows Client Cannot Connect to HP-UX SSH Client/Server

Christian Tremblay — Wed, 20 Dec 2006 12:05:26 GMT

If you have generated your key pair in Windows ex: putty keygen, the format is different from the unix format.

There are 2 comments line ( the first and last if I remember well) that have to be deleted and the windows generated key is not on a single line ( it has cr line feeds in it)you need to delete those too)in order for the key to be ONE single line.

Chris