A user calls from home or from another building: "Remote Desktop says it can't connect to my office PC." The message lists three possible reasons, remote access isn't enabled, the computer is off, or it isn't on the network, and the user has no idea which one applies. In my Tier 1-2 work at a university faculty and in Ministry of National Education technology workshops, remote access requests came up often enough that I learned to work them in a fixed order instead of guessing.
These are my study notes on how I'd work this ticket for a Windows 11 Pro or Enterprise PC, written as a guide and "what I learned," with each step checked against Microsoft's documentation. Group Policy design and firewall rules in a large domain are study topics for me, so I note where the service desk should hand off to the systems or network team.
What the user is actually seeing
Microsoft's troubleshooting article lists two common messages [1]:
- "Remote Desktop can't connect to the remote computer for one of these reasons: 1) Remote access to the server is not enabled 2) The remote computer is turned off 3) The remote computer is not available on the network."
- "This computer can't connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator."
A different family of messages means the connection reached the PC but the account was refused: "Access is denied" or "The connection was denied because the user account is not authorized for remote login" [3]. I write down the exact text, because it tells me which half of the problem I'm in: reaching the PC, or being allowed to sign in to it.
First questions
- One user or many? Microsoft's own checklist starts here: one user points to that user's account or permissions, many users point to the PC, a policy, or the network [3].
- Where is the user? On the office network, or at home? From outside the network, Remote Desktop needs a VPN or another approved path [2], so "VPN connected?" is the first question for a home user.
- What are they typing in the Computer box? The computer name, an IP address, or an old name from a sticky note.
- Did it ever work? A brand-new request, a PC that was just replaced or reimaged, or something that worked yesterday are three different tickets.
- Exact message and time, for the ticket.
Check the target PC first
Microsoft's first step is simply to check that the machine is running [1]. In practice that means:
- Is it powered on and awake? Someone in the office may need to check it, or the PC may have been shut down, gone to sleep, or been moved.
- Is it a Windows edition that can host Remote Desktop? Pro, Enterprise, Education, and Server editions can accept incoming Remote Desktop connections; Windows Home can connect to other PCs but can't be a host [2]. A personal Home laptop will never work as a target.
- Is Remote Desktop enabled? On Windows 11 it's in Settings > System > Remote Desktop, and changing it requires admin rights [2]. On a managed PC this is usually set by policy, so if it's off, I'd escalate rather than change it on my own.
Reaching the PC: name, port, and firewall
If the user is on the right network and the PC is on, the next question is whether the PC answers on the Remote Desktop port. Microsoft's article uses this test from a machine on the same network [1]:
Test-NetConnection -ComputerName LT-0518 -Port 3389 -InformationLevel Detailed
TcpTestSucceeded : Truemeans there's no connectivity problem on that port, so the issue is on the PC's configuration side [1].TcpTestSucceeded : Falsemeans something on the path is blocking or not listening [1].
Then, following the same article [1]:
- Try the IP address instead of the name. If the IP works and the name doesn't, it's a name resolution (DNS) problem, which goes in the ticket for the systems team.
- Is the port different? The default is 3389. If a PC was configured with a different port, the user has to connect as
name:portorIP:port[1]. - Firewall rules. The inbound rules Remote Desktop - User Mode (TCP-In) and (UDP-In) need to be enabled for the network profiles in use [1]. Microsoft's article also shows turning the firewall off entirely or uninstalling antivirus to rule them out [1]. On a managed company PC I would not do either myself; I'd note the test result and hand it to the network or security team.
On the PC itself: is it listening?
If someone with admin rights can sign in at the PC (or a technician can reach it another way), Microsoft's checks are [1]:
qwinsta
A line rdp-tcp ... Listen means the Remote Desktop listener is running [1]. If it's missing, the article points to registry values (fDenyTSConnections and fEnableWinStation) and to two services that must be running: Remote Desktop Services (TermService) and Remote Desktop Services UserMode Port Redirector (UmRdpService) [1]. It also notes that policy settings override local ones [1], which on a domain PC means the real fix is usually in Group Policy, not in the registry of one machine. That's an escalation for me, with the qwinsta output attached.
If the listener runs and the port test succeeds but connections still fail, Microsoft checks whether another process is holding port 3389, by comparing the PID of TermService with the process listening on the port [1]:
tasklist /svc | findstr TermService
netstat -anob | findstr 3389
That's a useful piece of evidence to collect, but the fix (stopping another service, re-creating the Remote Desktop certificate) belongs to the systems team [1].
"Access is denied" or "not authorized for remote login"
When the connection reaches the PC but the account is refused, it's a permissions question, not a network one [3]:
- Is the user allowed to connect? When Remote Desktop is enabled, members of the Administrators group and the users you add can connect [2]. For everyone else, Microsoft points to the Remote Desktop Users group, either in Active Directory (Builtin > Remote Desktop Users) or locally on the PC (
lusrmgr.msc> Groups) [3]. - Does the user have the "Allow log on through Remote Desktop Services" right? This is set under Local Policies > User Rights Assignment, and Group Policy settings override the local security policy [3].
- Can the user sign in to that PC locally? If not, it's a broader account problem, not a Remote Desktop one [3].
- Is the target a domain controller? Only Domain Admins can use Remote Desktop to connect to a domain controller [3], so a regular user being refused there is expected.
As a service desk technician I can check group membership with read access, but adding someone to a group that grants remote access is a change that needs the manager's approval and is done by whoever owns access management.
A note on security
Microsoft's own guidance is clear that enabling Remote Desktop opens a port on the PC, should only be done on trusted networks, and that every account with remote access needs a strong password [2]. Network Level Authentication (NLA), which makes users authenticate before a session is created, is recommended and should stay on [2]. So "just turn off NLA" or "just open the port to the internet" are not fixes I'd suggest.
When I'd escalate
- The PC can't be reached by IP or the port test fails on the office network: network team, with the
Test-NetConnectionoutput. - Works by IP address but not by name: systems team, as a DNS issue.
- Listener not running, services won't start, or Remote Desktop is turned off by policy: systems team, with the
qwinstaoutput. - "Not authorized for remote login" and the user should have access: access management, with the manager's approval.
What to put in the ticket
- User: J. Doe, connecting from home over VPN to office PC LT-0518 (Windows 11 Pro).
- Issue: "Remote Desktop can't connect to the remote computer" since this morning. Only this user affected.
- Checks: VPN connected. PC was asleep, a coworker woke it.
Test-NetConnection LT-0518 -Port 3389returnedTcpTestSucceeded : Trueafter that.- Action: User connected successfully. Asked the user to check the sleep setting with the PC owner or IT before leaving it on overnight.
- Follow-up: None. If it recurs, check the PC's power settings policy with the systems team.
What I learned
"Remote Desktop can't connect" is two different problems hiding behind one dialog. Either the client can't reach the PC (off, asleep, wrong name, wrong network, port blocked), or it reaches the PC but the account isn't allowed in. The order that saves time is: read the exact message, confirm the PC is on and is a Pro or Enterprise edition with Remote Desktop enabled, run Test-NetConnection on port 3389, try the IP address, and only then look at the listener, services, and group membership. And the steps that change firewall rules, the registry, or who has remote access belong in an escalation, not in a quick fix.
Sources
- Microsoft Learn, Remote Desktop can't connect to the remote computer: https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/remote-desktop-cannot-connect-remote-computer
- Microsoft Learn, Enable Remote Desktop on your PC: https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-allow-access
- Microsoft Learn, Troubleshooting access denied and user not authorized issues in RDS: https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/troubleshooting-access-denied-and-user-not-authorized-rds-issues
I'm Rıza Korkusuz, an IT support professional in San Diego. I write these notes to organize what I'm learning about desktop and service desk work. More at rizakorkusuz.com/it-support and github.com/rizakorkusuz.