Remote Desktop Error 0x104: How to Fix It

Remote Desktop error 0x104 usually means the client cannot find or reach the computer you are trying to connect to. These steps help Windows and macOS users check the computer name, network, Remote Desktop settings, and firewall without weakening security unnecessarily. You will need access to the remote PC or help from someone who does.

What You’ll Need

• The name or IP address of the remote Windows PC, and the account you are allowed to use.
• Access to that PC to check its settings, or someone at the PC who can follow the steps.
• Both devices connected to the same local network, or an organization-approved VPN or Remote Desktop gateway for access over the internet.
• Administrator permission on the remote PC for changes to Remote Desktop or firewall settings.

Step-by-Step

1. Check that the remote PC is available. Make sure it is powered on, awake, and connected to the network. Remote Desktop cannot connect to a computer that is shut down or asleep. If you can, sign in locally and confirm it has working internet or local-network access.
2. Confirm the PC supports incoming Remote Desktop. On the remote PC, open Settings > System > About and check its Windows edition. Windows Pro, Enterprise, and Education editions can host incoming Remote Desktop connections; Windows Home cannot. If it is Home, use an approved remote-access option that supports the edition rather than trying to enable unsupported host features.
3. Turn on Remote Desktop. On a supported edition, go to Settings > System > Remote Desktop and switch on Remote Desktop. Confirm the prompt. Keep Network Level Authentication enabled unless your organization’s administrator directs otherwise. If the setting is managed or unavailable, contact the administrator rather than changing policy or registry settings.
4. Use the correct computer name. On the remote PC, open Settings > System > About and note the Device name. Enter that name in the Remote Desktop client. Names may not resolve across different networks, so try the PC’s local IP address if both devices are on the same network. On the remote PC, find its IPv4 address in Settings > Network & internet, under the active Wi-Fi or Ethernet connection. A local address usually works only on that network.
5. Check the connection between devices. First test whether other websites or network resources work from the device running Remote Desktop. If both PCs are at home or in one office, connect them to the same trusted network and retry. If connecting from elsewhere, connect to your organization’s approved VPN first, or use its configured Remote Desktop gateway. Do not expose Remote Desktop directly to the public internet by opening router ports as a quick fix.
6. Allow Remote Desktop through the Windows firewall. On the remote PC, open Windows Security > Firewall & network protection > Allow an app through firewall. Select Change settings if needed, then confirm that Remote Desktop is allowed on the appropriate network profile. Use the profile that matches the current trusted network; do not turn off the firewall. If a third-party firewall is installed, ask its administrator to check its Remote Desktop rules.
7. Retry with a fresh connection entry. In the Remote Desktop client, remove or edit any saved entry with an old computer name or address. Add the correct name or address again, then enter the authorized account when prompted. For a work or school account, use the sign-in format your organization requires. A typo, stale saved address, or incorrect account can make a working PC seem unreachable.
8. Restart and update both devices. Save work, then restart the remote PC if you can do so safely. Restart the client device as well, install available Windows updates, and update or reinstall the Remote Desktop client through its usual app update method. Retry after both devices reconnect to the network.

Common Mistakes

• Using a Windows Home PC as the host: Home can connect out to another PC, but it does not provide Microsoft’s built-in incoming Remote Desktop host.
• Entering the wrong name or an out-of-date address: A device name may resolve on a local network but not through a VPN or across separate networks. An IP address can also change.
• Assuming the error is a password problem: Error 0x104 commonly points to a reachability or name-resolution issue. Check network access and the destination before repeatedly changing credentials.
• Disabling the firewall or security requirements: This can expose the PC without fixing the underlying issue. Keep the firewall on and allow only the needed, appropriate rule.
• Trying to connect over the internet without an approved route: A local computer name or private IP usually cannot be reached from outside the network unless an approved VPN or gateway provides access.

Tips

• Write down the exact device name and current address while physically at the remote PC; this avoids guessing.
• If a connection worked before, note what changed: a router, VPN, network, PC name, Windows update, firewall, or saved connection entry may be responsible.
• Test one change at a time and retry. This makes it easier to identify the cause and undo an unnecessary change.
• For a managed work computer, use the organization’s instructions for VPN, gateway, account format, and firewall policy. Those settings may be controlled centrally.

Troubleshooting

The PC name fails, but the IP address works: This points to name resolution. Use the correct address temporarily on the same network, then ask the network administrator to check name resolution or the VPN’s DNS settings. Remember that a changing IP address may stop working later.

Neither name nor address works on the same network: Verify the host is awake, Remote Desktop is enabled, and the firewall rule applies to the active network profile. Confirm both devices are connected to the intended network. If you are comfortable doing so, ask an administrator to verify that the Remote Desktop service is running; avoid changing services or firewall rules without permission.

It works on the local network but not remotely: The host is likely reachable locally, but the remote route is missing or incorrect. Connect to the approved VPN or use the configured gateway, and confirm the organization permits access from your current network. Do not use router port forwarding as a substitute for an approved secure setup.

The setting is enabled but the client still reports 0x104: Recheck the destination spelling, saved connection details, VPN status, and firewall profile. Restart the host if practical. If this is a company device, send IT the exact error, client device type, destination name, whether local or VPN access works, and when the issue began.

You cannot access the remote PC to check it: Ask someone at its location to confirm it is powered on and connected, or contact the administrator through another channel. A client-side setting cannot make an offline or unreachable host accept connections.

Frequently Asked Questions

What does Remote Desktop error 0x104 mean?
It generally indicates that the Remote Desktop client could not locate or reach the target computer. Incorrect names, network problems, an unavailable host, or blocked connections are common causes.

Can I connect to a Windows Home PC using Remote Desktop?
You can use a Home PC as a client to connect to another supported host, but Windows Home does not host incoming connections through Microsoft’s built-in Remote Desktop feature. Use an approved alternative if the Home PC is the destination.

Should I enter the computer name or its IP address?
Try the device name first when name resolution is available. A current local IP address can help on the same network, but private addresses generally do not work from outside it without a VPN or gateway.

Does error 0x104 mean my password is wrong?
Not necessarily. It more often indicates that the host cannot be reached or identified. Once it is reachable, you may still need to enter the correct account credentials.

Is it safe to open Remote Desktop to the internet?
Do not expose it directly as a troubleshooting shortcut. Use an organization-approved VPN or Remote Desktop gateway, keep security protections enabled, and ask an administrator to configure remote access.

Why did Remote Desktop stop working after it worked before?
The PC may be asleep or offline, its address or name may have changed, or a network, VPN, firewall, or policy change may have interrupted access. Check those items in order and involve IT for managed devices.

Related

• Keep Sensitive Banking Data Out of AI Agent Prompts
• Block or Allow AI Apps on Managed Android Devices
• How to Use ChatGPT with Siri on iPhone