RDP Not Working? Complete Remote Desktop Troubleshooting Guide for Windows 10 & 11 (2026)

Remote Desktop Protocol (RDP) is one of the most useful tools built into Windows. It allows users to access another computer remotely as if they were sitting directly in front of it. Businesses use it for remote support, system administration, and accessing office computers from home. Students and IT professionals use it to manage servers, labs, and virtual machines.

However, one of the most frustrating situations occurs when the network appears to be working correctly, ping tests are successful, but Remote Desktop refuses to connect.

Many online guides provide quick fixes without explaining how RDP actually works or how to systematically identify the root cause. As a result, users often spend hours trying random solutions.

This guide provides a complete troubleshooting process that helps you identify exactly where the problem lies and how to fix it.

Understanding How RDP Works

Before troubleshooting, it is important to understand the components involved in a successful Remote Desktop connection.

For an RDP connection to work:

• The target computer must be reachable on the network.

• Remote Desktop must be enabled.

• The Remote Desktop Services service must be running.

• TCP Port 3389 must be listening.

• Windows Firewall must allow RDP traffic.

• The user account must have permission to log in remotely.

• Authentication and security policies must allow the connection.

If any one of these components fails, the connection may not work.

The First Question: Can You Ping the Remote Computer?

Open Command Prompt on the client computer and run:

ping 192.168.1.10

Replace the IP address with that of the target computer.

Successful Result

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

This means:

• The remote computer is online.

• The network path is working.

• Basic communication exists between both devices.

Important

A successful ping does not mean RDP should work.

Ping uses ICMP packets, while Remote Desktop uses TCP Port 3389.

You can successfully ping a computer and still be unable to establish a Remote Desktop connection.

Step 1: Test Port 3389

On the client computer, open PowerShell and run:

Test-NetConnection 192.168.1.10 -Port 3389

Scenario 1: TcpTestSucceeded = True

If you receive:

TcpTestSucceeded : True

This means:

• Port 3389 is reachable.

• The RDP service is responding.

The problem is likely related to authentication, user permissions, or security settings.

Scenario 2: TcpTestSucceeded = False

If you receive:

TcpTestSucceeded : False

This means:

• Port 3389 is blocked.

• The service is not listening.

• A firewall is preventing access.

• Network policies are restricting connections.

Continue to the next steps.

Step 2: Verify That Remote Desktop Is Enabled

On the target computer:

1. Open Settings.

2. Navigate to:

System → Remote Desktop

3. Ensure Remote Desktop is turned ON.

Many users assume RDP is enabled because it worked previously. Windows updates, policy changes, or system modifications can sometimes disable it.

If Remote Desktop was disabled:

1. Enable it.

2. Restart the computer.

3. Test again.

Step 3: Verify the Remote Desktop Service Is Running

Remote Desktop relies on a Windows service called Remote Desktop Services.

To verify:

1. Press Windows + R

2. Type:

services.msc

3. Press Enter.

Locate:

Remote Desktop Services

Expected Status

Running

If the Service Is Stopped

1. Right-click the service.

2. Click Start.

3. Set Startup Type to Automatic.

Restart the computer and test again.

Step 4: Check Whether Port 3389 Is Listening

Even if Remote Desktop is enabled, Windows must still listen on Port 3389.

On the target computer, open Command Prompt and run:

netstat -an | find "3389"

Expected Output

TCP    0.0.0.0:3389    LISTENING

or

TCP    [::]:3389    LISTENING

What If Nothing Appears?

This is one of the most important troubleshooting clues.

If no result appears:

• The RDP service is not listening.

• The service may be stuck.

• RDP may not be properly enabled.

• Registry settings may be corrupted.

Solution

Restart the service:

net stop termservice
net start termservice

Or simply reboot the machine and test again.

If the port still does not appear, continue with the next section.

Step 5: Verify Windows Allows RDP Connections

Open PowerShell as Administrator on the target computer and run:

Get-ItemProperty -Path "HKLM:\System\CurrentControlSet\Control\Terminal Server" -Name fDenyTSConnections

Interpretation

0 = RDP Allowed
1 = RDP Blocked

If the Value Is 1

Run:

Set-ItemProperty -Path "HKLM:\System\CurrentControlSet\Control\Terminal Server" -Name fDenyTSConnections -Value 0

