Check Your Account and Server Information Then Try Again

Let's try to effigy out how to set an RDP connection error This calculator tin't connect to the remote computer. It occurs when you attempt to connect to a remote Windows computer or Windows Server host running Remote Desktop Services (RDS) role using the congenital-in Windows RDP client (mstsc.exe).

The problem looks like this: when y'all try to connect to a remote Windows server/desktop via RDP, the mstsc.exe client freezes for a minute, and a window with the following RDP error appears:

Remote Desktop Connection

This estimator can't connect to the remote computer.

Endeavor connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.

Check the RDP Network Connectivity

Showtime of all, check if the remote computer is accessible from your device over the network, and the default Remote Desktop port (TCP 3389) is responding (and non blocked by firewalls).

Brand sure the DNS address of the remote RDP host is correctly resolved from your estimator. Use the following commands:

nslookup rdp_server_name1
ping rdp_server_name1
              

If the DNS proper noun is not resolved properly, check your DNS settings or endeavor connecting to a remote host using its IP address.

Hint. Be sure to check the contents of the local hosts file. It should non comprise static entries for the proper name or IP accost of your remote server. Remove extra entries from the hosts file. Yous tin can list the contents of the hosts file using PowerShell:

Get-Content $env:SystemRoot\System32\Drivers\etc\hosts

You tin check the RDP port availability on a remote server from a client workstation using:

The Telnet customer:

telnet rdp_server_name1 3389

PowerShell four.0 and higher:

Test-NetConnection rdp_server_name1 -Port 3389 -InformationLevel Tranquillity

Annotation. If this command returned True, so the RDP port responds on the server and it'due south non blocked.

PowerShell all versions:

New-Object System.Net.Sockets.TcpClient).Connect('rdp_server_name1', 3389)

If port 3389 is unavailable, you should check if the Remote Connexion is enabled on the remote server (right-click on Start push button > Settings > System > Remote Desktop > Enable Remote Desktop).

You lot tin can remotely enable Remote Desktop on a Windows computer by changing the fDenyTSConnections registry.

Check the RDP Service Settings on the Remote Calculator

If Remote Desktop is enabled, adjacent you should check the setting, which determines the maximum number of simultaneous users' connections to a Remote Desktop. Open up tsadmin.msc mmc snap-in (Administrative tools > Remote Desktop Services > Remote desktop Session Host Configuration). Click on RDP-TCP properties, and check the value of the Maximum connections property in Network Adapter tab.

The tsadmin.msc is missing in mod Windows versions (similar Windows ten or Windows Server 2016), and so y'all should set the RDP service settings using Group Policies.

1. Open the local GPO editor on the remote host: Win + R > gpedit.msc;
2. Navigate to the following GPO section: Reckoner Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections;
3. Enable the policy parameter named Allow users to connect remotely using Remote Desktop Services (if this policy is disabled, the remote user will not be able to connect to this reckoner using Remote Desktop Services);
   
4. Besides, check if the Remote Desktop Services do not limit the number of simultaneous connections to the server. A maximum number of RDP connections can be specified in the section Connections using the policy Limit number of connections. Prepare unlimited connections by specifying 999999 in the option RD Maximum Connections allowed;

Use the netstat command to verify if TCP port 3389 is in the Listening state. Open a command prompt equally administrator, and execute the command:

netstat -a -o|find "Listing"

As you tin can see, in our example, port 3389 is listening.

TCP 0.0.0.0:3389 DESKTOP-JOPF9:0 LISTENING 1096

Endeavour to restart the Remote Desktop Services service. You can perform this action using the services.msc console or with the following command in the elevated PowerShell prompt:

get-service TermService| Restart-Service -forcefulness -Verbose

Check RDP Port and Windows Firewall Settings

In some cases, the ambassador can modify the RDP port number from default 3389 to something else (although Microsoft does non recommend this). To check the current port on which the Remote Desktop service is listening on the computer, open up the registry editor (regedit.exe), and go to the registry key:

HKEY_LOCAL_MACHINE\Organisation\CurrentControlSet\Control\Final Server\WinStations\RDP-Tcp

