Issues using SSH shell session from a Windows 8.1 box as a non-admin group User
Issues using SSH shell session from a Windows 8.1 box as a non-admin group User
Hello, We are new to the RDM product and are just setting it up. We setup the enterprise server and data source on a Windows 2012 R2 box and then installed the RDM client on a Windows 8.1 box. When we setup the client we did so under an Administrator account on the box and then configured all of our sessions, etc under that and tested and everything works great.
We then logged out of the Windows admin user and logged in as a regular Windows user. We can open the RDM data source, as an RDM administrator, and see all the sessions, etc. However when we attempt a SSH shell session we just get a black screen. No prompt for credentials or anything. If I change the session to a Putty session it does work, so communication to the device is fine. If I try a web based session that works fine as well.
I have tried giving normal Windows users total control over the devolutions directories but that didn't make any difference. If I log out of windows as the normal user and back in as the Windows admin user everything works fine. At a loss here...
All Comments (4)
Hi,
Could you verify if you get any error in the application logs located in the Help ribbon?
David Hervieux
David, sorry for the late response. No, the last application log entry is on 4/2 and is reference to upgrading database for data source.
I should clarify as well, I am using the same RDM user (which is also an administrator role user), just a different Windows user that has different security rights. One use has Administrator rights over the box, which works perfectly, and the other just has standard user rights, which does not. RDP and HTTP sessions work just fine, just not the embedded ssh which is what I want to use. Thanks!
Hi,
It looks like the the connection is blocked somewhere. Could you try to add a exclusion in your Anti-Virus?
David Hervieux
Hi,
I don't think it's possible to copy it for security reason. It use the Windows encryption to secure the file and this is user/machine specific.
David Hervieux