Can Ping But Cannot Remote Desktop? Get Your Solutions!

Why can ping but cannot remote desktop?

If you can ping the remote IP address but can't RDP, it means that the RDP failure isn't related to the network. And take a look at other reasons that cause the problem "cannot connect to the remote computer using RDP":

• Remote Desktop isn't enabled on or seated up a specific user
• Remote Desktop is blocked by Windows Defender Firewall.
• DNS issues
• Remote Desktop Services issues.

What to do when you can ping but cannot remote desktop?

If you can ping but cannot remote desktop Windows 11/10/8.1/8/7 and Windows Server 2022/2019/2016/2012 R2,  you can take one or more solutions to make you can connect to the remote device again. Or you can turn to a reliable and fast third-party remote desktop software, AnyViewer. 

Solution 1. Enable Remote Desktop on the destination 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 Remote Desktop is enabled on the host computer.

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”.

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.

Solution 2. Allow Remote Desktop through Windows Defender Firewall

If you haven't enabled Remote Desktop to pass through firewall, you can encounter Remote Dekstop not working even ping works. Then, you can change Firewall settings to allow RDP.

Step 1.  In the search box, type “allow an app through windows firewall and click "Open". 

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

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 remote desktop will be affected. If so, you need to change port.

☞ How to 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"

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 "can ping but cannot RDP" issue. 

☞ How to change port

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

Step 2. Run the command:

▪ netstat -a -o

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.

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.

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 register DNS.

Solution 5. Remove the 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 be stuck on "can ping but cannot remote desktop" issue. At this point, you can check whether the IP address and the user name are correct and then decide whether to modify them.

Step 1. Double-click “This PC” and 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 are correct. If not, change them to the right ones and press “Ctrl” + “S” to save the change. Then, exit from the window.

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”.

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”.

Switch to a third-party remote desktop software [Free and Reliable]

 It's not so easy to locate the specific reason when you can ping but cannot remote desktop. Then,  why not employ a third-party remote access utility, AnyViewer to get a stable and high-quality remote connection? 

Let's have a look at the reasons why we pick up AnyViewer:

 High compatibility: AnyViewer can allow you to access Windows Home, Standard, Professional, and advanced editions while Remote Desktop is only supported by Professional and advanced versions of Windows.

 Rich features: AnyViewer supports you to chat in session, adjust resolution, change image quality, and so on, which are unavailable in Remote Desktop sessions.

 Easy setup: You are not required to make complicated settings like port forwarding when you access a computer from outside the network when you need to perform port forwarding or set up VPN using RDP to control a PC from a different network.

Preparation work:

• The lock PC and remote PC are connected to the internet.
• Download and install AnyViewer on the two computers. 

Step 1. Create an AnyViewer account, and sign in to the same account on both the source computer and the destination computer.  Once logged in, the computer will be assigned to the account automatically.

Step 2. On your local computer, go to "Device", locate the destination PC, and click it. Then, click "One-click control" and you can take full control of the computer right now.

Notices:

❤ If you want to control the remote computer with blacking its screen and disabling its keyboard & mouse, you can upgrade to Professional or Enterprise and check "Connect in privacy mode" and then click "One-click control".
❤ Apart from taking full control of another PC, other functions are offered, including viewing the screen only, locking the computer, etc.
❤ AnyViewer supports you to control your PC from mobile devices and you need to download its mobile app on App Store or Google Play.
❤ If there is someone on the other end to accept a remote control, you can  “Send a control request to your partner” and wait for he/she to accept the request.

Then, you can see the desktop and apps on the destination computer and take operations as if you were sitting in front of it without physical presence. 

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, AnyViewer, to access your computer without obstacles.