Note the value of the PortNumber REG_DWORD parameter. It indicates the current TCP port assigned to the RDP service. In our instance, this is 3389 (d3d hexadecimal value). If y'all have a different port, you lot can change information technology to 3389 (in decimal), and restart the estimator.

You can cheque the electric current Remote Desktop listening port number using PowerShell:

Get-ItemProperty -Path 'HKLM:\Organisation\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -name "PortNumber"

In order to check the RDP port on a remote computer, use the Invoke-Command control:

Invoke-Command -ComputerName computername1 {Get-ItemProperty -Path HKLM:\Organization\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp -Proper name PortNumber | select PortNumber}

If a non-standard port is configured for Remote Desktop on a remote computer, you must specify the port number separated by a colon when connecting to the computer through the Remote Desktop Connection client. For instance, rdp_server_name1:3320.

Also, bank check that the rule which allows incoming RDP connections is enabled in the Windows Defender Firewall settings.

1. To exercise this, go to the Control Panel > Arrangement and Security > Windows Defender Firewall;
2. Press the "Let an app or feature through Windows Defender Firewall" > Alter Settings;
3. Find the Remote Desktop rule, and brand sure it is enabled for Private and Public networks.

Hint. You tin can enable the built-in firewall rule for the Remote Desktop Service running on port TCP/3389 using PowerShell:

Enable-NetFirewallRule -DisplayGroup "Remote Desktop"

If this built-in firewall rule is missing, you can create a new ane:

New-NetFirewallRule -DisplayName "AllowRDP_connection" -Direction Inbound -Protocol TCP –LocalPort 3389 -Action Allow

Check your network connection profile. You may see diverse RDP connexion errors if a Public contour is configured for your network location. Try irresolute it to Private.

You can change the network location using the Command Panel (Network and Cyberspace > Status > Connection Backdrop), or with PowerShell.

Get current network profile:

Become-NetConnectionProfile

Change network connection profile to Private:

Set-NetConnectionProfile -InterfaceIndex 14 -NetworkCategory Individual

If you use a 3rd-party firewall or antivirus, make sure it does not block incoming RDP connections. You can temporarily disable your antivirus software.

Next, check your network connexion properties. Verify if the network connection status is set to Public. Change it from Individual to Public if needed (Settings > Network & Cyberspace > Status > Network condition > Change connexion backdrop).

In some cases, you need to attempt resetting the winsock and IP stack settings for the network adapter on the remote computer. Open a command prompt with administrator rights and run the commands:

netsh winsock reset
netsh int ip reset
                
ipconfig /release
                
ipconfig /renew
                
ipconfig /flushdns
              

In Windows x, there is a special option to reset network settings in Settings > Network and Internet > Status > Network reset.

After resetting the network settings, you demand to reboot Windows.

RDP This computer tin't connect to the remote computer: a possible cause

Another possible cause of the RDP error may be a high level of security, which is not supported by older versions of the RDP customer.

In this case, open the General tab on the RDP-Tcp properties window, and modify the Security layer from default Negotiate to less secure RDP Security Layer.

Tip. Snap-in tsadmin.msc and RDP-Tcp Properties dialog boxes are missing in Windows Server 2019/2016 and 2012 R2. Just you can configure the Remote Desktop setting using the local Group Policy Editor (gpedit.msc). The necessary policies are located in the following GPO section: Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.

RDP security level tin can be specified using the policy named Require user of specific security layer for remote (RDP) connections. Enable this policy, and in the dropdown carte select the RDP Security level. This will change the Remote Desktop security layer from the default Negotiate to the less secure RDP.

Save the changes, update local GPO settings using the "gpupdate /strength" command, and restart the Remote Desktop Service:

cyberspace stop TermService && net start TermService

RemoteApp Asunder: Can't Connect to the Remote Computer

In some cases, when connecting with Windows ten to a remote desktop on Remote Desktop Gateway on Windows 2012 R2, an error occurs:

RemoteApp Disconnected

