RDM 6.6.0.0 - Credentials Issues

RDM 6.6.0.0 - Credentials Issues

avatar

I used the prior version of RDM to access approximately 30 servers via RDP without any issues. I recently upgraded to RDM 6.6.0.0 and the session entries and credentials migrated just fine. However, when I access a Win 2003 server via RDP, the credentials are not being passed and the server is requiring I log in. This worked fine in the prior release and it works fine with Win 2008 servers.
I've tried creating new credential entries and nothing seems to work. Any ideas?

All Comments (23)

avatar

Hi,
Could you verify if you have the problem in external or embedded mode?

David Hervieux

avatar

Both external and embedded. If you want to connect to my laptop to review, I have a GoToAssist account that you can connect to.

avatar

I'm not sure it will help at this point. I have some questions before. If you use mstsc.exe directly does it work?

David Hervieux

avatar

If I try and run mstsc and I select my Win 2008 server, I can see that it has saved credentials and it logs in just fine. If I select a Win 2003 server, I can see there are no saved credentials. When I select to save the password and then try again, the credentials are passed. After I save the password via mstsc and tried again through RDM, it worked. That is a good workaround, but isn't the concept of the credentials entry to pass the credentials that so I wouldn't have to save it through MSTSC?

avatar

Hi,
I was asking that to find some clue about the problem. If I understand correctly when you save the credentials in the database (shared password) it does not work but if you save them locally (with mstsc) it works?

David Hervieux

avatar

Correct, but the odd thing is that once I saved the password using mstsc, I can now log in through RDM without having to log in.

avatar

Could you export me the session and send it to me? Do you reproduce it on multiple Win 2003 machines or just this one?

David Hervieux

avatar

It happens on all Win 2003 servers. I have a number of clients that each have a number of servers - some 2003 and 2008. All the 2003 servers have this issue across all clients.
I've attached the export of one of the 2003 sessions with credentials. You won't be able to connect unless you VPN in first, but if you want to see it fail, we can do a GoToAssist session.

KEHOE-WEB-2.rdm

avatar

Thank you. I don't need to connect. I just want to see if I can find a specific setting.

David Hervieux

avatar

Hi,
I have seen that you use the Credential repository. If you enter the username and password directly in the session, does it change anything?

David Hervieux

avatar

If I use Session Specific Credentials, it works if I save the password on the local computer. If I try and save the password in the database, it does not work.

avatar

I suspect one thing. Is it possible to prefix the username with the domain name?

Domain\Username

I'm sorry to ask you so many question. It's because I don't understand what could be the problem since it work fine everywhere else.
edited by dhervieux on 11/22/2011

David Hervieux

avatar

That didn't work. I Opened the Credential Entry and tried two different ways...
1 - In the User Name box, I typed PRINCECASTLE\BKD and left the Domain box empty. I typed the password in as well.
2 - In the User Name box, I typed PRINCECASTLE\BKD and entered PRINCECASTLE in the Domain box. I typed the password in as well.

avatar

Is it possible that the Credential repository is corrupt? Is there are way to rebuild it? I can delete all the entries and try again, but I assume something more drastic is necessay since I tried deleting and re-entering a single Credential entry.

avatar

i don't think it's corrupted because you have tried to enter it directly and it does not help. Maybe the application is unable to save it in the Windows Credential Vault but you said that in embedded mode it does not work too?

David Hervieux

avatar

I think that tomorrow I will accept your offer an connect on your machine

David Hervieux

avatar

I can available today until 9:30am central, then again later today after 3pm central. Let me know what time works for you.

avatar

Hello
Im a new User of the RDM. Great Tool!!! Back to Topic:
I have the same problem. I think i know the what the problem is:
I create a new RDP Session
=>Server, User, Domain => Save Credentals.

Now, if i connect directly (double click RDO Session) then is the Domain missing. If I click "open session (prompt for Credential)" then is the Domain there.
Look here the Screenshots:


The configuration:


---------------------------------------

The Direct Login:



---------------------------------------

The Login with credential Prompt


---------------------------------------

As you can see, with the prompt the Domain is set, with the direct login it doesent is set. Thats the reason why we cant login, cause the domain name is missing.

Regards

Co1m
edited by Co1m on 12/2/2011

avatar

Hi,
We have found the problem and this issue was related to this faq:

http://remotedesktopmanager.com/remotedesktopmanager/Support/FAQ#g7

For the domain problem I'm not sure it's related but could you try to included it in the name?

Domain\Username

David Hervieux

avatar




Hello
First I added the Domain to the Username (additonally to the Domain). Same behavior.
Then i deleted the Domain name and tried the same thing. Same behavior.

What else could it be?

Kind regards

Daniel alias Co1m

avatar

Could you try to see if this work in embedded mode?

David Hervieux

avatar

Hi
it worked with the embedded mode.
What could be the Problem?
regards

Daniel

avatar

It's possible that the application is unable to save the credential in the Windows Credential Vault. Do you have strict security policy on your machine?

David Hervieux