10 reasons why Remote login doesn’t work in Windows 10 (and how to fix it)

Le PC n’accepte pas les connexions distantes? La cause commune est souvent une fonction désactivée ou un blocage réseau; cet article vous guide pas à pas pour résoudre le problème Remote login doesn’t work in Windows 10. Vous apprendrez pourquoi cela se produit (paramètres, pare-feu, édition Windows, services, permissions, NLA, NAT/routeur, etc.) et recevrez des corrections pratiques, commandes et astuces pour retrouver l’accès à distance.

Key Takeaway

The most common fix is to enable Remote Desktop on the target PC, ensure the Remote Desktop service is running, allow TCP port 3389 through the Windows Firewall (or a third-party firewall), and confirm the user has permission; once those basics are correct, troubleshoot NLA, NAT/port forwarding, and third-party security software.

Quick Fix Guide

Quick Fix Guide

Reason for the Problem	Quick Solution
Remote Desktop not enabled	Enable Remote Desktop in Settings > System > Remote Desktop or Control Panel > System > Remote settings.
Windows 10 Home edition	Use Quick Assist, upgrade to Pro, or install a supported remote tool (TeamViewer, AnyDesk).
Windows Firewall blocking RDP	Allow RDP via Windows Defender Firewall or run netsh advfirewall firewall add rule name=”RDP” dir=in action=allow protocol=TCP localport=3389.
Network profile set to Public	Change to Private in Settings > Network & Internet > Status > Change connection properties.
Remote Desktop Services stopped	Start Remote Desktop Services (TermService) in services.msc or run sc start termservice.
User not allowed or missing rights	Add user to Remote Desktop Users group and check Local Security Policy > User Rights Assignment.
Network Level Authentication (NLA) issues	Temporarily uncheck NLA in System Properties > Remote or set registry UserAuthentication to 0.
Router/NAT/Port forwarding issues	Forward TCP port 3389 to the PC’s local IP (or use VPN) and check public IP.
Third‑party security/antivirus blocking	Temporarily disable or configure third‑party firewall to allow RDP.
RDP listening port changed or port conflict	Verify RDP port in registry HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber and test with netstat -an.

Detailed Fixes for “tu mets ici le problème du 10 reasons why Remote login doesn’t work in Windows 10 (and how to fix it)”

1) Remote Desktop not enabled

Why it causes the problem:

• If Remote Desktop is off, Windows will refuse all RDP connections.

Step-by-step solution:

1. Open Settings > System > Remote Desktop and toggle Enable Remote Desktop on. Confirm the PC name shown for connecting.
2. Or open Control Panel > System and Security > System > Remote settings and under Remote Desktop choose Allow remote connections to this computer.
3. Ensure the checkbox Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended) is set according to your environment (see NLA section).
   Notes:

• Enabling shows the computer name and suggests adding users.
• After enabling, test local RDP connection from another device on the same network.

2) Using Windows 10 Home edition (no RDP host)

Why it causes the problem:

• Windows 10 Home cannot act as an RDP host; RDP server is only in Pro/Enterprise/Education editions.

Step-by-step solution:

1. Confirm your edition: Settings > System > About and check Edition.
2. If Home, use one of:
   • Use Quick Assist (built into Windows 10): open the Start menu and type Quick Assist to share a session.
   • Use third-party remote tools like TeamViewer, AnyDesk, Chrome Remote Desktop.
   • Upgrade to Windows 10 Pro via Settings > Update & Security > Activation > Change product key and enter a Pro key.
     Notes:

• Avoid unsupported RDP “patches” that enable RDP on Home — they can be unstable or insecure.

3) Windows Firewall blocking RDP

Why it causes the problem:

• Windows Defender Firewall blocks inbound TCP port 3389 by default, preventing connections.

Step-by-step solution:

1. Open Windows Security > Firewall & network protection > Allow an app through firewall and ensure Remote Desktop is allowed on your network profile.
2. Or open an elevated PowerShell or Command Prompt and run:
   • netsh advfirewall firewall add rule name=”RDP” dir=in action=allow protocol=TCP localport=3389
3. Verify rule: netsh advfirewall firewall show rule name=all or check Windows Defender Firewall with Advanced Security.
   Notes:

• If using custom ports, open that port instead of 3389.
• For domain environments, confirm Group Policy isn’t overriding rules.

4) Network profile set to Public

Why it causes the problem:

• The Windows Firewall treats Public networks as restrictive; Remote Desktop often only allowed on Private.

Step-by-step solution:

1. Open Settings > Network & Internet > Status > Change connection properties.
2. Set Network profile to Private for the network you’re on.
3. Re-run firewall checks to confirm Remote Desktop allowed on Private profile.
   Notes:

• Change back to Public if you’re using an untrusted network after troubleshooting.

5) Remote Desktop Services stopped or disabled

Why it causes the problem:

• The RDP host service (TermService) must run for connections.

Step-by-step solution:

1. Press Win + R, type services.msc and press Enter.
2. Find Remote Desktop Services (service name TermService), ensure Startup Type is Automatic and click Start if stopped.
3. From an elevated command prompt you can run:
   • sc query termservice
   • sc start termservice
     Notes:

• If the service fails to start, check Event Viewer (Event Viewer > Windows Logs > System) for errors.

6) User not allowed or lacking permissions