Your computer can't connect to the remote computer because an error occurred on the remote figurer that you desire to connect to. Contact your network administrator for assistance.

To fix this problem, you need to perform the following steps on the RDP client:

1. Open the Registry Editor (regedit.exe);
2. Get to the registry fundamental HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client;
3. Create a DWORD parameter with the name RDGClientTransport and the value 1;
4. Restart the computer.

The RDGClientTransport parameter forces the clients to use the RPC/HTTP connections instead of HTTP/UDP to connect to the server.

If the in a higher place solution didn't set up the RDP connection error, try to change the drove settings on the RDSH server side. Open properties of your problematic application collection, get to the Security tab, and uncheck the pick "Let connections only from computers running Remote Desktop with Network Level Authentication".

If the RemoteApp Asunder mistake occurs on only a unmarried not-domain joined computer, information technology is possible, that the different LAN Manager/NTLM policy settings are used on the RDSH host and the desktop computer. Often, this can crusade authentication problems.

Check current Network Security: LAN Manager authentication level policy settings on RSDH using the command gpresult /r c:\tmp\gpreport.html (audit html file) or using rsop.msc (this policy is located in the section Estimator Configuration > Windows Settings > Security Settings > Local Policies > Security Options). If LM and NTLMv1 protocols are disabled on your RDSH server (Transport NTLMv2 Response only policy value), you must alter the appropriate policy settings on the client side.

1. To exercise this, open the local GPO editor (gpedit.msc);
2. Go to the GPO department higher up;
3. Enable the policy "Network Security: LAN Manager hallmark level", and set its value to Send NTLMv2 Response only;
4. Update the policies on the client with the command gpupdate;
5. Cheque your RemoteApp connexion.

Fix: Tin can't Connect to the Remote Desktop Gateway Server

At that place is another error related to Remote Desktop Gateway which is used to evangelize RemoteApps to users:

RemoteApp Asunder.

Your computer tin can't connect to the remote estimator because the Remote Desktop Gateway server address is unreachable or incorrect. Type a valid Remote Desktop Gateway server address.

This error looks similar this:

Your estimator tin't connect to the remote reckoner because the Remote Desktop Gateway server is temporarily unavailable. Try reconnecting later on or contact your network administrator for assistance.

If yous are facing one of the errors above, then, near likely, the problem is that your computer can't resolve the public FQDN proper noun of your Remote Desktop Gateway server. In some cases, the public RDGW name can't match the hostname.

To fix this trouble:

1. Open up the Cyberspace Information Services (IIS) Manager on the Remote Desktop Gateway server;
2. Go to the IIS section Sites > Default Website > RDWeb > Pages > Application Settings;
3. For the DefaultTSGateway value, enter the server's FQDN public proper noun of your RD Gateway server, and and then restart the web services with the command:

   iisreset

Likewise, check your RDGW certificate. Your certificate must not be expired.

Yous can observe your SSL certificate info by going to Server Manager > Remote Desktop Services > Collections > Your_Collection > Tasks > Edit Deployment Properties > Certificates > RD Gateway > View Details. Cheque the certificate expiration date.

Go dorsum to your client's PC, and effort to beginning a new RDP session. The connection should exist established successfully.

Remote Desktop Connectedness: Fault Code 0x904, Extended Error Code: 0x7

In modern versions of Windows 10/11 and Windows Server 2016/2019/2022, you may encounter another common RDP connection error:

Remote Desktop Connection

This computer can't connect to the remote computer.

Try connecting again.

Error Code: 0x904

Extended Error Code: 0x7

Most often, when connecting to RDP, an error 0x904 appears on an unstable network connection (not enough bandwidth, packages lost, mismatch encryption cyphers, etc.), or when your VPN connection to a corporate network is too boring. Attempt to reconnect to your VPN workspace or change your Isp.

• Writer
• Contempo Posts

I enjoy technology and developing websites. Since 2012 I'm running a few of my own websites, and share useful content on gadgets, PC administration and website promotion.

alvarezcreeidell1956.blogspot.com

Source: https://theitbros.com/this-computer-cant-connect-to-the-remote-computer/

Share this post