Forum / Remote Desktop Manager Mac - Support

SSH problem with Cisco SSH-1.99-Cisco-1.25

  • Create an Issue
  • Cancel

I'm trying Remote Desktop Manager for Mac OS. The configured SSH Shell connection don't work. I've found a trick to make it work.... Edit Entry>SSH Shell>Advanced and select Verbose, set to 2 and select Enable logging. This is the only the way to work.

Clock2 yrs

Hello,

I'm moving your post to the Mac thread since you're using RDM Mac.

What version of RDM are you using?


Best regards,



Mark Beausejour

signaturesignature

Clock2 yrs

Hello,
I'm using 5.2.0.0

Clock2 yrs

Hi,

Only with level 2? Can you get us the log file generated? You can send it to me via email: xfortin@devolutions.net

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs

yes, only level 2

Clock2 yrs

Hi,

And how about the log generated through the "Enable logging" option? Can you send it to me?

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs

Hi again,

Just to make sure.

If you disable Verbose and Enable logging, your connection fails to open successfully?

If you set the Verbose mode to anything else than 2 (1, 3 and 4), it still fails?

The log you've sent me, for which scenario was it?

Could you send me the log with those configurations:
Verbose: enabled
Enable logging: true
Verbose level: 4

I'd like to inspect the log of a failing session.

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs

I have reproduced this exact scenario. The session works from Windows RDM, but not Mac. It opens to a black screen and never connects. If you enable verbose 2, It hangs at 'ssh_analyze_banner: SSH-2.0-Cisco-1.25'. If you enable logging with verbose 2, it connects normally.

Attached are verbose 1-4 logs as requested above.

verbose1.log
verbose2.log
verbose3.log
verbose4.log
Clock2 yrs

Hi Brad,

Thanks for the log. We look into them and see what we can find.

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs

Just tried 5.3.0, and unfortunately this issue still exists.

Clock2 yrs

Hi Brad,

We still haven't figured out this specific issue. We're working on a new engine for our SSH Shell session that might solve this issue or, at the very least, make it a lot easier to troubleshoot. That being said we still have an engineer looking into this.

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs