RDP external prompts, embedded does not
I'm a historic user of RDM. Finally got around to introducing it to my current workplace. I've found the following:
New RDP entries using a credential repository entry appear to only parse the password successfully via the embedded RDP client. When attempting to launch the session "normally" via external MSTSC application, the password prompt always appears indicating the password was incorrect.
It appears it parses the domain and username successfully, as they appear in the dialog box but the prompt itself indicates a bad username or password .
Is this a known bug or is there a work around ? Before deploying this to my team I'd like not have to say " HEY heres this great new product but its got bugs !"
All Comments (2)
Hi,
It's not a bug it's just the way that we supply the credentials to mstsc. With the ActiveX it's easy we can set the username, domain and password fields. With mstsc we have to simulate the way the application read the credentials. I know that some OS prefers to have the username like this: Domain\UserName. Could you try it?
David Hervieux
Okay thank you I'll keep it in mind. The world hasnt ended, I did fiddle with some of the "tools" configuraable options and called teh credential repository from there. I 've undone those changes and now it connects fine externally.
I'll keep your solution to the problem in mind should it re-occur, I'm still populating the db for the team here.
Thanks for the prompt response.