Problems connecting using SSH

mrw · Post by **mrw** » Thu Oct 03, 2013 6:07 am

Hi,
I´m trying to connect to a HP SAN using SSH to get some info regarding disk-status.
But when I run the test I get this error: "RMA: 301 - Protocol error. Communication failed. Probably firewall issue."
I know that the server that the RMA lies on can connect to the SAN. If I use Putty it works fine. And also if I alter the username in Connection Manager for the HP SAN I get the error "Incorrect username or password". So the RMA is trying to connect and is getting a reply.
Any ideas on what the problem can be? In Putty I can see it´s using SSHv2 and AES-256 with SHA1.
Do I need to store the SSH fingerprint somewhere perhaps?

//Andreas..

KS-Soft · Post by **KS-Soft** » Thu Oct 03, 2013 9:17 am

RMA version?
Does your server support AES-128?
(RMA does not use AES-256)

Regards
Alex

mrw · Post by **mrw** » Fri Oct 04, 2013 2:24 am

RMA version: 4.62

And in Putty I can´t select to use AES128 or 256 but just AES and that creates a connection with AES256. If you know how to force AES128 in Putty please let me know.
And I have also tried to connect with 3DES(both ssh1 and ssh2) and Blowfish and that works fine with Putty.
Is there a way to force the SSH method that the RMA uses?

KS-Soft · Post by **KS-Soft** » Fri Oct 04, 2013 8:45 am

Is there a way to force the SSH method that the RMA uses?

Client and server negotiate, send list of supported encryption methods and select best supported method...
Could you use sniffer (WireShark) to check network traffic between RMA and server?

Regards
Alex

mrw · Post by **mrw** » Mon Oct 07, 2013 2:06 am

I have emailed at wireshark-output to you.
I can´t see any obvious cause of the problem, but hopefully you can.