However, one common issue that users face is the error message: Remote access to the server is not enabled in Windows 10. This can be frustrating, especially when remote access is critical for work or troubleshooting. In this blog, we will explore the possible reasons for this issue and provide step-by-step solutions to enable remote access in Windows 10.
Understanding the Problem
Before diving into solutions, it’s essential to understand what causes the “Remote access to the server is not enabled in Windows 10” error. This error usually occurs when:
- Remote Desktop is disabled: Windows 10 requires Remote Desktop to be enabled on the target computer or server.
- Firewall settings are blocking Remote Desktop: Firewalls can block the necessary ports for Remote Desktop connections.
- Network-level authentication (NLA) issues: Remote Desktop often requires NLA for secure connections, which may not be configured correctly.
- Permissions are not granted: The user account attempting to connect may not have the required permissions.
- Services are not running: Certain Windows services need to be active for Remote Desktop to work properly.
Let’s look at how to resolve these issues step by step.
Step-by-Step Guide Remote Access to the Server Is Not Enabled in Windows 10
1. Enable Remote Desktop in Windows 10
The first step is to ensure that Remote Desktop is enabled on the target machine. Follow these steps:
- Open System Settings:
- Press Desktop Windows + I to open the Settings menu.
- Go to System > Remote Desktop.
- Enable Remote Desktop:
- Toggle the switch for On Remote Desktop to the “On” position.
- A confirmation prompt will appear. Click Confirm to enable the feature.
- Note the Computer Name:
- Under the Remote Desktop settings, note the computer name or IP address. You will want this information to connect remotely.
- Optional Settings:
- Click on Advanced settings to configure additional options, such as requiring network-level authentication (NLA) for more secure connections.
- Open System Settings:
If Remote Desktop was already enabled, proceed to the next steps to check for other potential issues.
2. Adjust Firewall Settings
Windows Defender Firewall may block Remote Desktop connections if it’s not configured correctly. To allow Remote Desktop through the firewall:
- Open Firewall Settings:
- Press Desktop Win + R, type control, & press Enter.
- Navigate to Method & Security > Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall.
- Enable Remote Desktop:
- See for Remote Desktop in the list of allowed apps.
- Ensure both Private and Public checkboxes are checked.
- Manually Open Ports (if needed):
- Open the command prompt and type netsh advfirewall firewall add rule name=”RDP” dir=in action=allow protocol=TCP localport=3389. This will manually open the default port (3389) Remote Desktop uses.
- Open Firewall Settings:
After configuring the firewall, try connecting again.
3. Check User Permissions
Remote Desktop requires that the user account has permission to connect to the target machine. Here’s how to check:
- Open System Properties:
- Press Win + R, and type sysdm.cpl, & press Enter.
- Go to the Remote tab.
- Select Remote Desktop Users:
- Press on Select Users… under the RDP section.
- Add the username or group that needs access by clicking Add and typing the name of the user account.
- Administrator Accounts:
- By default, administrators on the destination machine have remote access rights. Ensure that the account you’re using has administrative privileges or has been added to the list of authorized users.
- Open System Properties:
4. Verify Required Services Are Running
Remote Desktop relies on specific Windows services to function. Make sure the following services are running:
- Remote Desktop Services:
- Press Win + R, & write services.msc, & press Enter.
- Locate Remote Desktop Services in the list.
- Right-click and select Start if the service is not running.
- Check Dependencies:
- Double-click Remote Desktop Services to open its properties.
- Go to the Dependencies tab and ensure that all dependent services are running.
- Restart Services:
- If the services are already running, restart them by right-clicking and selecting Restart.
- Remote Desktop Services:
5. Resolve Network-Level Authentication Issues
Network-Level Authentication (NLA) adds an extra layer of security to Remote Desktop but can cause connection issues if not configured correctly.
- Disable NLA Temporarily:
- Open System Properties (via sysdm.cpl).
- Under the Remote tab, uncheck Permit connections from computers running Remote Desktop with Network Level Authentication.
- Click Apply and test the connection.
- Enable NLA After Configuration:
- Once the issue is resolved, re-enable NLA for security purposes.
- Disable NLA Temporarily:
6. Troubleshoot Common Errors
If the above steps don’t resolve the issue, here are additional troubleshooting tips:
- Test Connectivity:
- Use the ping command to test the network connection to the target machine. Open Command Prompt and type:
ping <target_machine_IP> - Ensure the target machine is reachable.
- Use the ping command to test the network connection to the target machine. Open Command Prompt and type:
- Check Group Policy Settings:
- Open the Group Policy Editor (gpedit.msc) & navigate to Desktop Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host.
- Ensure that the policies for allowing Remote Desktop connections are enabled.
- Update Windows:
- Ensure both the client and server machines have the latest Windows updates installed. Sometimes, outdated software can cause connectivity issues.
- Test Connectivity:
7. Alternative Tools for Remote Access
If the Remote Desktop is not working, consider using alternative tools to access your server or machine remotely:
- Third-Party Software:
- Tools like TeamViewer, AnyDesk, or Chrome Remote Desktop offer reliable remote access options.
- Enable Windows Remote Assistance:
- Unlike Remote Desktop, Windows Remote Assistance allows you to share a session with another user and may bypass certain restrictions.
- Third-Party Software:
Conclusion
The “Remote access to the server is not enabled” error in Windows 10 can stem from a variety of issues, including disabled Remote Desktop, firewall restrictions, permission problems, or misconfigured services. By following the step-by-step guide outlined in this blog, you should be able to diagnose and resolve the issue efficiently.
If you’re still facing challenges, consider consulting your IT administrator or leveraging third-party remote access tools as a temporary workaround. Ensuring your Windows 10 setup is configured correctly will save time and boost productivity when accessing remote servers.



