When attempting to connect to a Windows Server using Remote Desktop Protocol (RDP), you may encounter an error indicating that the maximum number of connections has been exceeded, the server is busy, or no additional Remote Desktop connections are available.

This problem is especially common on servers where administrators or users frequently disconnect RDP sessions instead of properly signing out.

It can also occur because of:

• Windows Server administrative RDP limits
• Disconnected or abandoned sessions
• Incorrect Group Policy configuration
• RDS connection limits
• Remote Desktop Session Host configuration
• Multiple sessions belonging to the same user
• Improper session timeout policies
• RDS licensing or deployment configuration
• Stuck or ghost sessions
• RDP listener/service problems

The important point is that this error does not necessarily mean that many people are actively working on the server. Windows may still be maintaining sessions that appear disconnected but continue consuming server resources and session capacity.

Microsoft confirms that Remote Desktop for administration supports two concurrent remote administrative connections. Environments requiring more concurrent user connections need a properly configured Remote Desktop Session Host deployment and the appropriate RDS CALs.

Understanding the Difference Between Remote Desktop Administration and RDS

Before changing any configuration, determine how the server is being used.

Scenario 1 – Remote Desktop for Server Administration

If you have a normal Windows Server installation and RDP is being used only by administrators for server management, Windows provides up to two concurrent remote administrative connections without requiring RDS CALs for those administrative connections.

For example:

• Administrator A connects to the server.
• Administrator B connects to the server.
• Administrator C attempts to connect.

The third administrator may be unable to establish another normal administrative RDP connection.

You should not attempt to bypass this limitation by simply changing registry or Group Policy values.

If the server is intended for multiple employees to run applications or desktops concurrently, deploy Remote Desktop Services correctly.

Scenario 2 – Remote Desktop Session Host / Multi-User RDS Server

An RDS server is different.

A properly configured RD Session Host can support many simultaneous users depending on:

• Server hardware
• RDS architecture
• Application workload
• RDS configuration
• RDS CAL availability
• Group Policy
• Session limits
• Licensing mode
• Network capacity

Microsoft states that allowing more than the two administrative connections or supporting multiple user connections requires the Remote Desktop Session Host role and appropriate RDS CALs.

Therefore, if 10, 20, 30, or more employees are supposed to work simultaneously, the correct solution is an RDS deployment—not trying to increase the administrative RDP limit.

Why Does the Maximum Connections Error Occur?

1. Users Disconnect Instead of Signing Out

This is one of the most common causes.

When a user closes the Remote Desktop window using the X button, the session normally becomes disconnected.

The user is no longer looking at the desktop, but the session can continue running on the server.

Applications may remain open, including:

• Microsoft Excel
• Microsoft Word
• Google Chrome
• Accounting applications
• ERP applications
• Database clients
• Outlook
• Background applications

Microsoft documents that disconnected sessions can continue running, and by default they can remain maintained unless session timeout policies are configured.

Therefore:

Disconnect ≠ Logoff

A disconnected user may still have a live Windows session.

2. Multiple Disconnected Sessions Exist

Consider a server showing:

Administrator       Active
User01              Disc
User02              Disc
User03              Disc
User04              Disc

Only Administrator may currently be working, but four additional sessions remain on the server.

These abandoned sessions consume resources and, depending on configuration, can contribute to session-capacity problems.

3. Group Policy Is Limiting the Number of Connections

Windows includes a policy called:

Limit number of connections

Check it at:

Computer Configuration
   > Administrative Templates
      > Windows Components
         > Remote Desktop Services
            > Remote Desktop Session Host
               > Connections
                  > Limit number of connections

This policy controls the maximum number of simultaneous Remote Desktop Services connections.

Microsoft documents this policy as a mechanism for limiting simultaneous connections to an RD Session Host server.

If someone has configured this value too low, legitimate RDS users may be prevented from connecting.

4. Sessions Are Never Automatically Logged Off

Another common configuration problem is allowing disconnected sessions to remain indefinitely.

For example, a user connects at 9:00 AM, works for an hour, and then closes the RDP window.

The session becomes:

Disc

If no disconnected-session timeout has been configured, that session can remain on the server for a long time.

Repeated over days or weeks, this can result in many abandoned sessions.

5. User Creates Multiple Sessions

Depending on your RDS configuration, the same user may potentially create multiple sessions instead of reconnecting to the existing session.

You should review the policy:

Computer Configuration
 > Administrative Templates
 > Windows Components
 > Remote Desktop Services
 > Remote Desktop Session Host
 > Connections

and examine the setting:

Restrict Remote Desktop Services users to a single Remote Desktop Services session

