Rıza KorkusuzTechnical Support

Remote Desktop Can't Connect to the Remote Computer: A Service Desk Guide for Windows 11

How I would work a Remote Desktop cannot connect ticket: reading the exact message, checking the target PC and Windows edition, Test-NetConnection on port 3389, DNS and firewall checks, qwinsta and the Remote Desktop services, Remote Desktop Users permissions, and when to escalate

8 min readUpdated 2026-11-12Original notesStudy notes

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]:

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

  1. 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].
  2. 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.
  3. What are they typing in the Computer box? The computer name, an IP address, or an old name from a sticky note.
  4. 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.
  5. 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:

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

Then, following the same article [1]:

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]:

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

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 3389 returned TcpTestSucceeded : True after 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

  1. 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
  2. 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
  3. 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.