Remote Desktop is one of the most useful Windows features for accessing another computer remotely. It allows you to connect to a Windows PC from another device and use its desktop, applications, files, and other resources as if you were sitting in front of it.
However, Remote Desktop can sometimes stop working. You may see an error saying that the remote computer cannot be reached, the connection may be refused, or Windows may connect but fail to display the remote desktop.
The problem can be caused by Remote Desktop being disabled, an incorrect network configuration, Windows Firewall, the Remote Desktop service, incorrect credentials, an unsupported Windows edition, or problems with the remote computer itself.
The following methods cover the most common ways to fix Remote Desktop when it is not working in Windows 11.
Method 1: Make Sure Remote Desktop Is Enabled
The first thing to check is whether Remote Desktop is enabled on the computer you want to access.
- Press Windows + I to open Settings.
- Select System.
- Select Remote Desktop.
- Turn on Remote Desktop.
- Confirm the setting when Windows asks.
- Note the PC name shown on the Remote Desktop page.
You will need the computer name or IP address when connecting from another device.
If Remote Desktop is already enabled, turn it off, wait a few seconds, and enable it again.
Make sure you are performing this check on the remote computer, not only on the computer you are using to make the connection.
The remote PC must also be turned on and connected to the network.
Method 2: Check Whether Your Windows Edition Supports Remote Desktop
Not every Windows edition can act as a Remote Desktop host.
Windows 11 Pro, Enterprise, and Education editions support incoming Remote Desktop connections. Windows 11 Home does not normally provide the built-in Remote Desktop host feature.
To check your edition:
- Open Settings.
- Select System.
- Select About.
- Find Windows specifications.
- Check the Edition field.
If the remote computer is running Windows 11 Home, the built-in Remote Desktop host cannot normally be enabled through the standard Settings interface.
In that situation, you can use another remote-access solution or upgrade Windows to an edition that supports Remote Desktop hosting.
The computer from which you are connecting can use the Remote Desktop client even when it is running a different supported Windows edition.
Method 3: Check Your Network Connection
Remote Desktop requires network connectivity between the two computers.
First, make sure both computers are connected to the network.
On the remote computer, open Command Prompt and run:
ipconfigLook for the computer’s IPv4 address.
From the client computer, you can test whether the remote computer responds:
ping 192.168.1.100Replace the example address with the actual IP address of the remote computer.
If the ping fails, it does not always mean Remote Desktop itself is broken because Windows or the network may block ICMP traffic. However, it can help identify basic connectivity problems.
If both computers are on the same local network, verify that they are connected to the correct network and that network isolation is not preventing communication.
For connections over the internet, additional router, firewall, VPN, or network configuration may be required.
Method 4: Restart the Remote Desktop Services
Remote Desktop depends on Windows services. If the required service is stopped or stuck, connections may fail.
- Press Windows + R.
- Type:
services.msc- Press Enter.
- Find Remote Desktop Services.
- Check its status.
- Right-click it and select Restart if available.
- Open Properties if necessary.
- Check that the startup configuration is appropriate.
You can also restart the service from an elevated Command Prompt.
Open Command Prompt as administrator and run:
net stop termserviceThen run:
net start termserviceAfter restarting the service, try connecting again.
If Windows refuses to stop or start the service, restart the computer and test Remote Desktop again.
Method 5: Allow Remote Desktop Through Windows Firewall
Windows Firewall can block Remote Desktop connections even when Remote Desktop itself is enabled.
To check the firewall rules:
- Press Windows + R.
- Type:
wf.msc- Press Enter.
- Select Inbound Rules.
- Look for rules related to Remote Desktop.
- Make sure the appropriate Remote Desktop rules are enabled.
You can also use Windows Defender Firewall settings from Control Panel.
- Open Control Panel.
- Select System and Security.
- Select Windows Defender Firewall.
- Select Allow an app or feature through Windows Defender Firewall.
- Make sure Remote Desktop is allowed on the appropriate network profile.
Avoid disabling the entire Windows Firewall simply to test Remote Desktop. Enabling the required Remote Desktop rules is a safer approach.
If a third-party security application has its own firewall, check that application as well.
Method 6: Check Remote Desktop Settings and Network Profile
Windows networking settings can affect remote connections.
Open:
Settings > Network & internet
Check whether the computer is connected correctly.
For a private home or office network, make sure the network profile is configured appropriately.
You should also check the advanced Remote Desktop settings:
- Open Settings.
- Go to System > Remote Desktop.
- Open the available advanced settings.
- Review the Remote Desktop configuration.
- Make sure the required authentication settings are compatible with the client computer.
If Network Level Authentication is enabled, the connecting computer must be able to authenticate correctly before the remote desktop session is established.
If credentials are being rejected, confirm that you are using an account that is allowed to connect remotely.
Method 7: Add the User Account to Remote Desktop Users
A Windows account must have permission to connect through Remote Desktop.
Administrators can normally connect, while other accounts may need to be added to the Remote Desktop Users group.
To add an account:
- Press Windows + R.
- Type:
sysdm.cpl- Press Enter.
- Open the Remote tab.
- Select Select Users.
- Select Add.
- Enter the Windows username.
- Select Check Names.
- Select OK.
- Apply the changes.
You can then try connecting again using that account.
Make sure the username and password are correct.
If you are using a Microsoft account, the username format may not always be the same as the name displayed on the Windows Start menu. When authentication fails, verify the exact account credentials configured on the remote computer.
Method 8: Check the Remote Desktop Port and Network Configuration
Remote Desktop normally uses TCP port 3389.
If a firewall, router, VPN, security application, or another network configuration is blocking the required connection, Remote Desktop may fail.
On the remote computer, you can check whether Windows is listening on the standard Remote Desktop port.
Open Command Prompt as administrator and run:
netstat -an | findstr 3389If Remote Desktop is functioning normally, you may see a listening entry associated with the port.
You can also test the port from another Windows computer with PowerShell:
Test-NetConnection 192.168.1.100 -Port 3389Replace the IP address with the address of the remote PC.
Look at the TcpTestSucceeded result.
A successful connection indicates that the client can reach the specified port. If it fails, investigate the firewall, network, Remote Desktop service, VPN, or router configuration.
Common Remote Desktop Errors
Remote Desktop errors can have different causes.
If Windows says that the remote PC cannot be found, check the computer name and network connection.
If Windows says that the connection was refused, check whether Remote Desktop is enabled and whether the required service is running.
If the username or password is rejected, verify the account credentials and Remote Desktop permissions.
If the connection works on the local network but not over the internet, the issue may involve the router, VPN, firewall, or external network configuration.
Remote Desktop Works Locally but Not Over the Internet
A local Remote Desktop connection and an internet Remote Desktop connection are not the same thing.
If you can connect using the remote PC’s local IP address but cannot connect from outside your network, Remote Desktop itself may be working correctly.
The problem may instead involve:
- Router configuration.
- Firewall rules.
- VPN configuration.
- NAT.
- ISP restrictions.
- Public IP address changes.
- Port forwarding.
Exposing Remote Desktop directly to the public internet can increase security risks. For remote access from outside your home or office, using a properly configured VPN or another secure remote-access solution is generally preferable to exposing the Remote Desktop service unnecessarily.
If Remote Desktop Suddenly Stopped Working
If Remote Desktop worked previously and suddenly stopped, check recent changes first.
Windows updates, firewall changes, network changes, password changes, VPN configuration, and system restarts can affect remote connections.
Try these steps:
- Restart the remote PC.
- Restart the client PC.
- Check whether Remote Desktop is still enabled.
- Restart Remote Desktop Services.
- Check Windows Firewall.
- Confirm the remote computer’s IP address.
- Test the connection again.
If the remote computer received a new IP address from the router, using an old IP address can also cause the connection to fail.
Conclusion
When Remote Desktop is not working in Windows 11, start with the simplest checks. Make sure Remote Desktop is enabled on the remote computer and confirm that the Windows edition supports incoming Remote Desktop connections. Then check the network connection, Remote Desktop Services, Windows Firewall, and user permissions.
If the basic settings are correct, testing port 3389 can help determine whether the problem is related to network connectivity or the Remote Desktop service. Checking the remote computer’s IP address is also important because local network addresses can change.
For connections over the internet, additional networking and security configuration may be required. A Remote Desktop connection that works locally but fails remotely often points to a router, firewall, VPN, or NAT issue rather than a Windows Remote Desktop problem.
By checking each component systematically, you can usually identify whether the problem is caused by Windows settings, the user account, the firewall, the network, or the remote computer itself.
FAQs
1. Why is Remote Desktop not working on Windows 11?
Common causes include Remote Desktop being disabled, an unsupported Windows edition, network problems, Windows Firewall blocking the connection, stopped Remote Desktop services, or incorrect account permissions.
2. Does Windows 11 Home support Remote Desktop hosting?
Windows 11 Home does not normally provide the built-in Remote Desktop host feature. A supported Windows edition such as Pro is required for the standard incoming Remote Desktop feature.
3. What port does Windows Remote Desktop use?
The standard Remote Desktop port is TCP 3389. Firewall, router, or VPN configuration can prevent connections to this port.
4. Why does Remote Desktop work on the local network but not over the internet?
This commonly indicates a networking or remote-access configuration issue. Router NAT, firewall rules, VPN settings, public IP changes, or ISP restrictions can prevent an external connection even when local Remote Desktop works correctly.
Quick Summary
- Make sure Remote Desktop is enabled on the remote Windows 11 PC.
- Check the Windows edition, network connection, Remote Desktop service, and firewall.
- Confirm that the correct user account has permission to connect remotely.
- Use
Test-NetConnectionand port 3389 checks to diagnose network-related problems.