Restart the computer.

Step 6: Check Firewall Rules

Windows Firewall is responsible for a large percentage of RDP failures.

Open PowerShell as Administrator and run:

Get-NetFirewallRule -DisplayGroup "Remote Desktop"

Review the rules.

If they are disabled:

Enable-NetFirewallRule -DisplayGroup "Remote Desktop"

Advanced Firewall Test

To determine whether the firewall is the problem:

Temporarily disable the Private profile:

Set-NetFirewallProfile -Profile Private -Enabled False

Attempt to connect.

Results

If RDP starts working:

• Firewall configuration is the issue.

If RDP still fails:

• Continue troubleshooting.

Re-enable the firewall:

Set-NetFirewallProfile -Profile Private -Enabled True

Step 7: Verify Network Profile Settings

Windows treats Public and Private networks differently.

If the network is marked as Public:

• Incoming RDP connections may be blocked.

Check:

Settings → Network & Internet

Select the active connection and ensure:

Private Network

is selected.

Step 8: Verify User Permissions

Even if everything else is configured correctly, the user account may not have permission to connect remotely.

On the target computer:

1. Open:

System → Remote Desktop

2. Click:

Select users that can remotely access this PC

3. Add the required user account.

Additional Requirement

The user account should have a password.

Windows frequently blocks remote logins for local accounts that have blank passwords.

Step 9: Check Whether Port 3389 Has Been Changed

Although uncommon, administrators sometimes change the default RDP port.

Check the configured port:

Get-ItemProperty -Path "HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" -Name PortNumber

Expected value:

3389

If a different value is returned, connect using that port or restore the default configuration.

Step 10: Check for Group Policy Restrictions

In business environments, Group Policy may prevent Remote Desktop access.

Open:

gpedit.msc

Navigate to:

Computer Configuration
  → Administrative Templates
    → Windows Components
      → Remote Desktop Services

Review all Remote Desktop-related policies.

Domain administrators may also enforce restrictions that override local settings.

Step 11: Review Event Logs

If all settings appear correct but RDP still fails, Windows Event Viewer often reveals the real problem.

Open:

eventvwr.msc

Navigate to:

Applications and Services Logs
 → Microsoft
   → Windows
     → TerminalServices-LocalSessionManager

and

Applications and Services Logs
 → Microsoft
   → Windows
     → TerminalServices-RemoteConnectionManager

Look for warnings and errors generated during connection attempts.

These logs often identify:

• Authentication failures

• Service issues

• Listener problems

• Permission errors

• Policy restrictions

Common RDP Error Messages and Their Meaning

"Remote Desktop Can't Connect to the Remote Computer"

Possible causes:

• Firewall blocking Port 3389

• RDP disabled

• Incorrect IP address

• Service not running

"An Internal Error Has Occurred"

Possible causes:

• Corrupted RDP configuration

• Network issues

• Authentication problems

• Security policy conflicts

"Your Credentials Did Not Work"

Possible causes:

• Incorrect username

• Incorrect password

• User lacks RDP permissions

"The Remote Computer Requires Network Level Authentication"

Possible causes:

• Authentication mismatch

• Older RDP client

• NLA configuration issue

Recommended Troubleshooting Order

When diagnosing Remote Desktop problems, always follow this sequence:

1. Verify the correct IP address.

2. Test ping.

3. Test Port 3389.

4. Confirm Remote Desktop is enabled.

5. Verify Remote Desktop Services is running.

6. Confirm Port 3389 is listening.

7. Review firewall settings.

8. Verify the network profile is Private.

9. Check user permissions.

10. Review Event Viewer logs.

Following this order prevents unnecessary guesswork and quickly isolates the root cause.

Conclusion

Most Remote Desktop failures occur because one of five things is wrong:

• Remote Desktop is disabled.

• Port 3389 is blocked.

• The Remote Desktop service is not running.

• Firewall rules are preventing access.

• The user lacks permission to connect.

The key to successful troubleshooting is not trying random fixes but following a structured process. By testing each component in order, you can identify the exact cause of the problem and resolve it efficiently.

Whether you are an IT technician, student, system administrator, or business user, mastering this troubleshooting approach will save time and help you solve Remote Desktop issues with confidence.