Good day Benjie Meneses,
The reason this happens is that even though your server only runs the Remote Desktop Licensing role, it still participates in the RDP connection process. When you connect via RDP, the client may briefly try to check for license information on the target server.
In your case, the Licensing Server might have momentarily failed to reach itself or another license source due to a temporary network issue, DNS glitch, or service delay.
Please make sure the Remote Desktop Licensing service is running and set to Automatic (Delayed Start). Also, check the RDS configuration in Server Manager to confirm that no specific license server is defined. That’s the correct setup for a licensing-only server.
This type of error usually clears up on the next connection attempt. If it happens again, check the Event Viewer for more detailed logs.
Please let me know if these steps help stabilize the connection! And if this answers your question, feel free to click “Accept Answer” so others can benefit from it as well 😊
Jason,