0x507 Authentication Error Remote Desktop
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 0x507 remote desktop Authentication June 10 2013 Network Level Authentication (NLA) as you may or rdp authentication error 0x507 may not know is a new feature of Windows Server 2008 and Vista workstations that adds some extra authentication error code 0x507 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
Remote Desktop Authentication Error Local Security Authority
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 the local security authority cannot be contacted 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
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: XP SP3->Server 2k8 Authentication error code: 0x507 Windows Server > Remote Desktop Services (Terminal Services) Question 0 Sign in to vote Hi everyone,I had a lab setup of 3 Server 2k8 RC0 Terminal servers. They functioned as my thinclient RemoteApp servers, and they did a fantastic job! So fantastic that I went ahead and purchased Server 2008 http://www.procompgroup.com/library/entry/enable_xp_sp3_to_use_network_level_authentication/ Enterprise Edition licenses. I setup my environment the same exact way I had set up my RC0 environment, but I have ran into unexpected errors. Long story short:My XP SP3 computers (which have the 'latest' RDP client) cannot connect to my 2k8 servers. They simply throw back an "Authentication code error: 0x507." I did find the MS Knowledgebase page where https://social.technet.microsoft.com/Forums/windowsserver/en-US/3861c357-a82c-49d0-a7c3-db3478ea0a38/xp-sp3server-2k8-authentication-error-code-0x507?forum=winserverTS it said to edit a couple registry keys which appended the data "tspkg" and "credssp.dll" to three different locations, then rebooted and has made no difference.With the latest RDP Client, I can still connect to my 2003 servers without a problem. The one difference I've noticed is that when the RDP client connects to a Server 2008 TS, it asks for a username & password before going any further, unlike connecting to a 2003 server where it'll connect you to the server first then ask for the login credentials.I'm stuck, and cannot get past this. School starts in a couple weeks and I need to find a workable solution to these issues. I've tried to go through as many RDP settings as possible on my Server 2008 TS and that has made no difference (accept all connections even from insecure clients, added my user group to the Remote Desktop system group...stuff like that)I would love to hear what some people have to say, and would appreciate any feedback or ideas about this situation. Thank you!-Mike Tucker
Advisory Board Home Ideas Exchange Community Forums Beta News and Announcements Introduce yourself to the Community! Announcements and Release Notes Security Industry News Webroot for Home Webroot® SecureAnywhere™ - Antivirus Webroot® SecureAnywhere™ - https://community.webroot.com/t5/Webroot-SecureAnywhere-Complete/Remote-Desktop-Connection-failing/td-p/45734 Internet Security Plus Webroot® SecureAnywhere™ - Complete Webroot® Mobile for Android Webroot® Mobile for iOS Webroot® Legacy Products (2011 and Prior) Webroot® SecureAnywhere™ - Antivirus for PC Gamers Admittedly More Interesting than Internet Security Techie Non-Techie Photos Channel Partner Channel Partners CommunityCategoryBoardKnowledge BaseUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible authentication error matches as you type. Showing results for Search instead for Do you mean Register · Connect with Facebook · Sign In · Help Webroot Community : Home : Community Forums : Webroot for Home : Webroot® SecureAnywhere™ - Complete : Remote Desktop Connection failing Reply Topic Options Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer an authentication error Friendly Page « Message Listing « Previous Topic Next Topic » « Previous 1 2 Next » enchant New Voice Posts: 7 Registered: 06-20-2013 Remote Desktop Connection failing Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content 06-20-2013 05:07 AM About a week ago (give or take), my Prevx software switched over to Webroot. I honestly don't know what changes were made, but I DO know that some were.Round about the same time, my Remote Desktop Connection to another system stopped working. When trying to connect from my WinXP machine to my Win7 machine, I started getting the following error:An authentication error has occurred (Code: 0x507).Anyone know what might have happened? My next step is to reload a restore point of a couple weeks back, but I'd like to avoid this if there's a simple fix.Thanks for any help. Solved! Go to Solution. Report Inappropriate Content Message 1 of 14 (7,262 Views) Reply 0 Kudos Rakanisheu Retired Webrooter Posts: 1,289 Registered: 03-13-2013 Re: Remote Desktop Connection failing Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content 06-20-2013 05:14 AM E