For many business RDS environments, restricting each user to one session can simplify session management and reduce unnecessary duplicate sessions.

However, configure this according to your actual application and operational requirements.

Quick Fix: Check Existing RDP Sessions

If you have local/console access, virtualization console access, or another administrative session, open:

Command Prompt as Administrator

Run:

query user

or:

qwinsta

qwinsta displays Remote Desktop sessions running on the server, including their usernames, IDs, and states. Microsoft notes that qwinsta is equivalent to query session.

Example:

USERNAME          SESSIONNAME       ID    STATE
Administrator     rdp-tcp#5          2    Active
User01            rdp-tcp#8          4    Disc
User02            rdp-tcp#10         7    Disc
User03            rdp-tcp#12         9    Active

The important columns are:

USERNAME – Windows user account

ID – Session ID

STATE – Current session state

Common states include:

Active
Disc
Listen

How to Log Off a Disconnected RDP Session

Suppose:

query user

shows:

User01          4    Disc

Run:

logoff 4

where 4 is the session ID.

Microsoft's logoff command ends the user's session, terminates the processes in that session, and deletes the session.

Then run:

query user

again.

The disconnected session should disappear.

Important Warning

Logging off a user closes applications running inside that session.

Unsaved work may be lost.

Microsoft specifically warns administrators that forcing another user's session to log off without warning can cause data loss.

Always verify that the session is safe to terminate whenever possible.

Using Task Manager to Remove Disconnected Sessions

You can also use the graphical interface.

Open:

Task Manager

Select:

Users

You may see users such as:

Administrator       Active
Accounts            Disconnected
User01              Disconnected
User02              Active

Right-click the unwanted disconnected user and choose:

Sign off

Confirm the operation.

Again, do this carefully because applications and unsaved documents in that session will be terminated.

Emergency Administrative Connection Using MSTSC /ADMIN

If normal administrative RDP access is unavailable, an administrator can try:

mstsc /admin

Press:

Win + R

and enter:

mstsc /admin

Then connect to the server.

This requests an administrative session and is useful for server administration scenarios.

However, /admin is not a method for bypassing RDS licensing or creating unlimited user sessions.

Once connected, inspect existing sessions:

query user

and safely log off abandoned sessions where appropriate.

Check Whether the RDP Listener Is Working

Run:

qwinsta

Look for:

rdp-tcp        Listen

Microsoft recommends checking qwinsta when troubleshooting whether the RDP-TCP listener is available.

You can also check port 3389:

netstat -ano | findstr :3389

Normally, RDP uses TCP port:

3389

You should see a listening entry when the standard RDP listener is operating.

Note that organizations can configure RDP to use a different port.

Check Remote Desktop Services

Open:

services.msc

Locate:

Remote Desktop Services

The service name is commonly:

TermService

Verify that it is running.

Restarting Remote Desktop Services can disrupt active Remote Desktop users, so it should not be your first troubleshooting step on a production server.

Configure the RDP Connection Limit Correctly

Open:

gpedit.msc

Navigate to:

Computer Configuration
 > Administrative Templates
 > Windows Components
 > Remote Desktop Services
 > Remote Desktop Session Host
 > Connections

Open:

Limit number of connections

Microsoft documents that this policy can limit the number of simultaneous RDS sessions. If the configured number is exceeded, additional connections can be refused.

For an RD Session Host environment, configure the value according to your licensed and supported RDS design.

Do not use this setting as a way to bypass Microsoft's RDS licensing requirements.

Apply Group Policy Changes

After changing applicable policies, run:

gpupdate /force

Some RDS settings may require users to reconnect, a service restart, or a server restart before their behavior is fully reflected.

On a production RDS server, schedule disruptive changes during a maintenance window whenever possible.

Configure Automatic Cleanup of Disconnected Sessions

This is one of the best long-term solutions.

Open:

gpedit.msc

Navigate to:

Computer Configuration
 > Administrative Templates
 > Windows Components
 > Remote Desktop Services
 > Remote Desktop Session Host
 > Session Time Limits

Look for:

Set time limit for disconnected sessions

Microsoft documents that disconnected sessions can otherwise remain active indefinitely and that this policy can specify how long a disconnected session is retained.

For example, an organization might configure disconnected sessions to be removed after:

1 hour
2 hours
4 hours
8 hours
1 day

The correct value depends on business requirements.

Consider “End Session When Time Limits Are Reached”

Within:

Remote Desktop Session Host
 > Session Time Limits

review the policies controlling what happens when session time limits are reached.

There is an important difference between:

Disconnecting a session

and

