Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4679
  • Last Modified:

(0x507) error when trying to Connect to TS 2008 from XP SP3

I have terminal services set up on a Windows server 2008 that is also a domain controller. I have no issues connecting to it remotely through machines running Windows 7. However, I have several machines running XP SP3 that cannot seem to connect. I get to the initial log in screen in TS which authenticates no problem. It is when I launch an application and enter in my credentials that I get the RemoteApp error:
An authentication error has occurred (Code: 0x507)

Remote computer: {domain name}

Any help would be appreciated
0
B00m3r
Asked:
B00m3r
1 Solution
 
Neil RussellTechnical Development LeadCommented:
Upgrade to the latest RDP client.
0
 
Neil RussellTechnical Development LeadCommented:
OR Are you using smart cards at all over the TS session?
0
 
B00m3rAuthor Commented:
No, I'm not using smart cards. I've done all optional and required windows updates on the machines. Is the latest RDP client only downloadable from microsoft directly?
I've also enabled NLA through the registry.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Neil RussellTechnical Development LeadCommented:
I wouldnt download ANY windows components form anywhere EXCEPT microsoft!
0
 
B00m3rAuthor Commented:
I meant through their website as apposed to doing it through Windows Update
0
 
Neil RussellTechnical Development LeadCommented:
What version of the client are you currently running?
 
0
 
B00m3rAuthor Commented:
Right now I'm running Version 6.0. To the best of my knowledge that is the latest version.
0
 
B00m3rAuthor Commented:
Scratch that, I'm running RDC 6.1
0
 
sameeragayanCommented:
Check "Always Prompt for Password" on RDP - Properties and see whether it will work that way.

5436645654656.png
0
 
DavidGeraldCommented:
Have you configured your RAP and CAP policies correctly?
Also have you got NLA enabled on enabled on the connection in session host server, if so try disabling.  Make sure encryption on the samce screen is set to client compatible.
0
 
B00m3rAuthor Commented:
I was able to resolve the issue. The registry changes that I had for XP SP3 to enable NLA weren't correct.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now