Hi All, I am using Windows 8 Pro as my workstation from which I connect to remote servers. I have started to experience rather odd and annoying issue that once I start to establish remote connection and have entered destination IP or FQDN it brings up authentication widow where credentials need to be entered but the joke is, that windows does not have fields to enter the user name and password, it spins 'Just a moment' and after 1 minute or so app finally allows me to specify the credentials. This appears to happen with the Windows server 2008 and later destination servers.
I have to admit that I had tried to save the credentials for some of the connections. I also use Remote Desktop Connection Manager, MSTSC, and Remote Desktop app for Windows 8. This issue is occurring on all three of them. I have tried to remove saved credentials from the Credential Manager, inspected the Log Files, but nothing obvious is appearing.
Remote Desktop Connection - Clear History in Windows This tutorial will show you how to reset and clear all or specific Computer and User name history entries listed in the Remote Desktop Connection tool for your user account in Windows 7, 8, and 10.
Please refer to attached image. Thanks for your help. Davidgagnon wrote: Thanks to Niall post I was able to come with that alternative solution.
I use RDCMan 2.7 in a Server 2012 enviroment, I was having the same issues, the following Solved them: For the password/profile mark (Global). ToolsOptions Click Default Group Settings Go to Profile Management Tab Select your profile Edit Add in your credentials and click Save Click OK, OK then File and Save All. Your credentials should now be cached for all connections saved. For the password mark (File) simply go to your file name (top root parent) inside the Remote Desktop Connection Manager, right-click on it Properties Go to Profile Management Tab Select your profile Edit Add in your credentials and click Save Click OK, OK then File and Save All. Your credentials should now be cached for all connections saved.
Hope that Helps. David This was the fix for me! Is this on a domain, or in a workgroup environment? I had a similar issue in a workgroup environment, because there were no saved credentials for the target machine - it also happens when there are existing (incorrect) credentials stored for the target machine.
Try removing existing / entering credentials manually (in Control Panel User Accounts User Accounts Manage your credentials) and see if the problem persists. Which type of remote desktop connection does the target machine allow? Is it 'Any' or 'Allow only connections from computers running remote desktop with network level authentication'? Try changing this setting and see what happens. Hi Bryce and thanks for your reply.
Time sync is fine, I had that checked before. Have looked through the log files, nothing is reported (I even cleared log files before attempting to connect and nothing new is entered, even checked the Windows Component Event logs for Remote Desktop app and Connections) Will try to look through the logs of remote servers. Remote Desktop is enable on all the servers I access, please note that this issue started after some time I was able to establish Remote Desktop connection successfully without delay I have now. I do remember re-installing my machine some time ago which started to have same issue. It is probably 2 months from now and all was fine then.
Hi Andre, I kind of did this part of your advised troubleshooting. My workstation is on the domain which is different from domains I connect to, there are multiple different domains. I though about that too that it must be trying to use my domain credentials to access remote hosts by default, but I wasn't able to prove that yet. I did remove all my saved credentials for the server I was accessing on daily basis and that didn't made any difference. All machines I access are configured to accept connections from any device without requesting NLA. Other guys in our office are accessing them and have no issues whatsoever.
Thanks Andre for advice, Just tried to specify this in Credential Manager and received another similar issue. 'Your system administrator does not allow the use of saved credentials to logon to the remote computer x.x.x.x because its identity is not fully verified.' This caused same delay to bring up the fields where I specify the credentials. I did found how to make credentials saved and verified: But that isn't the solution for that, why it is happening in first place as it was working fine before without the delay.
Hi HBAMacdade, Please note that I am fully aware of this command, as that is how I would usually launch my Remote Desktop connections, but I don't use switches apart from /admin or /console. If I would need to full connection details in command line, then I rather would wait that minute as it would not be time efficient anyway. Thanks for your contribution doh. Quick update regarding issue, my pc with Win8 went for restart due to updates, and funny enough it is working fine now without delay. Checked what was installed and nothing more that Office 2013 updates, which cannot be linked to the issue I am having, question now is, for how long it will work?:D.