Hi
With SSH Shell and private key file , the RDM app crash
the are no problem on on SSH shell rebex
but i ve to use SSH Shell for X11 forwarding
Thanks
Julien
My version of RDM : 11.1.7.0
Hello Julien,
Are you using RDM in 32 or 64 bits? If you are using it in 64 bits could you try it in 32 bits?
Does it happen if you use X11 forwarding only or does it also happen without using it, just by specifying the host + credentials + key?
We'll investigate and try to reproduce this issue.
Regards,
Hubert Mireault
Forwarding yes or not dont change the issue
Problem it s only on 32Bits with host + login credential + keyfile
no problem if host rejects the key
It s seem to works on 64Bit but there are problem with the windows
jupcchess.pub
jupcchess.ppk
2016-03-08_10h11_00.png
Hello Julien,
I used the private and public keys you attached to your post and set them on one of our machines, and it works perfectly.
Are you running RDM as administrator?
Do you have a machine with no private key (just username + password) to connect to? Does that work?
Do you experience this issue on other workstations?
Regards,
Hubert Mireault
Are you running RDM as administrator?
No but same issu as admin
Do you have a machine with no private key (just username + password) to connect to? Does that work?
yes I use many machine with RDM without problem
Do you experience this issue on other workstations?
not yes but tomorrow i could try it
I have test with other host on centos or debian and i have the same problem
It s possble to run RDM on debug mode foir send you a debug trace ?
My windows event :
Nom de l’application défaillante RemoteDesktopManager.exe, version : 11.1.7.0, horodatage : 0x56d64186
Nom du module défaillant : ntdll.dll, version : 6.1.7601.19135, horodatage : 0x56a1c6fa
Code d’exception : 0xc0000374
Décalage d’erreur : 0x000cf70b
ID du processus défaillant : 0x12a4
Heure de début de l’application défaillante : 0x01d17aa47f613113
Chemin d’accès de l’application défaillante : F:\rdp\RemoteDesktopManager.exe
Chemin d’accès du module défaillant: C:\Windows\SysWOW64\ntdll.dll
ID de rapport : 44505d9d-e698-11e5-89d5-d4bed998b5a2
Hello,
I'm intrigued as to why it would work with certain machines but not others. Could you export your faulty entry (right click > export > Export selection (.rdm)) and send it to me at hmireault (at) devolutions.net? Be sure to remove sensitive information like IP address and credentials. If there are any logs, you can find them in RDM in the Help tab > View Application Log.
Our terminal is based on PuTTY, so you could try the creating a session on PuTTY with the same settings and seeing if it works http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
You could also try using sfc /scannow in an administrator command prompt, there might be an error within ntdll.dll https://support.microsoft.com/en-ca/kb/929833
Regards,
Hubert Mireault