By Annie / Last Updated December 9, 2021

Can ping but cannot remote desktop

“I failed to connect to my friend’s Windows 10 laptop. I considered that it was caused by network failure. However, I can ping his computer. Why I can ping but cannot RDP to Windows 10? Is there any idea?”

Why can ping but cannot connect using RDP?

You can ping the remote PC and it means that the network is normal. And Remote Desktop not working can be caused by these events.

  • Remote Desktop is disabled or sets up a specific user.
  • Remote Desktop is blocked by Windows Defender Firewall.
  • DNS issues
  • Remote Desktop Services issues.

7 solutions to fix ping working but Remote Desktop not working

After confirming that the network is well by ping, have a look at the following solutions to fix RDP not connecting.

Solution 1. Make sure Remote Desktop is enabled on the remote computer

Despite it sounds amazing, there are some users who haven't empowered Remote Desktop on the remote computer. Now, follow the means to check if RDP is enabled.

Step 1. On the remote computer (the PC that you need to access remotely), right-click “This PC” on Windows 10/11 ("Computer " on Windows 8, “My Computer on Windows 7”) and choose “Properties”.

Properties

Step 2. In the left sidebar, click “Remote Desktop” and you can check whether “Enable Remote Desktop” is turned on. If not, turn it on.

Enable Remote Desktop

Solution 2. Allow Remote Desktop through Windows Defender Firewall

If you have enabled Remote Desktop to pass through firewall, you can encounter Remote Desktop not working even ping working. Then, you can change Firewall settings to allow RDP.

Step 1. Type “allow an app through windows firewall and click "Open". 

Firewall

Step 2. In the pop-up window, click "Change settings", locate “Remote Desktop” and allow it on Private and Public networks.

Allow Remote Desktop through Firewall

Solution 3. Check 3389 port and change port

Windows Remote Desktop uses 3389 port under different networks. If the port is used by another app, port conflict will occur and RDP connection will be affected. If so, you need to change port.

Check 3389 port

Step 1. Input “cmd” on the search box, right-click “Command Prompt” and choose “Run as administrator”.

Step 2. Run the command:

netstat -an | find "3389"

Find 3889

If you see TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING, it means that 3389 port is in normal status. If not, it means that 3389 port is blocked and you can change port to settle out RDP not connecting issue.

Change port

Step 1. Press Windows + X and choose Windows PowerShell (Admin).

Step 2. Run the command:

netstat -a -o

Find PID

Note: The “netstat -a -o” command can list all IP address and ports. Find out Remote Desktop port (3389) and its PID. If you see the same PID of another port, it means that RDP port will conflict with another port.

Find App PID

Step 3. Run the command:

tasklist /svc

Note: The “tasklist /svc” command can help you to find out the corresponding apps of the different PIDs.

Step 4. Press Windows + R to open Run dialogue; then input “regedit” and click Enter to open Registry Editor.

Step 5. Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp and find out "PortNumber". 

Step 6. Find out “PortNumber”, double click it, click “Decimal” option, and set a new data (The new data is the new port). Then, click “OK” to save the change and reboot the computer.

Change Value Data of Port Number

Step 7. Then, repeat the steps above to change the port to 3389 and reboot the computer.

Solution 4. Flush DNS and re-registry DNS

Based on some users’ feedback, it’s a useful way to flush and re-register DNS for “able to ping but unable to RDP”.

Step 1. Run Command Prompt as administrator.

Step 2. In the Command Prompt window, input “ipconfig/flushdns” and click “Enter” to flush DNS.

Step 3. Input “ipconfig/registerdns” and click “Enter” to registry DNS.

Flush and Re-registry DNS

Solution 5. Remove wrong IP address and names from the hosts file

The IP address and name are saved in the hosts file. If they are wrong. You can stick on ping work but Remote Desktop not working. Thus, you can check whether the IP address and the user name are correct and then decide whether to modify it.

Step 1. Double click “This PC”, go to C:\Windows\System32\drivers\etc.

Step 2. Locate the hosts file, open it in Notepad and check whether the IP address and the name is correct. If not, change them to the right ones and press “Ctrl” + “S” to save the change. Then, exit from the window.

Host Files

Solution 6. Restart Remote Desktop Configuration

In some cases, Remote Desktop Configuration Services may have an abnormal state, causing the able to ping but unable to connect. At this point, you need to restart the Remote Desktop Configuration Service.

Step 1. Open Run dialogue, input “services.msc” and click the “Enter” key.

Step 2. Locate “Remote Desktop Configuration”, right-click it, and choose “Restart”.

Remote Desktop Configuration

Step 3. Locate “Remote Desktop Services”, right-click it, and choose “Restart”.

Solution 7. Reboot Windows Explorer

You can also try to reboot Windows Explorer to solve the “Can ping but cannot remote desktop” issue.

Step 1. Press “Ctrl+Shift+ESC” at the same time to open Task Manager.

Step 2. Find out “Windows Explorer”, right-click it, and choose “Restart”.

Restart Explorer

restart-explorer

A free & stable remote access solution – AnyViewer

Do you have to try the ways one by one to fix Remote Desktop not connecting while you can ping? Obviously, you can skip the solutions and just switch to a stable & easy-to-use remote access utility, AnyViewer, whether your computer and the remote computer are running Windows 11/10/8.1/8/7 or Windows Server 2022/2019/2012 R2. Compared with Windows Remote Desktop, AnyViewer takes advantage of the following aspects.

✔ During a remote session, Windows Remote Desktop doesn’t’ allow you to adjust the resolution of the remote screen while AnyViewer supports changing resolution and adjusting image quality.
✔ Remote Desktop does not have a built-in Chat function and AnyViewer has that one, allowing sending messages to each other between the two remotely connected devices.
✔ During a remote session, Remote Desktop cannot achieve Ctrl+Alt+Delete, command prompt, task manager, and other functions only with one click while AnyViewer can.

Now, let’s see how to use AnyViewer to connect to another computer remotely.

Preparation work:

  • The lock PC and remote PC are connected to the internet.
  • Download and install AnyViewer on the two computers.
Download Freeware Windows PCs & Servers
Secure Download

Step 1. On the remote PC, run AnyViewer, click “Settings” and enable “Set security code”. Then, type a valid security code and click “OK”. Now, the security code to access the remote computer has been set.

Set Security Code

Step 2. On the local PC, run AnyViewer, input the device ID of the remote computer, click “Connect”; then, choose “Input security code”, type the security code of the remote PC. Finally, click “OK” and you can connect to the remote computer immediately.

Input Security Code

Note: You can achieve unattended remote access via security code; if there is someone on the other end to accept a remote control, you can choose “Send a control request to your partner” and wait for he/she to accept the request.

Once the remote session is established, AnyViewer offers five items: Resolution, Image Quality, Message, and Zoom in/out, which enables you to adjust the screen resolution, change image quality & hide desktop wallpaper, open Task Manager, and zoom in or out the remote desktop window.

Wrap things up 

It’s rather frustrating if you find that you can ping but cannot remote desktop. If so, you can take on ore more of the seven solutions to repair RDP, which can be time-consuming. Or you can turn to a free & secure remote access software for Windows, AnyViewer, which offers you a better experience.