An Authentication Error Has Occurred Xp
Contents |
97202 Map it Mailing Address PO Box 82065Portland, OR 97282 Phone 503-287-3332 .(JavaScript must be enabled to view this email address) Enable XP SP3 to use Network Level an authentication error has occurred rdp xp Authentication June 10 2013 Network Level Authentication (NLA) as you may or authentication error has occurred remote desktop xp may not know is a new feature of Windows Server 2008 and Vista workstations that adds some extra
An Authentication Error Has Occurred The Local Security Authority Cannot Be Contacted
security as well as improves login performance by offloading some of the initial remote computer resources required at login. Earlier versions of Terminal Services authentication did not occur until the
An Authentication Error Has Occurred 0x607
full desktop connection (including all the related processes) were started which chewed up server resources and opened the server up to denial of services attacks. With NLA enabled, the user is "pre-authenticated" before any desktop and related processes are created. It is recommended to have all Terminal Servers (RDS) use NLA at all times. XP Service Pack 3 and an authentication error has occurred 0x507 Remote Desktop 6.0 support NLA but it is not turned on by default which means you may simply not connect or see the error "An authentication error has occurred (Code:0x507)". To fix this on XP SP3 systems use the “fix it” utility from MS: http://support.microsoft.com/kb/951608 Or manually make the edits yourself: Click Start, click Run, type regedit, and then press ENTER. In the navigation pane, locate and then click the following registry subkey: HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\Control\Lsa In the details pane, right-click Security Packages, and then click Modify. In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK. In the navigation pane, locate and then click the following registry subkey: HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders In the details pane, right-click SecurityProviders , and then click Modify. In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK. Exit Registry Editor. Restart the computer. ← Back to main Library page Copyright © 2007 ProComp Group LLC. All rights reserved. // Sitemap Portland web design: 420 Creative
a few minutes. Join Now Hi all, As of yesterday I have been getting an authentication error when I attempt to Remote Desktop from my XP SP3, (I know, I know XP. but
An Authentication Error Has Occurred Code 0x507
I will be stuck with it for a while longer) machine to our 2008 R2 an authentication error has occurred rdp windows 7 server. This just started yesterday, and I have checked the internet with no real answers. I am hoping someone in Spice land an authentication error has occurred code 0x800 may have an answer for me . Thanks Reply Subscribe View Best Answer RELATED TOPICS: authentication error Authentication Error Authentication Error   8 Replies Datil OP LWBM Mar 28, 2014 at 4:57 UTC http://community.spiceworks.com/topic/452023-remote-desktop-disconnects-instantly - http://www.procompgroup.com/library/entry/enable_xp_sp3_to_use_network_level_authentication/ Last post, I updated recently. 0 Thai Pepper OP brian wing Mar 28, 2014 at 5:02 UTC Any specific details you can share about the error? Screenshot, error number, error message? Check the event logs on the XP box and, if you have access the 2008R2 server. It's likely the security level required by the 2008R2 server, esp. if your XP box isn't domain joined. 1 Jalapeno OP https://community.spiceworks.com/topic/465591-authentication-error-with-xp-and-2008-r2 Nick3135 Mar 28, 2014 at 5:06 UTC Thanks LWBM, but this is a different issue. We can log in using Win 7 and 8 boxes. It is just the XP boxes that the problem occurs. The actual verbage is: "An authentication error has occurred. The requested security package does not exist. Remote server: xxx-xxxx. 0 Jalapeno OP Nick3135 Mar 28, 2014 at 5:09 UTC Hi Brian, The RDP setup is as shown in your post. and the XP box is joined to the domain and I am an Administrator on both boxes. 0 Pimiento OP Best Answer Chris8724 Mar 28, 2014 at 5:59 UTC 1st Post Nick, The NLA (Network Level Authentication) is not configured by default on these XP machines is my first guess. There is a registry change that I have previously used Here. Hope this helps. Chris 0 Jalapeno OP Nick3135 Mar 28, 2014 at 6:55 UTC Thanks Chris, I tried this but 'No Joy'. I keep getting the same error. 0 Jalapeno OP Nick3135 Mar 28, 2014 at 7:50 UTC Hi Chris I don't know what was different, but after I had run your fix I could not log into the 2008 R2 server, but after I ran MS Fixit hat basically did th
unreachable. NLA Error, XP SP3 This is really annoying and it took me a little while to find the fix, so I am blogging about this in hopes that others waste less time! I have http://blog.kristinlgriffin.com/2010/08/authentication-error-has-occurred.html a 2008 R2 RD Session Host server farm. IT is set to accept only http://www.bozteck.com/troubleshooting/enable-nla-on-windows-xp-for-rdp/ connections from NLA clients. Connecting from any Win7 machine works great. Then I tried to connect via a client running XP SP3, running RDC 6.1 (supports NLA) with CredSSP enabled. I got the following error: An authentication error has occurred. The specified target is unknown or unreachable. If I turn off requiring NLA on the authentication error farm servers, I can connect.Next, I added RDC 7.0 and tried again. I get the same error.I tried from more XP clients, with the same setup and I get some that get in and some that give the error. VERY CONFUSING. Turns out, there is a hotfix out there that fixes this:I added: http://support.microsoft.com/kb/953760, and rebooted. Now it works. What I find interesting is that the hotfix does not authentication error has specifically lay out this exact error result.ARGH.If it had I would have found it SO much faster. Note: WebSSO will still not work unless you have RDC 7.0 on your XP client - RDC 7.0 is a requirement for WebSSO. Posted by Kristin L. Griffin at 4:41 PM 16 comments: baodadSeptember 29, 2010 at 10:38 AMThank you so much for posting this! It saved me hours and hours of research!ReplyDeleteRepliesDarth M3ph0zMay 31, 2012 at 12:21 PMThis comment has been removed by the author.DeleteReplyKristin L. GriffinDecember 3, 2010 at 9:45 AMGlad to be of service :)ReplyDeleteLouisDecember 16, 2010 at 2:56 AMGreat! Thank you very much!!!ReplyDeleteMalumFebruary 2, 2011 at 8:35 PMGreat info, thanks very muchReplyDeletehighkoOctober 10, 2011 at 6:33 AMThx, still valuable after all this time :-)...ReplyDeletewing_zero01December 7, 2011 at 10:02 AMThank you for this. Saved a lot of timeReplyDeleteDoxturMay 17, 2012 at 11:03 PMIt's work! Thank you!ReplyDeleteDarth M3ph0zMay 31, 2012 at 12:24 PMI am so glad there are people like Kristin Griffin in the world. Why just today, this problem came up for us here at my organization and this article solved it for us. Now we can use NLA for our legacy Terminal services clients. Then I realized who it was that wrote the article
computers with Network Level Authentication (NLA) enabled. Luckily, Microsoft has released a couple of hot fixes and VNCScan has written into it a feature that still allow you to connect to Windows 7 and above computers with NLA enabled. You will need to do this if you cannot connect to a remote computer with NLA and if you get the following error: “An authentication error has occurred. The specified target is unknown or unreachable.” Warning: The hotfixes from Microsoft below are not fully regression tested and should be installed in a lab environment before placing it into production. Downloads For your convenience, I have placed direct download links to the hotfixes below. Microsoft RDP 7.0 Update for Windows XP SP3 WindowsXP-KB953760-v2-x86-ENU.exe (For XP SP3 only) WindowsXP-KB953760-x86-ENU.exe (For XP SP3 only) Bozteck VNCScan RDP Manager (Latest version) Instructions Download all of the items above Install the RDP 7.0 update Install both of the hot fixes and then reboot Install Bozteck VNCScan and run it for the first time. If prompted, please reboot. When VNCScan is ran for the first time, it checks to see if NLA has been enabled for the RDP client on your computer. If not, it sets it to be enabled and then prompts you to reboot your computer for it to take effect. You could also enable NLA manually by following the instructions below if you do not wish for VNCScan to do it for you: Click Start, click Run, type regedit, and then press ENTER. In the navigation pane, locate and then click the following registry subkey: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsa In the details pane, right-click Security Packages, and then click Modify. In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK. In the navigation pane, locate and then click the following registry subkey: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSecurityProviders In the details pane, right-click SecurityProviders, and then click Modify. In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and th