How to Fix Common Remote Desktop Connection Problems


When encountering remote desktop connection failures on a Windows remote server, there are various troubleshooting steps you can try on your local PC. By following the suggestions, you can often resolve common connection issues. However, it's important to recognize that there may be instances where the problem persists despite your best efforts. In such cases, reaching out to your hosting provider for assistance is recommended.

Fix Common Remote Desktop Connection Problems

1. Verify Login Credentials

When facing RDP connection failures, the first thing you need to do is to verify whether the credentials are correct or not.

When credentials are incorrect, you will get the following error message "The logon attempt failed". There are some causes behind this issue.

The logon attempt failed

Make sure username and password are copied right

One of the causes is that the username/IP/port, or the password, or all are wrong. You may be pretty postive that you have entered the right password as you only copy and paste it to the fields. However, it happens when you copy and paste a password into the password field, a white space is copied along with the password. This will cause logon errors. So please check if the username and password are correct and make sure that there is no blanks before your password.

The logon attempt failed

Check if it's due to the Windows security settings

Another cause is Windows security settings. Some users have reported that while Remote Desktop Protocol (RDP) functioned flawlessly on system versions like Windows 7, they encountered errors when using Windows 10 or after reinstalling their operating systems. This issue suggests that the problem could be attributed to the Windows security settings, specifically those designed to restrict non-administrative users from logging in. If you want to allow non-admin users to use RDP, you need to log in as admin and modify this policy first.

Make sure IP and port are correct

The default Remote Desktop Protocol (RDP) port number for Windows servers is 3389. The default port are frequently targeted by ransomware attacks. Therefore, it's considered good practice to not use the standard port and change to a custom one. After the port change, you need to specify the server using the IP with the port included at the end by a colon (IP:port), for example,

Log with IP and port

If you are still using the default port, it's highly recommended to change it to a non-standard port. Check the written guide on how you can change the RDP port. Refer to the following tutorial if you prefer a video guidance.

2. Check the Service Status

When your hosting service is suspended or canceled for some reason, you will not be able to connect to your server. Therefore, do make sure that your hosting service is active. At Database Mart, clients can log in to their billing account and check the service status.

Suspension/cancellation can result from an overdue on payment. Before your server is canceled, it's recommended to make payment immediately to get servers unsuspended. If a server is canceled, you may not be able to make payment and are at the risk of losing all data in the server.

Suspension/cancellation can also be caused by IP abuse, including phishing, spam, DDoS, malware, hacking, and other similar attacks. Hosting providers often strictly prohibite IP abuse, which is crucial for maintaining network stability, resource allocation fairness, security, privacy, compliance, reputation, and trust within the digital ecosystem. If it's for IP abuse, you should already receive an email regarding this matter.

Check service status

3. Verify that the Remote Server is Turned On

When the remote server is off, you definitely cannot connect to it.

You may come across an error message like below.

The logon attempt failed

You can see if the server is turned on through a control panel that is used to manage your server. Database Mart provide free control panels, such as SolidCP and IPMI. If you have a control panel, then you can refer to the following guidance to reboot the servers by yourself. Otherwise, you may have to contact the hosting provider to restart the server for you.

Reboot the VPS with SolidCP
Reboot the dedicated server with IPMI

4. Check if both IPs are blocked

When you are using a remote server that is not from your own country, then it could result in RDP failures if your IP address or the server IP address is blocked by national firewall rules set by either of the countries.

You can Check if the server IP is blocked from any countries by visiting this site Simply enter in an IP and see which countries are blocking it.Ideally, the “Loss %” column is showing 0% for each location and mostly solid green bars in the “Chart” column. China is usually the toughest firewall to get through.

Check if an IP is blocked

5. Test the Network

Check the network using Ping, Telnet, and Tracert command.

Ping server IP

The following screenshot shows that a ping result.

Ping server IP

If you get the result "Destination host unreachable" when you ping your server IP, it means the network configuration is incorrect. In this case, you can contact your hosting provider for help.

Ping server IP

If the ping request has timed out or worked, please continue using telnet command to test the RDP/SSH connection.

Telnet RDP port

Open a command prompt. Type in "telnet IP-ADDRESS PORT" and press enter. For example, you would type "telnet 3389." If it works, you will see the following output.

Telnet server IP-good output

If you get the "Connect failed" error like below, please contact your hosting provider for assistance.

Ping server IP

6. Internal error (Windows Server Only)

If you get the internal error, the quickest method to resolve this is to reboot the server. Please refer to the following guide to reboot your server.

Internal error

Wrap up

Troubleshooting common remote desktop connection issues from your local PC before reaching out to your hosting provider can save time and potentially resolve the problem more quickly. By following the steps outlined in this blog, including checking network connectivity, verifying credentials, checking server status, and rebooting servers, you can often identify and resolve the issue on your own. However, if you've exhausted all available troubleshooting options or if the problem persists, don't hesitate to contact your hosting provider for assistance. They have the expertise and resources to address more complex issues and provide guidance tailored to your specific environment.