The Remote Desktop Error Code 0x104 on Windows 10 occurs when you try to give access to the system that is available on the same or on another network. But when it fails, you may see an error message that states –
We couldn’t connect to the remote PC because the PC can’t be found. Please provide the fully-qualified name or the IP address of the remote PC, and then try again. Error Code 0x104
This issue can be highly complicated. Some users who are trying to connect their remote servers also experienced the failure of internet connections. However, here are some easy methods that may help you to get rid of this mess.
Remote Desktop Error Code 0x104
To fix Remote Desktop Error Code 0x104 on your computer follow these suggestions:
- Turn on Network Discovery
- Clear Custom DNS Servers
- Allow Port 3389 in the Windows Firewall.
Let us see them in detail.
1] Turn on Network Discovery
Network discovery is a feature that allows your computer to identify additional devices available on the same network. This makes it easy to share files and printers between the networks you want. In order to set up the RDP connection, you must have to ensure whether this option is enabled or not. So, let’s see how to turn on Network Discovery:
Open the Control Panel and in the search box, type in Network and Internet. Press Enter and on the next page, select the Network and Sharing Center option.
From the left sidebar, select the Change advanced sharing settings link.
Expand the network profile that is currently being used to your network connection. After that, select the radio button next to Turn on network discovery.
Finally, hit Save changes button.
2] Allow Port 3389 in the Windows Firewall
TCP port 3389 is the default port that is used for the Windows Remote Desktop Protocol. This port is also used in the Windows Firewall to connect other devices available either on the same network or different networks. However, if the Windows Firewall blocks this, you won’t be able to give access to them.
To make a connection, you need to allow port 3389 in the Windows Firewall. Here is how to do it:
Open the Control Panel window, select the System item.
From the left pane of the next screen, select the Remote settings link. This will open the System Properties wizard where ensure that you’re on the Remote tab.
Under the Remote Desktop section, mark the checkbox next to Allow remote connections to this computer.
Click on the Apply > OK button to save the changes.
Now, again open the Control Panel window and select Windows Defender Firewall item.
From the left pane, select the Advanced settings link. On the next screen, select Inbound Rules.
Move to the right pane and then search for Remote Assistance (RA Server TCP-In) under the Name column.
Once you find it, make sure it is enabled.
Now find out Remote Desktop – User Mode (TCP-In) and Remote Desktop – User Mode (UDP-In).
Make sure both options are enabled and 3389 is the Local Port. In order to make the local port visible, drag the horizontal scroll bar towards the right end.
After that, try to set the connection again and check if the Error Code 0x104 is resolved now.
3] Clear Custom DNS Servers to fix Error Code 0x104
If enabling Network Discovery doesn’t fix the problem, you may try to resolve it by clearing the custom DNS server before setting up the remote connection. It is easily applicable to both the host and target systems. Let’s try to clear custom DNS servers. To do it –
Open WinX menu using Windows+X keyboard shortcut.
From the menu list, select Settings > Network & Internet.
Move to the right pane and click on Change adapter options.
On the Network Connections page, look for your adapter.
Once you find, right-click on it and select Properties option.
On the respective properties wizard, make sure you’re on the Networking tab.
Thereupon, mark the checkbox next to Internet Protocol Version 4 and then select the Properties button.
Also, make sure Obtain DNS server address automatically is selected.
Click on the OK button to save the changes and then try to connect it again.
Let us know if this guide helped you to solve the problem.
- Tags: Remote Desktop