I had a rather odd problem with a connection today.
It worked fine previously but here is a list of things I've tried and what happened:
- Connect with correct credentials and host in format IP:port /admin with rdp, not using RDM: connects without issue.
- Connect with correct credentials through RDM: Gives the can't reach remote computer error.
- Connect with wrong credentials through RDM: Shows the incorrect credentials prompt. Signing in with correct credentials here gives the same error as above.
- Checking the Restricted admin checkbox under the Advanced tab then connecting with correct credentials through RDM: Connects but gives following error message in the session "Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced.".
Could it be because of the /admin part? RDM auto removes it and the port from the host field but as far as I can see only the port info is inserted elsewhere.
I am rather new to RDM and remote desktop in general, so what is mentioned above is the full extent of my troubleshooting, except for refreshing RDM between changes.
Thanks in advance
Hello,
We had another customer with a issue similar and in his case the credential use was a external credential. Have you entered the credentials directly in the session or you are connected to a Credentials repository?
What version of RDM are you using?
What type of database are you connected to?
Best regards,
David Grandolfo
I'm connected to an SQL Azure database and using RDM Enterprise edition 13.6.2.0 64 bit.
Normally I use credential repositories as there are 2 users for this connection but I just tested it with credentials set to default and then setting them directly in the session.
The result was the same, it claimed it couldn't reach the remote computer.
If I check the 'Always ask password' box and type the password manually when I open the session it connects without issue.
After some more testing I found a solution that was incredibly simple.
I just had to check the 'Open console (Admin mode)' checkbox on the session.
Thank you for your time
Perfect,
Thanks for the follow up, if you need further help please let us know.
Regards,
David Grandolfo