How to use the 'built in SSH shell' (as opposed to putty)

Do you use the Rebex SSH or just the one call SSH Shell?

The one just called 'SSH Shell' (with the monitor logo with SSH written in it), not Rebex or putty.

It's strange. This one is based on Putty. I will ask Hubert to verify if we can enable a debug level.

I tried enabling logging but no log file gets written either. There's also nothing to see in the RDM Application Log.

Hello,

Could you try enabling the verbose option in the SSH Shell entry, as well as the logging in event mode rather than the printable output?

Regards,

Could you try using RDM 32 bits instead of 64 bits on both the computer with the crash as well as the one with the connection never opening? Thank you.

Regards,

Ok, I tried a few machines switching 32 and 64 bit. The results:

Terminal server (Windows 2012):
32-bit works
64-bit crashes with log (see above)

Laptop 1 (Windows 10):
32-bit works
64-bit does nothing (see above)

Laptop 2 (Windows 10):
32-bit works
64-bit does nothing (as above but different laptop)

So it appears you hit the nail on the head suspecting 64-bit RDM to be the problem. That makes me wonder: is the 32-bit version 'preferred'?

Any idea if and when this can be fixed (yet)?

http://help.remotedesktopmanager.com/index.html?tipsandtricks_32bit_vs_64bit.htm The 32 bit executable is preferred unless you run into memory issues with embedded RDP connections.

The terminal used for the SSH Shell is a 32 bits-only DLL, so if we want to use it in RDM 64bits, we have to use an external program (embedded32.exe) to embed the terminal, then embed that program into RDM. I'm unable to reproduce it in our environment, but there seems to be an issue with embedded32 itself, so we'll investigate.

Could you try something:
1. Open RDM 64 bits with one of the machines where it doesn't work (crash or do nothing)
2. Go in the Help tab, then open the Profiler
3. In the Debug Only tab, change the debug level to Embedded32. Keep this window open.
4. Open the SSH Shell connection. It should log to the profiler the steps made to open the connection through embedded32. Could you post this here or send it to me at hmireault@devolutions.net ? Thank you.

Regards,



Regards,

Starting process
PID: 5800
MainWindowHandle: 0
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Wait 100ms
Process has exited.

Sorry for making you go through so many verifications, but could you paste the contents of your RemoteDesktopManager.debug file? This is where the profiler logs its outputs. There should be a few more things in there in regards to the embedded32 logging, as I checked in the code and the Profiler window doesn't seem to output what comes from Embedded32.exe directly to the window since it comes from another process.

Regards,

see email

I looked through the logs you have sent me. I'm still not sure what's causing the issue but there might be something that's corrupted with Embedded32. Would it be possible for you to try the latest beta of RDM as a test to see if you still encounter these issues?

As a temporary workaround, using the 32 bits version of RDM would work. As mentionned, if you don't encounter memory issues, there is little reason to use RDM 64 bits.

Regards,

Sure, no problem. I'll keep you posted.

Hello Bas,

We found an issue with the terminal in 64 bits. There will be a fix in version 11.1.0.0. When it's out, could you give it a try and see if it works on the machines where it previously didn't? Thank you.

Regards,