• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 235
  • Last Modified:

Security error when connecting to Terminal Services

I get an error, " Because of a security error, the client could not connect to the remote comptuer.  Verify that you are logged on to the network and then try connecting again".  

I have two servers one SBS2003, its the main DC and one application non DC (member) w2k server.  The non DC server as an application that needs access from remote staff.  I have a sonicwall firewall configured for VPN and setup to get the DHCP infor from the main SBS2003 server.  In which it does.  I have validated this in the lease addresses of the dhcp console.  I can connect all the time to the main SBS2003 server via terminal services but I get the above error when I go to connect the the W2K application server.  When I'm in house I can connect terminal services just fine to the W2K application server.  I only get this error when I access the application server remotely.   Any Ideas.  

I did a search and licenses was mentioned but since this is a W2K server and I'm using XP, I should have a license issue on that application server, right?

Fred
0
Bulls-Eye
Asked:
Bulls-Eye
  • 3
  • 2
  • 2
  • +1
1 Solution
 
Bulls-EyeAuthor Commented:
Oops,  Sorry about all the grammar errors.  I was in a rush.

Fred
0
 
Yan_westCommented:
From Microsoft support:

Because of a security error, the client could not connect to the Terminal Server
http://support.microsoft.com/?id=329896
0
 
Yan_westCommented:
Hmm, also, is there any event id in the server when you try to connect remotely?
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.

 
nathan_jardineCommented:
I had a similar problem and I disabled the license logging service and was able to get in with no problems.
0
 
Bulls-EyeAuthor Commented:
Ok, I checked the license logging service and it was disabled. The only event id's are printer ones like 1106 and 1111, printer driver not found.  I printed out the microsoft case and I'm going down there to execute those steps.  I'll let you guys know what I find out.

Thanks for all your help!  
Fred
0
 
Bulls-EyeAuthor Commented:
It was the termial server certificate that was corrupted.  I had to delete the registry entries and re-install terminal services.  Thanks everyone for your fast response and help.

Fred
0
 
RoadrnnrCommented:
I am having the same problem but it only happens when you connect with a 98 or 2000 machine. When i connect with an XP client its fine. No events logged. Tried wiping the cerfificates out of the registry and reactivating, even by phone. Still no luck. Any ideas?
0
 
RoadrnnrCommented:
Heh,.... nevermind, it appears that after you do the certificate stuff a reboot is required :)
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now