Rdp Authentication Error
Contents |
Desktop Error ‘An authentication error has occurred. The Local Security Authority cannot be contacted' Home » Microsoft » Windows - Remote Desktop Error ‘An authentication error has an authentication error has occurred (code: 0x80004005) occurred. The Local Security Authority cannot be contacted' KB ID 0000826 Dtd
An Authentication Error Has Occurred The Local Security Authority Cannot Be Contacted
27/06/13 Problem I saw this while attempting to create a remote desktop connection to a Windows 2012 Server. (Though
An Authentication Error Has Occurred This Could Be Due To An Expired Password
connecting to Windows 8 will be the same). I'd only just set this server up, and knew I'd enabled RDP, and I was attempting to connect as the domain administrator,
An Authentication Error Has Occurred Code 0x80090304
so at first I was a little perplexed. Solution If you have direct/local access to the machine you are trying to connect to. 1. Press Windows Key+R > In the run box type sysdm.cpl {enter} > Remote. 2. Remove the tick from "Allow connections only form computers running Remote Desktop with Network Level Authentication (recommended)". 3. Try again. If you do an authentication error has occurred the specified network password is not correct not have direct/local access to the machine you are trying to connect to. 1. On YOUR Machine > Windows Key+R > type regedit {Enter} > File > Connect Network Registry > Type in the details for the machine you are trying to connect to > OK. 2. Navigate to; {remote-machine-name} > HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Terminal Server > WinStations > RDP-Tcp Locate the UserAuthentication value and change it to 1 (one) > OK > Exit the registry editor. 3. Try again. Disable RDP Network Level Authentication via Group Policy If the destination server is in a remote data centre or remote location, and you cannot access the System Properties, you can turn this option off with group policy, and wait a couple of hours. 1. On a DC > Start > Group Policy Management > Either create a new group policy object and link it to the OU containing the problem machine, or edit and existing one. (Here on my test network I'm going to edit the default domain policy - WARNING this will disable this feature on
Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT See more RELATED PROJECTS Setup Cascade servers Setup new Cascade servers Windows 7, Office 2010 Upgrade It was time to upgrade from the old standards - XP and Office 2003, to Windows 7 and Office 2010. Microsoft the local security authority cannot be contacted expired password System Center 2012 Getting Microsoft System Center 2012 up and singing! TECHNOLOGY IN THIS DISCUSSION Remote Desktop the local security authority cannot be contacted server 2012 r2 Microsoft Wind...Server 2012 R2 Join the Community! Creating your account only takes a few minutes. Join Now So we have a Virtual Windows an authentication error has occurred the function requested is not supported Server 2012 R2 box (VMware) with Remote Desktop Services installed on it, for the past few days, a number of users have been getting intermitten problems logging onto the server through the web portal https://servername/rdweb. Users are able to directly RDP http://www.petenetlive.com/KB/Article/0000826 into the server via its IP address, but not is FQDN. I have researched a number of articles regarding this error and none of them seem to really address the issue am I getting. Hoping someone can help me out Tags: Microsoft Windows Server 2012 R2Review it: (61) Reply Subscribe RELATED TOPICS: Remote Desktop Services Learning about Remote Desktop Services New Remote Desktop Services startup   1 2 Next ► 33 Replies Poblano OP kdawg Mar 28, 2014 at https://community.spiceworks.com/topic/465198-authentication-error-0x80004005-unable-to-access-remote-desktop-services 1:30 UTC SIP.US is an IT service provider. Sounds like a DNS problem to me. Can they resolve the server's name with nslookup at the command prompt? 0 Sonora OP Derek8084 Mar 31, 2014 at 3:13 UTC Yes, they are able to perform a nslookup froom command prompt, yet another thing to add to this weird issue 0 Poblano OP kdawg Mar 31, 2014 at 3:45 UTC SIP.US is an IT service provider. Just some troubleshooting suggestions: 1. Ping the webportal address: does it respond? 2. Resolve the webportal address (both with SSL and without): does it resolve correctly both ways? 3. Run a port scanning tool, is a port blocked that is required? 4. Is there a firewall in the way? Could it be NATing the IP and not responding to the name? 5. Is there a dual homed scheme going on? Perhaps the DNS is tied to an IP that's not responding correctly because there are two IP's? Good luck! 0 Sonora OP Derek8084 Mar 31, 2014 at 10:55 UTC 1. The webportal address in on our intranet only right now, so it doesn't respond to a ping when I type in http://servername/rdweb 2. Yes, whether we go http or https, it resolves correctly. 3. No the port is not blocked by our firewall 4.There is no firewall in the way currently, as it doesn't leave our internal network. 5. There is no dual homed sc
Server Hosting Colocation Remote Desktop Connection: An authentication error has occurred. The Local Security Authority cannot be contacted Fixing login problems with Remote http://www.riptidehosting.com/blog/remote-desktop-connection-an-authentication-error-has-occurred-the-local-security-authority-cannot-be-contacted/ Desktop Services If you have having issues logging into a Windows Server with Remote Desktop Services, below are some things to try. For example, some users have seen an error like this when trying to login “Remote Desktop Connection: An authentication error has occurred. The Local Security Authority cannot be contacted”. First, check if your issue authentication error is affecting all users or just one account – can the administrator login? Does user have correct permissions to access the server via RDP – are they are member of the Remote Desktop Users group in User Permissions? Does the Firewall allow RDP connections? What port is used? Is a VPN connection required? Login as computername\username an authentication error (i.e. SERVER1\jdoe) instead if just typing jdoe at the RDP login prompt. (this seems to be required if using the MAC RDP client). Computername is the name given to the server, which you can see under computer properties If only affecting one user, try to reset the users's password and uncheck the box by "change password at next logon". In 2008 R2, login as administrator, open server manager (which may open automatically), expand tree on left side to get to users and groups, select users, right click on user name and say “set password” to reset password, then go in properties of user and uncheck change at next logon. In 2012 R2, click on start button, type “computer management” which will open and expand tree on left side to get to users and groups as noted above. Do not use the “user much change password at next logon” button in user properties. Various comments and posts online indicate that changes in the windows authentication