This error occured when you try to connect from your XP (SP 2 or 3) or Vista desktop to Windows 2008 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
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.49 from this link 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 settings on 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
Thank you so much for this solution. I spend 3 days and your note solved my problems in minute. Thank you again.
ReplyDeleteThank-you, worked for me too
ReplyDeleteThat's an accurate solution you have mentioned here in your post.
ReplyDeleteThanks
@Hosting Server India. I am glad that my post has helped you to solve your problem. Cheers
ReplyDelete@Jesica, I am glad it helped you and solve your problem.
ReplyDeleteYes, definitely. That proves you as a '5 years + of IT experience holder'.
ReplyDeleteLet us know, if you need any kind of services from us, virtual,dedicated or anything. We will be glad to serve you as an elite customer. :)
Thanks.
Thanks, this solved the problem!
ReplyDeleteRikard glad to hear my post has helped you to solve problem.
ReplyDeleteThank you so much it works
ReplyDeleteHi Carlos, Nice to hear it solved issue. And thank you for your comment.
ReplyDeleteAfter doing the above step I am being asked for credentials to log into my computer when I have never set credentials to log on to the computer...Need help please...
ReplyDeleteWe have a team of offshore support people in India and they were receiving the same error, adding tspkg to Security Providers did the trick. Thank You!
ReplyDeleteI am glad to hear this blog has helped you to solve outlook problem.
ReplyDeleteAdding tspkg worked for me. Thanks!
ReplyDeletePerfect!! simple and easy to follow plus it worked!!
ReplyDeletethanks. it worked
ReplyDeleteThanks for your comment on 0x507 authentication error. cheers
DeleteMany thank, good article !
ReplyDeleteSolved my issue. Definitely a good article.
ReplyDeleteThanks gor your comment Michael. Glad to hear my post has solved authentication error 0X507. cheers
DeleteI would have never found this on my own, thanks!
ReplyDeleteGregorio, Glad to hear my post has worked for you. Thanks for your comment.
DeleteThank you Australia for this post. I had a staff member with an XP (SP3) home laptop and she wanted to be able to RDP to her Windows 7 (SP1) desktop while at home across our VPN. Your steps helped resolve her connection issue.
ReplyDelete