An Authentication Error Occurred 0x507
Contents |
occurs when you try to connect from your XP (SP 2 or 3) desktop to Windows 2008 an authentication error has occurred 0x507 remote desktop or Windows 2012 Remote Desktop Server.To solve this error you need
Authentication Error Code 0x507
to make registry changes. Click onStartand Click onRUN(if it is Vista or later type regedit rdp authentication error 0x507 in search) TypeRegeditand clickOK It will open registory editor Click onHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa In right hand panel right click onSecurity Packagesand clcikModify. In box leave all value and
Rdp An Authentication Error Has Occurred Code 0x507
addtspkgat end As new value. and click OK.Refer Image Now click onHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders In right hand side panel right click onSecurity Providerand clickModify In data add wordcredssp.dllas new value. Do not change any other value ClickOKand exit from registery Editor Restartyour computer. Was this article helpful? 0 out of 0 found this helpful Have an authentication error has occurred the local security authority cannot be contacted more questions? Submit a request Comments Related articles Connecting to Remote Desktop on Windows 2012 Server with Network Level Authentication Windows Server 2012 - Remote Desktop Licensing without a Domain Disabling Network Level Authentication on Windows Servers Windows 2012 Remote Desktop - User Profile Disks and Temporary Profiles Remote Desktop Timeout Limits on Windows 2012 This entire document, including design, text, videos,graphics, and photographs are Copyright © 2014 Austlink Plus Pty Ltd, All Rights Reserved. No part of this document may be reproduced in any way or by any means for commercial or any other purposes, without prior written permission of Austlink Plus Pty Ltd. Use of any data for the purpose of creating promotional materials or producing a printed or electronic catalog of any kind is expressly forbidden without prior written permission of Austlink Plus Pty Ltd. Austlink Plus Pty Ltd - 2016 © Copyright All Rights Reserved 1300 766 812 Powered by Zendesk
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Remote App Authentication Error https://help.austlink.net/hc/en-us/articles/202717156-Remote-Desktop-Issue-Windows-XP-Authentication-Error-has-occured-0X507- (Code:0x507) up vote 0 down vote favorite I'm trying to get RDP services running with Windows 2008 R2. I'm at a WINXP SP3 client that was modified to run RDP with NLA. When I start the client connect to the local DC and get an authentification error (Code 0x507). I've already done the following: • Server Setup to run as a standalone local "DC" to provide Terminal services to a single application. Remote http://serverfault.com/questions/113594/remote-app-authentication-error-code0x507 Desktop Session Host CAL License is running & operational, RD Gateway Manager w/ Local Server RAP & CAP running NLA & operational Server has NLA & temporary use of port 3389 (which is directly connected to and accessible from the internet (I am planning to change the port to 443, but want to get the current system running first). • XP Client(s): RDP-Version on win xp clients is 6.1 If had SP2, then added SP3 and edited the registry settings to allow NLA, by: Click Start, click Run, type regedit, and then press ENTER. In the navigation pane, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE \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: HKEY_LOCAL_MACHINE \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. windows rdp share|improve this question edited Aug 13 '12 at 22:43 TML 33829 asked Feb 16 '10 at 22:11 CMK Is there a question here? –joeqw
you are accessing Windows Server 2008 OS remotely from Windows XP http://tech2solution.blogspot.com/2010/12/authentication-error-has-occurred-code.html SP2 or SP3 ,Windows 7,Windows Server 2003, this error http://australia-bestmate.blogspot.com/2011/03/authentication-error-has-occured-0x507.html wont allow us to connect remotely, this happens because of NLA,and some Registry disturbance in local desktop, The solotion for it is: 1. Try to login with different user in that system where you used to code authentication error 0x507 error. 2.After login with other user name try to access remote of windows server 2008. 3.Now you can access Windows Server 2008. Use the following steps if the above wont works for you. 1.Just rename the existing profile in that system. 2.Login with your id now an authentication error and take Windows Server 2008 remote it will work fine. Post comments if you got any issues Regards Raju Gunnal Posted by RajuG VCP at 8:25 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest 2 comments: AnonymousMarch 4, 2011 at 10:11 AMHi There, I had same problem. I followed steps from below website and it solved my problem.http://australia-bestmate.blogspot.com/2011/03/authentication-error-has-occured-0x507.htmlReplyDeletedigital signature Adobe ReaderDecember 18, 2011 at 6:25 PMYes I got this error message but I was not able to resolve it. I tried above mentioned steps which you given. All you need to just follow the steps and the error is resolved. Now I am able to access my application without authentication error message.ReplyDeleteAdd commentLoad more... Newer Post Older Post Home Subscribe to: Post Comments (Atom) Advertising Contact us @ Twitter tech2solution Copyright@tech2solution2011. Simple template. Powered by Blogger.
TS. This is NLA error. WIndows 2008 use NLA for security reason. To solve this error you need to make registory changes. 1. Click on Start and Click on RUN (if it is Vista type regedit in search) 2. Type Regedit and click OK 3. It will open registory editor 4. Click on HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa 5. In right hand panel right click on Security Packages and clcik Modify. 6. In box leave all value and add tspkg at end As new value. and click OK.Refer Image 7. Now click on HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders 8. In right hand side panel right click on Security Provider and click Modify 9. In data add word credssp.dll as new value. Do not change any other value 8. Click OK and exit from registery Editor 9. Restart your computer. If you are responsible for maintaining Windows Terminal Server in your environment then i strongly recommend to use "Windows Server 2008 Terminal Services Resource Kit" . This book is really very helpful. You can buy this book just for $31.49from thislink Windows Server 2008 Terminal Services Resource Kit If this still will not solve problem please send me an email at pcservice@live.com.au and i will send you file (which will change appropriate registory settingson your computer). Still can not solve this problem ? Need Professional Help. CLICK HERE for more information. Do you have too Many password to remember ? I use and personally recommend. Cheers Posted by Australia at 3:05 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Reactions: 23 comments: JesicaMarch 4, 2011 at 3:46 PMThank you so much for this solution. I spend 3 days and your note solved my problems in minute. Thank you again.ReplyDeleteAnonymousMarch 8, 2011 at 12:03 PMThank-you, worked for me tooReplyDeleteHosting Server IndiaApril 5, 2011 at 1:31 AMThat's an accurate solution you have mentioned here in your post. ThanksReplyDeleteAustraliaApril 5, 2011 at 10:00 AM@Hosting Server India. I am glad that my post has helped you to solve your problem. CheersReplyDeleteAustraliaApril 5, 2011