Ending/logging off a session

Disconnecting leaves the user's Windows environment and applications running.

Ending the session closes the applications and terminates the session.

Choose policies carefully because forced logoff can cause unsaved user data to be lost.

Active, Idle, Locked and Disconnected Sessions

Understanding session states makes RDP troubleshooting much easier.

Microsoft describes several common RDS states, including Active, Idle, Locked, and Disconnected.

Active

The user is connected and actively working.

Idle

The user is connected but has not interacted with the session for a period of time.

Locked

The Windows session remains present but is at the lock/sign-in screen.

Disconnected

The network/RDP connection has ended, but the Windows session continues running on the server.

This last state is responsible for many session-management problems.

Check Sessions on Another Server

If you have administrative permissions, you can query a specific RD Session Host:

qwinsta /server:SERVER01

Microsoft supports the /server:<servername> parameter for querying sessions on another RD Session Host.

Similarly, a session can be logged off from a specified server:

logoff 7 /server:SERVER01

Use extreme caution when doing this remotely.

Check RDS Licensing

If the server is being used by multiple employees, verify that Remote Desktop Services is correctly deployed and licensed.

Review:

Server Manager
 > Remote Desktop Services

and the relevant licensing configuration.

A production RDS environment generally requires appropriate:

• Windows Server licensing
• Remote Desktop Services CALs
• Correct RDS licensing mode
• Correct RD Licensing Server configuration

RDS CALs are generally deployed as:

• Per User
• Per Device

The appropriate model depends on the organization's licensing requirements.

A licensing problem can produce RDS access problems, although it should not automatically be assumed to be the cause of every maximum-connections error.

Do Not Confuse Windows Server RDP with Windows Desktop Editions

Windows Server Remote Desktop and client Windows Remote Desktop are not equivalent multi-user platforms.

A Windows 10 or Windows 11 PC should not be treated as a substitute for a licensed multi-user Windows Server RDS environment simply by modifying registry entries, patching system files, or using unsupported RDP wrappers.

For business multi-user environments, use an appropriately licensed Windows Server/RDS architecture.

Recommended Troubleshooting Sequence

When users report that RDP has reached the maximum number of connections, use this order:

Step 1 – Confirm the Server Is Reachable

Test:

ping SERVER-IP

If ICMP is intentionally blocked, ping failure alone does not prove that the server is offline.

Test the actual RDP service or port instead.

Step 2 – Try Administrative Access

Run:

mstsc /admin

If you gain access, continue troubleshooting from the server.

Step 3 – Check Sessions

Run:

query user

and:

qwinsta

Look for excessive:

Disc

sessions.

Step 4 – Log Off Abandoned Sessions

Example:

logoff 5

Then check again:

query user

Step 5 – Check Group Policy

Run:

gpedit.msc

Review:

Remote Desktop Session Host
 > Connections

especially:

Limit number of connections

Step 6 – Check Session Time Limits

Review:

Remote Desktop Session Host
 > Session Time Limits

Configure disconnected-session cleanup according to company policy.

Step 7 – Verify RDP Listener

Run:

qwinsta

Confirm that the RDP listener is in a listening state.

Then:

netstat -ano | findstr :3389

Step 8 – Check Remote Desktop Services

Run:

services.msc

Verify:

Remote Desktop Services

is operational.

Step 9 – Verify RDS Deployment and Licensing

If the machine serves multiple concurrent employees, confirm that it is actually configured as an RD Session Host with appropriate RDS licensing.

Step 10 – Restart Only When Necessary

If sessions, services, or the RDP subsystem are genuinely stuck, a server restart may clear the condition.

However, restarting a production RDS server will disconnect users and terminate their applications.

Use it as a controlled maintenance action—not the default solution.

PowerShell and Command-Line Diagnostic Commands

Useful commands for an RDP administrator include:

query user

Displays logged-on user sessions.

query session

Displays session information.

qwinsta

Displays Remote Desktop session information.

logoff SESSION-ID

Logs off a specified session.

gpupdate /force

Refreshes Group Policy.

netstat -ano | findstr :3389

Checks whether the standard RDP port is listening.

You can also examine the Remote Desktop Services service:

Get-Service TermService

This helps determine whether Remote Desktop Services is running.

Example Troubleshooting Scenario

Suppose a Windows Server is used by administrators and suddenly a new RDP connection reports that the maximum number of connections has been exceeded.

An administrator gains console access and runs:

query user

Output:

USERNAME          ID     STATE
Administrator      1     Disc
Administrator      2     Disc

Both administrative sessions are disconnected but still exist.

After verifying that there is no unsaved work, the administrator logs off one abandoned session:

