I’m trying to enable Remote Desktop on my Windows 11 PC so I can access it from another computer, but I can’t get it working. I checked the settings and still can’t connect, so I’m not sure if I missed a permission, firewall option, or setup step. I need help figuring out how to allow Remote Desktop in Windows 11 and what to check next.
I got tripped up by the same thing, and the whole mess came down to one detail people skip in the first minute.
Step 1. Check which Windows 11 edition you have
This decides the rest.
If your PC runs Windows 11 Home, it will not accept incoming Remote Desktop connections. You can connect out from it, but you cannot use it as the host.
If you have Windows 11 Pro, Enterprise, or Education, hosting RDP is supported.
Step 2. Turn Remote Desktop on
Open:
Settings > System > Remote Desktop > Enable Remote Desktop
When I did this on a Pro machine, Windows handled the background stuff on its own, firewall rules, service start, all of it.
Step 3. Make sure the account is allowed
This part gets missed a lot. Enabling RDP does not mean every account gets access.
- Add the account to Remote Desktop Users
- Or sign in with an administrator account
Step 4. Connect from the other device
On the client PC, open mstsc, type the target computer name, then sign in.
Stuff people usually get stuck on
- Windows 11 Home. This is the big one. If you're on Home, stop there.
- Wrong username format. I had better luck using
PCNAME\usernamefor local accounts, or the full Microsoft account email if the machine uses one. - Port 3389 blocked. Sometimes the network or firewall is the part breaking it, not Windows itself.
If you want the longer version with screenshots, this write-up covers it well:
7 Likes
One thing I’d add to what @mikeappsreviewer said, check the network profile on the host PC. If Windows set your connection to Public, RDP often fails even when the toggle is on. Set it to Private under Settings, Network and Internet, then open Advanced sharing settings and make sure Network Discovery is on.
Also, verify the PC is not sleeping. A sleeping Windows 11 box will not answer RDP, and this trips up tons of people. Set power options so the machine stays awake while you test.
If you’re connecting across the internet, don’t start with port forwarding right away. Test on the same local network first using the host’s local IPv4 address from ipconfig. If local works and remote does not, your router or ISP is the issue, not Windows.
One spot where I disagree a bit with @mikeappsreviewer is firewall handling. Windows usually adds the rule, but I’ve seen it fail after updates or third party security installs. Open Windows Defender Firewall, Allow an app, and confirm Remote Desktop is checked for Private networks.
If mstsc gives a credential error, try the host’s IP instead of computer name. DNS is wierd sometimes.
If the toggle is already on and you still cannot connect, I’d check one thing neither @mikeappsreviewer nor @cacadordeestrelas really leaned on enough: whether Remote Desktop is actually listening on the host.
On the Windows 11 PC you want to connect to, open Command Prompt and run:
netstat -an | find '3389'
If you do not see the PC listening on 3389, then the problem is on the host itself, not the client. In that case also run:
services.msc
and make sure these are running:
- Remote Desktop Services
- Remote Desktop Services UserMode Port Redirector
Also check this local policy setting because it can silently block access even when the Settings toggle looks enabled:
secpol.msc > Local Policies > User Rights Assignment > Allow log on through Remote Desktop Services
Your account, or the Administrators group, needs to be there. If it is missing, RDP just kind of sits there being useless.
One place I sorta disagree with @mikeappsreviewer is the idea that turning it on in Settings always finishes the job. It should, sure. Windows also ‘should’ do lots of things. Sometimes it doesnt.
Another easy gotcha: if you use a Microsoft account on the host, try MicrosoftAccount\youremail@example.com as the username. Plain email works sometimes, sometimes not. Classic Windows behavior.
Last thing, if this is a work PC or one that ever had domain policies, run:
gpupdate /force
Then reboot and test again. Group Policy can overwrite the GUI setting and make you think you’re losing your mind.
I’d add one check that often explains the “everything looks enabled but it still won’t connect” problem: NLA and edition mismatch on the client side.
On the host, go to SystemPropertiesRemote.exe and temporarily untick “Allow connections only from computers running Remote Desktop with Network Level Authentication” just for testing. I know some people hate that suggestion, but it’s useful because older clients, saved bad creds, or certain VPN/RD Gateway setups choke on NLA before you even get a proper error. If it suddenly works, you found the bottleneck.
Also, don’t trust the computer name too much. I disagree a little with the “just use mstsc with the PC name” advice because Windows name resolution is flaky on mixed Wi-Fi/Ethernet or mesh setups. Test with:
hostnameon the hostipconfigto confirm the current IPv4ping <host-ip>from the client
If ping fails locally, RDP is not your first problem.
Another overlooked item: router AP/client isolation. Some home routers block devices on the same Wi-Fi from talking to each other. If both PCs are on the same network but one is on guest Wi-Fi, RDP may never work.
Briefly, @cacadordeestrelas is right about the Windows edition trap, @andarilhonoturno is right to check whether 3389 is actually listening, and @mikeappsreviewer is right that firewall/profile issues are common. I’d just put network isolation and NLA testing higher on the list than most people do.
As for ', pros: can improve readability in a guide context, easy to reference. Cons: here it’s basically not relevant unless you’re comparing remote-access tools, so I wouldn’t force it.