This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Check reverse DNS lookup on the IP address of the Windows 2008 R2 machine. asked 6 years ago viewed 33132 times active 1 year ago Related 7Remote Desktop fails without error message2How to configure Remote desktop on window server 2008 R2?2Remote Desktop and Server 20082Remote Once the time was corrected then it worked. check over here
Initially I ran ipconfig /flushdns on the client because that's kind of what the RDP error told me to do. We wondered if this was somehow related to the problem. Try using the IP address of th, unable to RDP, windows 2012, WinteladminBy in Windows(2003/2008/2012) on September 29, 2015 Unable to connect to the Remote Desktop. ueland on October 16, 2013 at 21:54 said: Everywhere if needed, start with one, and continue until it work. https://social.technet.microsoft.com/Forums/office/en-US/8dae0410-a15f-4381-8bf7-c170fc5e8d2d/the-connection-could-not-be-completed-because-remote-computer-was-not-the-one-you-specified?forum=winserverClustering
We are able to connect by IP address.Googling for this error comes up with ideas like checking for time sync (it's good) and disabling the security checks for RDC (we can't Therefore, this issue was due to the time difference between the virtual machine and the NTP server set on an ESX host. We deleted the AD object, waited for about an hour, and (somewhat to our surprise) this actually fixed the problem--we were able to RDC to the virtual/public name without any trouble. What's the correct term to describe baby food?
Subscribe to Become The Solution! This was my exact issue. Leave a Reply Cancel reply CommentName Email Notify me of follow-up comments by email. The Local Security Authority Cannot Be Contacted This Could Be Due To An Expired Password Both are 64-bit.
Privacy statement © 2016 Microsoft. This Could Be Caused By An Outdated Entry In The Dns Cache Server 2012 Is a two-prime lens possible? Try using the IP address of the computer instead of the name. http://becomethesolution.com/blogs/the-connection-cannot-be-completed-remote-desktop-windows-error Note: If you do not wish to have auto sync, disable the Windows Time service or block the outbound port 123 on your local firewall.
RDP on physical was good and the issue was with the virtual host. The Local Security Authority Cannot Be Contacted Expired Password The connection to the server ‘Server URL' could not be completed during mailboxmigration March 8, 2016 4:58 PM / Leave a comment When you try to Migrate a mailbox from Exchange Fix was to run ipconfig /registerdns on the problem server. –Neil P Oct 6 '15 at 8:23 add a comment| up vote 2 down vote Yes, make sure the time on Like Show 0 Likes (0) Actions 3.
Re: Outdated Entry in DNS Cache when connecting to VCHB name with Remote Desktop hawkeye95 Sep 10, 2013 6:19 AM (in response to jrh910) We ran into this same exact problem. https://www.petri.com/forums/forum/microsoft-networking-services/dns/67455-rdp-not-working-to-server-with-host-name Would presence of MANPADS ground the entire airline industry? The Connection Cannot Be Completed Because The Remote Computer That Was Reached Is Not Dns Cache The target name used was TERMSRV/SERVERNAME. Windows 7 The Connection Cannot Be Completed Because The Remote Computer That Was Reached This could be caused by an outdated entry in the DNS cache.
This error can also happen when the target service is using a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target check my blog Categories HP (Servers/products) McAfee (Antivrus/ePO) Network (LAN/WAN) Powershell SCCM (Image/Deployment) Scripting (Automation) Storage (EMC/NetApp) Uncategorized Updates (Wintel Admin) VMware (ESX / vSphere) Windows(2003/2008/2012) Archives November 2016 October 2016 September 2016 August Thanks, WintelAdmin ← Windows could not finish configuring the system. This indicates that the target server failed to decrypt the ticket provided by the client. An Authentication Error Has Occurred The Local Security Authority Cannot Be Contacted Rdp
Thank you this worked! It has its hostname A record and reverse lookup correctly defined and there's a CNAME pointing to the FQDN that was previously used to address it. It was reporting a time in GMT when the server was actually in EST. this content share|improve this answer answered Feb 12 '10 at 18:23 Jim McKeeth 1,07141419 2 gotta love detailed error messages... –Hubert Kario Nov 8 '12 at 21:22 add a comment| up vote
Email check failed, please try again Sorry, your blog cannot share posts by email. %d bloggers like this: Windows Administrators Blog! The Local Security Authority Cannot Be Contacted Server 2012 R2 also fixed some of our other issues. Please type your message and try again. 3 Replies Latest reply: Sep 10, 2013 5:07 PM by jrh910 Outdated Entry in DNS Cache when connecting to VCHB name with Remote Desktop
pavankumar on August 31, 2013 at 09:42 said: Great Solution David on October 9, 2013 at 16:39 said: when you say "And of course, make sure that you don’t have any Try using the IP address of the computer instead of the name.) The first thing you should do, is to make sure that the clock is correct on these nodes: 1: This could be caused by an outdated entry in the DNS cache. The Local Security Authority Cannot Be Contacted Domain Controller Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Success! Renato Sampaio on October 7, 2015 at 16:42 said: If you have a duplicated DNS entry name's you faced the same error. This could be caused by an outdated entry in the DNS cache. http://deftmag.com/not-be/the-ea-network-could-not-be-reached-at-this-time.html It was confirmed that the issue was due to time latency.
© Copyright 2017 deftmag.com. All rights reserved.