logoff 1

A connection slot becomes available.

The administrator should then investigate why disconnected sessions are accumulating and configure appropriate session timeout policies rather than repeatedly terminating them manually.

Common Mistake: Closing the RDP Window

Users frequently click:

X

on the Remote Desktop window.

This normally disconnects the session.

A better practice when the user has completely finished working is:

Start
 > User/Profile
 > Sign out

Signing out closes the user's applications and releases the session.

However, disconnecting is useful when users intentionally want applications to continue running and plan to reconnect later.

The correct choice therefore depends on the workload.

Recommended RDS Policy for Business Servers

There is no universal timeout that is correct for every organization.

A practical configuration might include:

Disconnected Session Limit:
1–8 hours depending on business requirements.

Idle Session Limit:
Configured according to security and operational requirements.

Single Session Per User:
Often useful in standard office RDS deployments.

Connection Limit:
Configured according to the properly licensed RDS deployment and server capacity.

Do not set aggressive session limits without consulting users because accounting software, exports, reports, database operations, and other long-running processes may still be executing inside an apparently idle session.

Security Considerations

Do not solve RDP connection problems by weakening security unnecessarily.

Avoid:

• Disabling Network Level Authentication without a specific reason
• Exposing TCP 3389 directly to the public Internet
• Giving every RDP user administrator privileges
• Using unsupported RDP patches
• Circumventing RDS licensing
• Disabling Windows Firewall unnecessarily
• Sharing administrator accounts among employees

For Internet-facing access, consider properly configured technologies such as:

• RD Gateway
• VPN
• Zero Trust access solutions
• Multi-factor authentication
• Network-level firewall restrictions

Event Viewer Troubleshooting

For persistent RDP problems, check:

Event Viewer

Review:

Applications and Services Logs
 > Microsoft
 > Windows

Relevant Remote Desktop-related logs can help identify:

• Authentication failures
• Session creation problems
• Session disconnections
• RDP listener errors
• Licensing issues
• Transport problems
• RemoteConnectionManager events
• LocalSessionManager events

Event logs are especially important when clearing disconnected sessions temporarily fixes the problem but it repeatedly returns.

Preventing the Error Permanently

The best solution is not repeatedly rebooting the server.

Instead:

1. Identify whether the server is being used for administration or as a multi-user RDS server.
2. Deploy RDS correctly if multiple concurrent users are required.
3. Configure appropriate RDS CALs.
4. Prevent unnecessary duplicate sessions.
5. Configure disconnected-session time limits.
6. Train users on the difference between Disconnect and Sign out.
7. Monitor active and disconnected sessions.
8. Review RDS Group Policy settings.
9. Investigate recurring ghost or stuck sessions.
10. Maintain adequate CPU, RAM, storage, and network capacity.

Frequently Asked Questions (FAQ)

1. What does “maximum number of connections exceeded” mean in RDP?

It generally means that the server has reached a configured or platform-specific Remote Desktop connection/session limit, or existing sessions are consuming available capacity.

2. How many administrative RDP connections does Windows Server allow?

Windows Server Remote Desktop for administration supports two concurrent remote administrative connections without requiring RDS CALs for those administrative connections.

For larger multi-user environments, use Remote Desktop Session Host with appropriate RDS licensing.

3. How can I check who is connected through RDP?

Run:

query user

or:

qwinsta

4. How do I remove a disconnected RDP session?

First identify its session ID:

query user

Then:

logoff SESSION-ID

Example:

logoff 7

5. Will logoff close the user's applications?

Yes.

Microsoft states that after a user is logged off, processes in that session end and the session is deleted.

Unsaved work can therefore be lost.

6. Does closing the RDP window log off the user?

Normally, no.

Closing the RDP client usually disconnects the session while applications continue running on the server.

7. Why do disconnected sessions remain on the server?

RDS is designed to allow users to reconnect to their previous sessions. Depending on policy configuration, disconnected sessions can remain for an extended or unlimited period.

8. Can I automatically log off disconnected RDP users?

Yes.

Configure:

Remote Desktop Session Host
 > Session Time Limits
 > Set time limit for disconnected sessions

Choose a timeout appropriate for your organization.

9. What is mstsc /admin?

It starts Remote Desktop Connection requesting an administrative session.

Run:

mstsc /admin

It can be useful for server administration but does not bypass RDS licensing requirements.

10. Can I simply increase the RDP connection limit?

On an RD Session Host, connection limits can be configured, but the server must still comply with Windows Server and Remote Desktop Services licensing requirements.

Increasing a Group Policy number does not create additional RDS licenses.

