Windows Server remote prompts "You can provide a license because there is no Remote Desktop licensing server"

Recently has been very busy very busy, there is no time to take care of the blog, home basically is the rhythm of washing and sleeping, I really never thought before, I will have to go home do not want to touch the computer situation ... Not only do not want to touch the computer, and insomnia also disappeared, because it is too tired, finally have some benefits.

These days there are actually some can record work experience, helpless has no clue also has no time, just take advantage of today's lunch interval, first sorted out a small part of the good, otherwise the blog really waste ...

First, the failure case ①

When I added HTTPS to the test group's IIS this morning, I found the following error occurred remotely:

The remote session was interrupted because no Remote Desktop licensing server can provide a license. Please contact your server administrator.

degree, the original is also a very common mistake, explained as follows:

Windows Server 2008 R2 The remote session was interrupted because no Remote Desktop licensing server could provide a license.

Forget about the solution:

①, you can use the following command remote login:

MSTSC/V: Remote server IP address/admin

②, to completely resolve this problem, you will need to remove Remote Desktop services, as illustrated below:

Ps: But I turned on the admin did not seem to find Remote Desktop Services ...

Then when the new SSL encountered a small problem, to provide me with only Nginx certificate (Key and PEM), and the Web site is an IIS server, it is too troublesome to install Nginx agent.

I was going to apply for a Vauton free SSL certificate, and found that I did not get control of the domain name and had to rest. But in the end, I finished the task, the next article to continue to share.

The following additions were added to March 28, 2015:

Second, the failure case ②
After resolving the problem with the case ①, I accidentally discovered a new Remote Desktop Connection failure, as shown in figure:

The error message is: An authentication error occurred. Unable to connect to local security authority ...

Look at some similar cases on the Internet, the solution is mostly to modify some of the remote machine settings, and I follow the steps set after the still not. At the end of the 51CTO forum found a similar error prompted to solve the case, but also after the setting is indeed OK!

So, here's a note to make it easier for people to meet the same problems.

Workaround:

Network Connection Configuration--> dual-hit open Tcp/ipv4 configuration--> Select Advanced, locate the NetBIOS settings under the WINS tab, select Disable NetBIOS on TCP/IP, and then make sure.