I need help enabling remote access on my Windows 10 PC so I can connect to it from another location. I recently tried to set up Remote Desktop, but I’m not sure which settings to turn on, and the connection is not working. I need access to files and apps on this computer while away from home, so I’m looking for the correct steps and any fixes for common setup issues.
I set this up on a Windows 10 box a while back, and the shortest path looked like this.
1. Check which Windows 10 edition you have
Hit Win + R, type winver, then press Enter.
If it says Windows 10 Pro, Enterprise, or Education, you’re fine. If it says Home, built-in Remote Desktop hosting is out. I learned this the annoying way on an old laptop.
2. Turn on Remote Desktop
Open:
Settings → System → Remote Desktop
Flip on Enable Remote Desktop. Windows will ask for confirmation. Accept it.
3. Copy the PC name
Stay on the same screen and note the PC name. You’ll need it later from the other machine. I usually paste it into Notepad so I don’t mistype it.
4. Set a password on your Windows account
No password, no RDP login. Empty-password accounts won’t work.
5. Check the firewall rule
Most of the time Windows adds this for you, but I still check:
Control Panel → Windows Defender Firewall → Allow an app or feature through Windows Defender Firewall
Find Remote Desktop and make sure it’s allowed on Private networks.
6. Get the local IP if both PCs are on the same network
Open Command Prompt and run:
ipconfig
Look for IPv4 Address. That’s the one you want for local access.
7. Connect from another Windows computer
On the second PC, press Win + S, search for Remote Desktop Connection, and open it.
In the connection box, enter either:
• the PC name
• or the local IP address
Then sign in with your normal Windows username and password.
8. If you need access from outside your house
This part gets less friendly.
You’ll need one of these:
• port forwarding on your router for TCP 3389
• or a VPN
I’d pick the VPN route. Exposing RDP straight to the internet is where people get into trouble fast if they skip hardening.
If you want the longer version with screenshots, use this guide:
5 Likes
If Remote Desktop is enabled and it still fails, I’d check the stuff people skip.
First, test from inside your home network before you try remote internet access. If LAN access fails, the problem is on the PC, not the router.
Second, make sure your Windows account is allowed for RDP. Open System Properties, Remote tab, then check Select Users. Your account should be listed if you do not use an admin account.
Third, confirm the PC stays awake. A sleeping PC will not answer RDP. Set Power Options so it does not sleep while plugged in. This gets missed a lot.
Fourth, if you are trying from outside your house, I disagree a bit with the old port forward habit. Direct 3389 exposure is where people get owned. Use Tailscale, ZeroTier, or your router’s VPN if it has one. Easier to manage, less janky.
Fifth, test whether port 3389 is listening on the host PC. In Command Prompt, run:
netstat -an | find ‘3389’
If you do not see LISTENING, RDP is not running right.
@mikeappsreviewer covered the main switchs. I’d add this too, if your PC is on Home edition, use Chrome Remote Desktop or RustDesk instead. For a lot of people, those work faster with less fiddling.
One extra thing neither @mikeappsreviewer nor @reveurdenuit really spelled out: if you’re trying to connect with a Microsoft account, the username can trip people up. For RDP, use either MicrosoftAccount\youremail@example.com or the actual local username on the PC. A lot of failed logins are just bad username format, not bad passwords.
Also check this:
services.msc→ make sure Remote Desktop Services is runninggpedit.msc→ Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Connections
Make sure Allow users to connect remotely isn’t disabled
I’ll mildly disagree with the “just use the PC name” advice because that only works cleanly if your network/DNS is behaving. If it keeps failing, use the IP first to rule out name resolution issues. Saves time.
And if you’re remote from another location, don’t forget your ISP might change your home IP unless you set up dynamic DNS or use a mesh VPN. People set up everything right, then wonder why it worked yesturday and not today.
If you want a quick sanity test, try:
- Ping the PC
- Try
mstsc /v:IPADDRESS - If login fails, verify the account name format
That usually narrows it down fast.
I mostly agree with @reveurdenuit, @caminantenocturno, and @mikeappsreviewer, but one thing I’d check that often gets buried is the network profile. If your Windows 10 PC is set to Public network, Remote Desktop can act flaky even when the main toggle is on. Switch it to Private under Settings > Network & Internet > Properties for your current connection.
Also, verify this registry value if the GUI setting looks enabled but RDP still refuses connections:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
fDenyTSConnections should be 0
I slightly disagree with relying on port tests alone. I’ve seen 3389 listening and RDP still fail because Network Level Authentication was the blocker. Try temporarily unchecking “Allow connections only from computers running Remote Desktop with Network Level Authentication” just as a test. If it works after that, the issue is on the client side, not the host.
Another overlooked bit: if you use security software beyond Defender, it may silently block RDP even when Windows Firewall allows it.
If you’re on Windows 10 Home, skip fighting built-in hosting and use something else. Pros of ': can be simpler, less network tinkering. Cons: depends on the tool, sometimes less native performance and more third-party trust involved.