Share via

Unable to connect to RDP. Error code 0*101

Anonymous
2024-01-02T11:22:15+00:00

I am writing to bring to your attention an issue I've been experiencing while trying to establish a Remote Desktop connection. I have encountered the following error message:

"We couldn't connect to the remote PC because of a licensing error. If this keeps happening, contact your network administrator for assistance."

Additionally, when my manager attempted to connect, they received the following error:
"The remote session was disconnected because there are no remote desktop license servers."

Given the urgency and importance of this issue, I kindly request your assistance in resolving the licensing error. It appears there might be a discrepancy or issue related to our Remote Desktop Services (RDS) licensing or configuration.

Windows for business | Windows Server | User experience | Remote desktop services and terminal services

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-01-03T01:50:56+00:00

    Hello  Agatha B，

    Thank you for posting in Microsoft Community forum.

    From your error message，you seem not configure license server correctly.

    You can refer to the following steps：

    Step 1:Depending on whether you want to configure Group Policy centrally from your domain or locally on each session host:

    • Open the Group Policy Management Console (GPMC) and create or edit a policy that targets your session hosts.
    • Open the Local Group Policy Editor on the session host.

    Step 2:Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing.

    Step 3: In the policy list, right-click Use the specified Remote Desktop license servers, and then select Properties.

    Step 4: Select Enabled, and then enter the name(FQDN) or the IP of the license server under License servers to use. If you have more than one license server, use commas to separate their names.

    Step 5: Select OK.

    Step 6: In the policy list, right-click Set the Remote Desktop licensing mode, and then select Properties.

    Step 7: Select Enabled.

    Step 8: Under Specify the licensing mode for the Remote Desktop Session Host server, select Per Device or Per User, as appropriate for your deployment.

    After configuration, please check the registry.

    1.Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services

    LicensingMode, the value 4 for per user cal，the value 2 for per device cal

    2.Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core

    LicensingMode the value 4 for per user cal，the value 2 for per device cal

    3.Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TermService\Parameters\LicenseServers

    add string value: SpecifiedLicenseServers , value data is the FQDN OR IP address of license server

    4.Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsNT\Terminal Services,

    Add string value LicenseServers to specify a License Server, value data is the FQDN OR IP address of license server

    You can also find details in the following link.

    License Remote Desktop session hosts | Microsoft Learn

    I hope the information above is helpful.

    If you have any question or concern, please feel free to let us know.

    Best Regards,

    Haijian Shan

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2024-01-03T12:23:51+00:00

    This was already properly configured and it used to work perfectly until last week. Now, it doesn’t seem to work. What might be the cause for the same? Also, how to solve it now.

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-01-08T06:49:53+00:00

    Hello  Anna Ba，

    Thank you for your reply.

    This issue is a recent issue and may be caused by some adjustments you have made to some settings, such as Group Policy Update, Windows Update, etc. You currently need to check the error prompts in the Remote Desktop Licensing diagnostics on the session host server and make targeted fixes.

    Best Regards,

    Haijian Shan

    0 comments