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

Issues logging into a terminal server

I have a terminal server that is running Windows Server 2003.  I am noticing issues when I try to rdp into this server from other servers on the network.  Some of the other servers will get into it just fine but some will not.  On these servers that cannot gain access to this server, they can however rdp into other machines just fine.  

When I go to remote access this server I get the following error: The remote session was disconnected because there was an internal error in the remote computer's licensing protocol.

Thanks
0
microsymplex
Asked:
microsymplex
1 Solution
 
mkeiwuaCommented:
Hi microsymplex,

Are there any events in the Event Viewer?

B Rgds,

Mkeiwua
0
 
microsymplexAuthor Commented:
This is the only things I see in the event viewer on the server I am trying to rdp into:

Event Type:      Information
Event Source:      TermService
Event Category:      None
Event ID:      1004
Date:            3/31/2010
Time:            11:54:31 AM
User:            N/A
Computer:      MXTEST
Description:
The terminal server cannot issue a client license.  It was unable to issue the license due to a changed (mismatched) client license, insufficient memory, or an internal error. Further details for this problem may have been reported at the client's computer.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
 
WolfhereCommented:
Try deleting the MSlicensing key from HKLM\Software\Microsoft from the machines unable to access due to licensing. Then re-establish the 'key' by rdp'ing to the TS server. Also, from the TS server, check your user's in task manager and logoff all disconnected users.
0
Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

 
microsymplexAuthor Commented:
Hi Wofhere:
I did that and still receive the same error.  I also get this event in the log about 2 minutes after the first event:

Event Type:      Warning
Event Source:      TermService
Event Category:      None
Event ID:      1028
Date:            3/31/2010
Time:            11:56:20 AM
User:            N/A
Computer:      MXTEST
Description:
The terminal server client SRV1  has been disconnected because its license could not be renewed. The license server SRV1 was contacted to get Windows Server 2003 - Terminal Server Per Device CAL Token. license for this client.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
 
Henrik JohanssonSystems engineerCommented:
Was the deleting of MSLicensing registry key done on the client trying to connect?

The server is configured as a TS in application mode requiring it to have a TS Licensing Server available with TS-CALs. If you only nead to access the server for administrative tasks, you can have the server setup for RDP access in remote admin mode without neading to have TS-CALs. If so, just uninstall the Terminal Server role through Add/remove programs -> Windows components.

If you nead to have it in TS app mode (more than 2 RDP sessions), the server nead to be aware of where the TSLS with installed TSCALs is located. See technet article about howto configure preferred TSLS.
http://technet.microsoft.com/en-us/library/cc737644(WS.10).aspx

As the TS tries to get a TS Device CAL, make sure the TSLS on SRV1 has the same kind of TS-CALs (can be either User or Device) installed.

A good site for troubleshooting of TS troubleshooting is Vera Noest's site
http://ts.veranoest.net/ts_licensing.asp
0
 
microsymplexAuthor Commented:
Hi Henjoh09

Deleting of the MSLicensing registry was done on the client trying to connect.  

This is an actual terminal server and is configured properly.  We have been using it for a solid 6-8 months without any problems at all.  In fact I can even get some servers to connect to it without any problems at all currently.  I get this error on a few of the servers when trying to connect it (do not know about any problems with desktops yet).  It also sees the TSLS just fine and we have plenty of available licenses.

I will check out that website too.

Thanks
0
 
Henrik JohanssonSystems engineerCommented:
If still a problem, I remember that I've seen before that following registry value has become corrupt causing the TS to only obtain temporary TSCALs.

HKLM\System\CurrentControlSet\Control\TerminalServer\Licensing Core\PolicyAcOn

http://support.microsoft.com/kb/834651
0
 
Henrik JohanssonSystems engineerCommented:
I was notified today that we had similar problem on one of our TS and when troubleshooting I saw the eventid 1028 combined with eventid 38 and ended up with reinstalling the licensing service and TSCALs because the certificate store for TSLS had became corrupt and TSLS couldn't be re-activated. The lucky thing with this server is that it didn't affect so many users when the TSLS was local for a single TS and not the central TSLS for the rest of the TS farms.

http://support.microsoft.com/kb/2021885
http://support.microsoft.com/kb/887444
0
 
microsymplexAuthor Commented:
Thanks KB2021885 fixed our issue!
0
 
sbeardenCommented:
KB 2021885 suggests that you can remove the registry keys if you aren't connected to the internet.  It does not however specify if you have to reactivate the server and reapply the license paks.  I am trying to avoid that if at all possible, due to the fact a rogue IT person, has either misplaced or maliciously discarded the retail license paks and not even Microsoft is interested in helping.  So can someone answer that questions that has run through the steps whether or not it kills the current licensing database.  Otherwise, we'll be buying licenses that we have already purchased.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

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