HP-UX SSH to Linux RH

[Roger Gomes]

Hi All,

I'm try to connect via ssh from HP-UX to RH and the connection hangs. Everithing was working but some times ago no more !!

SSH HP-UX -> RH

Using debug in SSH I see this :

OpenSSH_4.1, OpenSSL 0.9.7e 25 Oct 2004
HP-UX Secure Shell-A.04.10.002, HP-UX Secure Shell version
debug1: Reading configuration data /opt/ssh/etc/ssh_config
debug3: Seeding PRNG from /opt/ssh/libexec/ssh-rand-helper
debug2: ssh_connect: needpriv 0
debug1: Connecting to XXX.XXX.XXX.XXX port 22.
debug1: Connection established.
debug1: identity file /home/roger/.ssh/id_rsa type -1
debug1: identity file /home/roger/.ssh/id_dsa type -1
ssh_exchange_identification: read: Connection reset by peer


But I can login in this way RH -> HP-UX.

Someone can help-me ?

10ks.

[Mel Burslan]

if you are the administrator of both the HPUX and the RH boxes and changed absolutely nothing (as in a software upgrade or patching) and it stopped working for no reason at all, you should talk to the people who control your routers and firewalls. Connection reset by peer is usually indicative of your source IP address not being liked by the target server. Unless you did some ipchains modification on the target (RH) side and blocked some addresses accessing your server, I'd probably blame the firewall.

[Matti_Kurkela]

Was that all of the debug output of SSH, or did you omit something?

The connection is established, then rudely disconnected almost immediately afterwards. This quick disconnection might be caused by a tcpwrapper/libwrap -style access control at the application level. Firewalls usually just ignore the connection attempt ("drop the packet") and let the client time out by itself.

Examine the files /etc/hosts.allow and /etc/hosts.deny on the RH host. If the access is allowed/denied based on host names, verify that the RH host can resolve the hostname when given the IP address: this is called "reverse DNS lookup" and it is often overlooked in DNS server management.

To test it, run "nslookup HP.UX.IP.address" on the RH host and see if you can get back an answer that includes the name of the HP-UX host.

MK

[Steven E. Protter]

Shalom,

suspects:

1) Software upgrade/bug one side or the other
2) permissions problems on key .ssh files
3) Network firewall issues.

SEP