11. Do I need RDS CALs for more than two simultaneous users?

For users connecting to a Windows Server through Remote Desktop Services to run desktops/applications—not merely the two administrative connections—you need a correctly configured RDS deployment and appropriate RDS CALs.

12. What is a disconnected RDP session?

It is a Windows session where the user's RDP connection has ended but the user's session and applications remain running on the server.

13. Can disconnected sessions consume RAM?

Yes.

Applications and processes inside the session may continue running, so disconnected sessions can continue consuming memory and other server resources.

14. Can disconnected sessions consume CPU?

Yes.

If applications inside the session continue performing work, they can continue consuming CPU even though the user is disconnected.

15. How do I see RDP session IDs?

Run:

query user

or:

qwinsta

The output includes session IDs.

16. Can I log off another user's session remotely?

Administrators with the necessary permissions can log off sessions on an RD Session Host, including by specifying the target server:

logoff 7 /server:SERVER01

Microsoft notes that appropriate permissions are required to log off another user's session.

17. What port does RDP normally use?

The default RDP port is:

TCP 3389

Organizations may configure a different port.

18. How do I check whether RDP is listening?

Run:

qwinsta

and verify the RDP-TCP listener.

You can also run:

netstat -ano | findstr :3389

for the default RDP port.

19. Should I restart Remote Desktop Services?

Only when necessary.

Restarting Remote Desktop Services can disrupt active sessions, so first investigate session limits, disconnected users, policies, listener status, and RDS configuration.

20. Should I reboot the server when maximum connections are exceeded?

A reboot may clear stuck sessions, but it should not be the first solution.

Use:

query user
qwinsta

and investigate the configuration first.

21. What is the best permanent fix?

The permanent solution is proper session management:

• Correct RDS deployment
• Appropriate RDS licensing
• Appropriate connection limits
• Disconnected-session timeouts
• Single-session policies where appropriate
• User training
• Regular monitoring

22. Why does the same user appear more than once?

The server may be configured to permit multiple sessions per user, or an existing session may not have been reconnected correctly.

Review the Restrict Remote Desktop Services users to a single Remote Desktop Services session policy.

23. Can I force all disconnected users to log off?

Technically yes, but use extreme caution.

Microsoft specifically warns that forcibly logging off sessions can cause loss of unsaved data.

For production environments, automated timeout policies are generally safer than indiscriminately terminating every session.

24. Does a disconnected RDP session mean the user is still logged in?

Yes.

Disconnected and logged off are different states.

A disconnected user's Windows session may still exist and applications may continue running.

25. Is the maximum-connections error always an RDS licensing problem?

No.

It can result from:

• Administrative connection limits
• Group Policy
• Disconnected sessions
• Session limits
• RDS configuration
• Duplicate sessions
• Stuck sessions
• Licensing configuration

Troubleshoot the actual cause before changing licensing or server settings.

Conclusion

The “Maximum Number of Connections Exceeded” RDP error is usually a session-management or configuration issue rather than a reason to immediately reboot the server.

Start by checking:

query user

and:

qwinsta

If abandoned disconnected sessions exist, verify that they can safely be terminated and then use:

logoff SESSION-ID

For a permanent solution, configure appropriate disconnected-session timeouts, review RDS Group Policy, prevent unnecessary duplicate sessions, and ensure that servers supporting multiple simultaneous employees are deployed and licensed correctly as Remote Desktop Session Hosts.

Most importantly, remember:

Disconnect keeps the session alive.

Sign out ends the session.

Understanding that distinction prevents a large percentage of recurring RDP session-capacity problems.

Tags

#RDP #RemoteDesktop #RemoteDesktopProtocol #WindowsServer #RDSError #RDPError #MaximumConnections #RemoteDesktopServices #RDS #RDSessionHost #WindowsServer2025 #WindowsServer2022 #WindowsServer2019 #WindowsServer2016 #RDPTroubleshooting #WindowsTroubleshooting #SystemAdministrator #SysAdmin #ITSupport #ITAdministrator #NetworkAdministrator #ServerAdministration #WindowsAdmin #RemoteAccess #RDPConnection #RDPSession #DisconnectedSession #IdleSession #RDPUsers #QueryUser #Qwinsta #WindowsCommands #PowerShell #GroupPolicy #GPO #RDSPolicy #SessionTimeout #RDSLicensing #RDSCAL #RemoteDesktopLicensing #MSTSC #MSTSCAdmin #TCP3389 #TermService #WindowsNetworking #ServerManagement #EnterpriseIT #ITInfrastructure #TechnicalSupport #KnowledgeBase