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: 273
  • Last Modified:

Remote Desktop Error (Machine Specific it seems)

OK So I get the error of

"The remote computer dissconnected the session because of an error in the licensing protocol.  Please try connecting to the remote computer again or contact your system administrator."

on two computers that try to connect to on specific terminal server.

I have tried the deleting of registry keys and everything to no avail.  

I can get to the terminal server from my desktop but I cannot from my laptop.

Any suggestions?
0
Goofdru
Asked:
Goofdru
  • 3
  • 3
1 Solution
 
DPAITCommented:
What are you connecting to?  
A terminal server with licenses or remote administration terminal services?

Sound somewhat like your license server is offline, not being seen or corrupted.
0
 
GoofdruAuthor Commented:
No it is online because I am on it right now on my desktop, trying to see if I see anything weird.  It is a terminal server with licenses, 15 to be exact per seat.  It is not accessed very often but now that a few people have gotten new PC's I don't know what to do.

0
 
DPAITCommented:
It may not be a licensing issue, the error doesn't seem to point to that, but it could be.  

Check the logs to see if you get any more detail on the error.

Also, per seat, means per machine.  So if you have connected from 15 different machines you would be out of licenses.  Assuming it is recording them correctly.

Check the license server and remove any machines that no longer need access.  

If the server is a 2003 box, and you have local admin rights, try connecting to the console by starting Remote desktop with the console switch  (mstsc.exe /console)  That would bypass any licensing issues.
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
GoofdruAuthor Commented:
Well this is what I have found out.

There is an error on the TS Application event log saying that it cannot contact the license service on our domain controller.  Which this is becoming a Cluster F anyway, but the TS is a W2K TS and the domain controller is a W2K3 server.

So after finding that the domain controller didn't have the license logging service started, I started it and now I am getting an error in the System log of:

"Terminal Services Licensing can only be run on Domain Controllers or Server in a Workgroup.  See Terminal Server Licensing help topic for more information. "

and

"The Terminal Services Licensing service terminated with service-specific error 29. "

and
In the application log when I try to connect from a different computer.  Yet the PC's that have worked before are still working.
"The terminal server cannot issue a client license. "
0
 
GoofdruAuthor Commented:
I am sorry all errors are in teh System log
0
 
DPAITCommented:
The error doesn't make sense if this machine is the DC...  

I would start with uninstalling the TS license service and then re-installing it on the domain controller.   Add/remove programs would have this.

None of this is going to work right without fixing this issue.  There is a default amount of machines TS will allow to connect w/o a running license server and there used to be time limitation also.

After getting the service running on the DC you may have to tweak the registry on the TS box to point directly to it even though you shouldn't have to do this.  I have seen it before.  I'll look to see if I can find the exact registry tweak to do that part in the mean time.

0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

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