RDP server refuses new connections: user limit or port conflict

Symptoms

• This computer can't connect to the remote computer - try connecting again.
• Only some users can connect; extra connections are refused.
• Or connections fail entirely while the server is up.

Fix it yourself

1. Remember plain Remote Desktop allows only two concurrent administrative connections without RDS CALs; more requires the RD Session Host role and licenses.
2. Check the 'Limit number of connections' Group Policy and the RDP-TCP Maximum connections setting on the host and raise them appropriately.
3. Verify the affected users have the required sign-in rights (Remote Desktop Users membership / logon rights).
4. Check for a port assignment conflict: confirm nothing else is using TCP 3389 (netstat -a) and that the RDP-TCP listener shows Listen state via qwinsta.
5. Restart Remote Desktop Services after configuration changes - this drops every active session on the host, so schedule it and warn connected users first - then retest.
6. Only after confirming with the affected users (unsaved work is lost when a session is logged off), disconnect or log off stale/idle sessions that are consuming the connection limit.

If that did not help

Attach qwinsta output, the connection-limit policy values, RDS licensing status, and netstat output for port 3389.