Why it causes the problem:

• Only administrators and users in Remote Desktop Users can sign in; blank passwords are prohibited for RDP.

Step-by-step solution:

1. To add a user: open System Properties > Remote > Select Users… and click Add, then enter the username.
2. Or add via Computer Management > Local Users and Groups > Groups > Remote Desktop Users, then Add your user.
3. Check user password: ensure account has a non-empty password.
4. Check local policy: open gpedit.msc > Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment > Allow log on through Remote Desktop Services and ensure the group is present.
   Notes:

• Domain accounts must be granted rights by domain policy if applicable.

7) Network Level Authentication (NLA) problems

Why it causes the problem:

• NLA requires authentication before a remote session is established; incompatible clients or credential issues will fail connection.

Step-by-step solution:

1. Temporarily disable NLA: Control Panel > System > Remote settings and uncheck Allow connections only from computers running Remote Desktop with Network Level Authentication.
2. If you can now connect, update the client or server credentials/CredSSP fixes.
3. To change via registry (advanced): open regedit, go to HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp, change UserAuthentication DWORD to 0 to disable; set to 1 to enable.
   Notes:

• Disabling NLA reduces security; re-enable after resolving client compatibility.
• Recent Windows updates sometimes break CredSSP; installing hotfixes or updating both client and server helps.

8) Router/NAT and port forwarding issues

Why it causes the problem:

• For connections across the internet, the router must forward external port 3389 to the PC’s local IP; without forwarding connection won’t reach the PC.

Step-by-step solution:

1. Find local IP: open Command Prompt and run ipconfig; note the IPv4 Address.
2. Log into your router’s admin page (common IPs 192.168.1.1 or 192.168.0.1), find Port Forwarding or Virtual Server, and create a rule forwarding TCP 3389 to the PC’s local IP.
3. Check your public IP at whatismyip.com and test from outside using mstsc /v:your.public.ip.
4. For security, consider using a VPN instead of exposing 3389 publicly, or change external port and forward to internal 3389.
   Notes:

• Configure the PC to have a static local IP or DHCP reservation to maintain forwarding.
• Some ISPs block port 3389; test with an alternate external port.

9) Third‑party security or antivirus blocking RDP

Why it causes the problem:

• AV suites and third-party firewalls can block RDP traffic even if Windows Firewall allows it.

Step-by-step solution:

1. Temporarily disable third‑party firewall/antivirus and test the connection.
2. If connection works, add an exception in the security app for inbound TCP 3389 or the mstsc.exe application.
3. Check vendor documentation for adding exceptions or configuring network profiles.
   Notes:

• Always re-enable protection after testing and use targeted exceptions rather than full disabling.

10) RDP listening port changed or port conflict

Why it causes the problem:

• If RDP is configured to a non-standard port or another application is using 3389, clients connecting to default port will fail.

Step-by-step solution:

1. Check listening port: open elevated Command Prompt and run netstat -an | find “LISTEN” | find “:3389”.
2. Check registry for port: open regedit and go to HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber; value is decimal port.
3. If changed, either set clients to connect using hostname:port or revert registry to 3389 and reboot.
4. If port conflict exists, identify process with netstat -abn and resolve the conflicting application.
   Notes:

• Changing RDP port requires firewall rule updates and potential router forwarding updates.

---

Preventive Measures and Advanced Diagnostics

• Regularly update Windows and clients to avoid CredSSP/NLA mismatches.
• Use a fixed IP or DHCP reservation for remote hosts to avoid broken port forwarding.
• Prefer VPN or SSH tunneling to expose RDP only over a secure channel, not directly on the internet.
• Use Event Viewer ( Event Viewer > Windows Logs > Security/System/Application ) to check failed logon events and service errors (look for Event IDs 4625, 1026, or TermService errors).
• For advanced diagnostics: use PortQry or telnet your.ip.address 3389 to test reachability, and sc query termservice for service status.

FAQ

Can I use Remote Desktop over the internet safely?

Yes — but do not expose RDP directly to the internet unless you use strong passwords, changed ports, and ideally two-factor authentication; the safest option is to place the host behind a VPN and connect to it through the VPN.

Why do I get “Your credentials did not work”?

This usually means incorrect username/password, account is disabled, user is not allowed to log on via RDP, or NLA is preventing authentication. Verify the account password, check user permissions, and try connecting from a client that supports NLA.

How do I check whether the RDP port is reachable from another network?

From a remote host, use telnet public.ip 3389 (or Test-NetConnection -ComputerName public.ip -Port 3389 in PowerShell). If the port is closed or filtered, the connection will fail.

Is Remote Assistance different from Remote Desktop?

Yes. Remote Assistance is designed for interactive help and allows the local user to see/control the desktop with permission; Remote Desktop creates a separate session and logs the local user out (unless using the same account in Windows 10 Pro with single session).

What if I can RDP within LAN but not from outside?

Check router port forwarding, ISP blocking, and ensure you’re using the correct public IP; also verify that local firewall and third-party firewalls allow the connection from the internet.

Conclusion

Most remote login failures stem from a disabled host, firewall/router blocking, incorrect permissions, or NLA/service issues; following the checklist above will resolve the majority of cases. Use the step-by-step fixes to address the specific cause and restore remote access when Remote login doesn’t work in Windows 10.