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

Can't access server via Remote desktop

Alright, gang...here's a fun one.

I have a Windows 2K server that is all of a sudden inaccessible via RDP...but only for certain users, and with no common thread between those who can't access it.  I'm one of those users.  If I try to access it, I receive the following error on the client side:

"the remote computer disconnected the session because of an error in the licensing protocol.  please try connecting to the remote computer again or contact your server administrator."

A corresponding event shows up in the system log on the terminal server:

Source: TermService
Category: None
EventID: 1004

The terminal server cannot issue a client license.

In addition, there's a frequently logged event in the application log on TS:

Source: LicenseService
Category: None
EventID: 213

Replication of license information failed because the license logging service on server \\servername could not be contacted.

Obviously, it seems like there's some communication breakdown between the TS in question and the LS.  I can ping the license server from the TS, I can access shares, etc...there doesn't seem to be a connectivity issue.  Running LSView from the TS detects the proper license server, and it doesn't appear to be a CAL issue, because I've verified that we have more than enough CALs, and besides that...there's no issue remoting on to any other server.

I'm at my wits end here, PLEASE help!!
0
GibsonGuitarIT
Asked:
GibsonGuitarIT
  • 7
  • 6
1 Solution
 
zelron22Commented:
You're probably out of licenses.  Are your other terminal servers also 2000, or are the 2003?  With 2000, it doesn't release the licenses so you periodically have to call up (or apply via the license server) Microsoft fullfillment and say, "Yo, we need some more licenses!".
0
 
GibsonGuitarITAuthor Commented:
I had that thought as well, but the TS is 2000, but on the license server it shows that I have "unlimited" available windows2000 TS licenses...and none issued.

Any other ideas?
0
 
zelron22Commented:
Stupid question no. 1: have you rebooted it?
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
GibsonGuitarITAuthor Commented:
not a stupid question...but step one, nonetheless :)

many, many times...several of the fixes i've found on the web have necessitated it...but...no happiness there.  The issue seems to be with devices that weren't previously issued a CAL.  The ones that can connect did so previously.  For good measure, I acquired another 25 W2K per device CALs and installed them on my license server...made no difference whatsoever.
0
 
GibsonGuitarITAuthor Commented:
any other ideas?  I'm running out of time and options, and I'd hate to burn one of our EA-included microsoft calls on something that likely has a glaring answer that I'm overlooking.
0
 
zelron22Commented:
Are all of the devices the same OS?
0
 
zelron22Commented:
Have you restarted the license server?  Did anything change around the time this problem occurred?
0
 
zelron22Commented:
New AV installed?  Firewall?
0
 
GibsonGuitarITAuthor Commented:
All devices are Windows XP Pro.   The server in question is our only remaining W2K server.  No new AV or firewall installs.
0
 
zelron22Commented:
Is the license server a domain controller?  Is it W2k3?

Just noticed your username.  I got a tour of the old Gibson factory (Gibson wasn't in it any more, some small guitar company was) in Kalamazoo years ago.  The company I was doing work for shared the building.  At least, I think it was the company in Kalamazoo.
0
 
GibsonGuitarITAuthor Commented:
Yeah, it's a W2K3 DC.

We're based in Nashville.  Gibson moved from Kalamazoo in 1973, I believe.

I wasn't around, at that point :)
0
 
GibsonGuitarITAuthor Commented:
GOT IT.  Somehow I missed, under "parameters" the defaultlicenseserver key, which was hard-coded to point to the old license server.  I can stop tearing my hair out.

Thanks again :)
0
 
zelron22Commented:
Ah, so something DID change.   woof.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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