Remote Desktop Troubleshooting Windows User

Remote Desktop Protocol (or RDP) is a protocol that is the most common way To gain administrative access to a Windows server. RDP is available on all Versions of Windows Server and a client (called Remote Desktop Connection) is Included ! with all versions of the. Windows desktop operating system. Connecting to your server via RDP gives you complete control of the server desktop environment ! As if you were sitting in front of the server’s monitor and keyboard. Depending on your permissions and settings, you can copy and delete files, Change file Permissions or settings, and even print documents from the server

For a remote desktop connection, you first need to have some basic settings and information

1. Using the Remote Desktop Protocol to manage Windows server  generally requires some basic settings and information about the server.

1. First, the Remote Desktop service must be running on the server To which you want to connect (RDP uses port 3389 by default).
2. Second, you must have the IP address of the server
3. Third, you must have a username and password that is allowed to connect remotely to the server (often, this is the primary administrator account, but can also be a secondary account set up specifically for remote access purposes). .
4. Finally, the Windows firewall (and any other hardware or software firewall) must be configured ,To allow a remote connection to your location.

Once you have all of the correct settings enabled, IP address and user account details, You can connect RDP to your server Just launch the RDP client, enter the IP address of the server and the user credentials, and log in to the server using what looks like the standard Windows desktop environment.

Helpful as a Remote Desktop Protocol When it comes To managing your Windows Server, many times connections also fail, which can be very frustrating as the error message is usually not very useful (often just shown below Window).

The error shown above means that for some reason, Your client was unable to make a connection to the Windows Server via the Remote Desktop Protocol When you are facing connectivity problems, there are several ways by which you can try to solve the problem and perform a connection check.

Connectivity Issue

Ensure you can reach the server via ICMP (or Ping). Most desktop operating systems will allow you to send small bits of Information to the Computer to verify connectivity and connection speeds Generally, you just need to open a terminal window (on a Windows desktop, press the Window key, then type cmd and press enter) and enter the following command: ping IP or 192.168.1.139. Normally, you’ll receive an output that is similar:

1. This output shows the pings were successful to the destination and took between 50 ms and 150 ms to complete. These pings indicate a successful connection to the server as desired (at least over ICMP). If the output for the command shows a failure to respond, we know there is some network interference.
2. The ping test fails (indicated by repeating asterisks), check your internet connectivity to guarantee that you can reach other resources on the internet. If not, you may need to contact your local service provider to restore your internet access.
3. Reaching other internet sites but not your server indicates your server is refusing connections from your IP address , (due to security software or firewall settings). To verify you may need to contact your hosting company that is blocked by your server does not have an IP address , You can find your current public IP address by going to https://whatismyipaddress.com/
4. Can you ping your server, but still not connect to RDP? This is a problem with the RDP service or your firewall. Therefore, there is an option to open the RDP port.

Firewall Issues

The best practice in configuring a firewall is to allow the least amount of access for various connections. To the server. Limiting Connections to a Particular Service, such as RDP, is called “scooping” for that Service. If your configured Windows firewall scopes traffic over RDP, It is possible . That a user may not be able to connect because their IP address is not included in the rule. Accessing the server via RDP from one user but not another user, check the firewall; Their IP Addresses cannot be Included In the allowed list of IPs for remote desktop access. Therefore, you will have to make some changes according to the image given below in your firewall.

1. Log into the server, click on the Windows icon, and type Windows Firewall in the search bar. And  change firewall setting

1. Click on Windows Firewall with Advanced Security.
2. Click on Inbound Rules
3. Scroll down to find a rule labeled RDP (or using port 3389)
4. Double-click on the rule, then click the Scope tab
5. Make sure the user’s Current IP address is included in the list of allowed Remote IPs