Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Im using Remotedesktop Client 0.23 on Linux Mint. When im trying to connect to a windows server, I get the following error: Disconnect: No valid license available

I know that I'm supposed to delete a file, but I can't find it.

Anyone who can help me?

share|improve this question

closed as off-topic by jasonwryan, derobert, Anthon, Shawn J. Goff, Renan Jun 2 '14 at 21:52

  • This question does not appear to be about Unix or Linux within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

Are you sure there isn't actually a licensing issue with your Windows Server or Terminal Services setup? – derobert Jun 2 '14 at 20:30
@derobert: Can it be something wrong with the licensing on the windows server? What do you mean with Terminal Service setup? It has worked before. – user500468 Jun 2 '14 at 20:37
When I Google for that error message, I get a lot of results saying that its from not having Terminal Services licensing (on the Windows Server) properly configured: accidentally using 120-day temporary licenses, not being in per-connection mode, etc. – derobert Jun 2 '14 at 20:39
@derobert: So the problem is on the windows server? What is Terminal Services? – user500468 Jun 2 '14 at 20:41
This question appears to be off-topic because it is about Windows licensing. – jasonwryan Jun 2 '14 at 20:42
up vote 1 down vote accepted

I would also take a look at using xfreerdp as a client instead, we use it with Window's license server and it work fine. Also I found this thread which discusses the problem, titled: rdesktop 'disconnect: No valid license available.

There was a tip in that thread to try this as a potential workaround with rdesktop.

this is a workaround i've just seen that if you know the hostname's owner of a valid MS license (CAL temp license) you can use it this way:

  $ rdesktop -n 'hostname' serverhostname 
share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.