This Computer Cant Connect to the Remote Computer Try Connecting Again. If the Problem Continues

Let'due south endeavor to figure out how to fix an RDP connection mistake This computer can't connect to the remote computer. It occurs when yous effort to connect to a remote Windows computer or Windows Server host running Remote Desktop Services (RDS) role using the built-in Windows RDP client (mstsc.exe).

The problem looks like this: when you try to connect to a remote Windows server/desktop via RDP, the mstsc.exe customer freezes for a minute, and a window with the post-obit RDP mistake appears:

Remote Desktop Connection

This computer tin't connect to the remote computer.

Effort connecting once more. If the trouble continues, contact the owner of the remote calculator or your network ambassador.

Check the RDP Network Connectivity

First 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 certain the DNS accost of the remote RDP host is correctly resolved from your computer. Use the post-obit 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. Information technology should non contain static entries for the name or IP address of your remote server. Remove actress entries from the hosts file. You tin list the contents of the hosts file using PowerShell:

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

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

The Telnet client:

telnet rdp_server_name1 3389

PowerShell 4.0 and college:

Exam-NetConnection rdp_server_name1 -Port 3389 -InformationLevel Quiet

Note. If this command returned True, then the RDP port responds on the server and information technology's non blocked.

PowerShell all versions:

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

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

Y'all tin can remotely enable Remote Desktop on a Windows computer by changing the fDenyTSConnections registry.

Check the RDP Service Settings on the Remote Computer

If Remote Desktop is enabled, side by side 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 (Authoritative tools > Remote Desktop Services > Remote desktop Session Host Configuration). Click on RDP-TCP backdrop, and check the value of the Maximum connections property in Network Adapter tab.

The tsadmin.msc is missing in mod Windows versions (similar Windows x or Windows Server 2016), then you should set the RDP service settings using Group Policies.

1. Open up the local GPO editor on the remote host: Win + R > gpedit.msc;
2. Navigate to the following GPO section: Computer 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 figurer using Remote Desktop Services);
   
4. Likewise, check if the Remote Desktop Services do non limit the number of simultaneous connections to the server. A maximum number of RDP connections tin be specified in the section Connections using the policy Limit number of connections. Set unlimited connections past specifying 999999 in the selection RD Maximum Connections immune;

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

netstat -a -o|find "List"

Equally yous can come across, in our example, port 3389 is listening.

TCP 0.0.0.0:3389 DESKTOP-JOPF9:0 LISTENING 1096

Try to restart the Remote Desktop Services service. You can perform this activeness using the services.msc console or with the post-obit command in the elevated PowerShell prompt:

go-service TermService| Restart-Service -force -Verbose

Check RDP Port and Windows Firewall Settings

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

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp

Annotation the value of the PortNumber REG_DWORD parameter. It indicates the current TCP port assigned to the RDP service. In our example, this is 3389 (d3d hexadecimal value). If you have a different port, you can modify it to 3389 (in decimal), and restart the figurer.

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

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

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

Invoke-Command -ComputerName computername1 {Get-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Command\Concluding Server\WinStations\RDP-Tcp -Name PortNumber | select PortNumber}

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

Likewise, cheque that the rule which allows incoming RDP connections is enabled in the Windows Defender Firewall settings.

1. To practise this, get to the Control Panel > Arrangement and Security > Windows Defender Firewall;
2. Printing the "Let an app or feature through Windows Defender Firewall" > Change Settings;
3. Find the Remote Desktop dominion, and make certain it is enabled for Private and Public networks.

Hint. You lot can enable the born 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 tin can create a new ane:

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

Bank check your network connexion profile. You may come across various RDP connection errors if a Public profile is configured for your network location. Endeavor changing it to Private.

You can alter the network location using the Control Panel (Network and Net > Status > Connection Properties), or with PowerShell.

Go electric current network profile:

Get-NetConnectionProfile

Modify network connectedness profile to Individual:

Set-NetConnectionProfile -InterfaceIndex 14 -NetworkCategory Private

If y'all use a third-party firewall or antivirus, make certain it does non block incoming RDP connections. Y'all can temporarily disable your antivirus software.

Adjacent, bank check your network connection backdrop. Verify if the network connexion status is set to Public. Change information technology from Individual to Public if needed (Settings > Network & Cyberspace > Status > Network condition > Change connectedness backdrop).

In some cases, you demand to endeavour resetting the winsock and IP stack settings for the network adapter on the remote computer. Open up a command prompt with ambassador 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 need to reboot Windows.

RDP This estimator can't connect to the remote reckoner: a possible cause

Some other possible cause of the RDP error may be a high level of security, which is non supported by older versions of the RDP client.

In this example, open the Full general tab on the RDP-Tcp properties window, and change 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. But y'all can configure the Remote Desktop setting using the local Group Policy Editor (gpedit.msc). The necessary policies are located in the following GPO department: Local Estimator Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.

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

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

net stop TermService && net start TermService

RemoteApp Disconnected: Can't Connect to the Remote Reckoner

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

RemoteApp Disconnected

Your computer can't connect to the remote calculator because an error occurred on the remote computer that you want 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. Become to the registry central 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 utilize the RPC/HTTP connections instead of HTTP/UDP to connect to the server.

If the above solution didn't set up the RDP connection error, effort to modify the collection settings on the RDSH server side. Open properties of your problematic awarding collection, go to the Security tab, and uncheck the option "Let connections only from computers running Remote Desktop with Network Level Hallmark".

If the RemoteApp Disconnected error occurs on only a unmarried not-domain joined computer, it is possible, that the different LAN Manager/NTLM policy settings are used on the RDSH host and the desktop computer. Often, this tin can cause authentication bug.

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

1. To do this, open up the local GPO editor (gpedit.msc);
2. Become to the GPO department higher up;
3. Enable the policy "Network Security: LAN Director authentication level", and set its value to Ship NTLMv2 Response but;
4. Update the policies on the client with the command gpupdate;
5. Check your RemoteApp connection.

Set: Can't Connect to the Remote Desktop Gateway Server

There is another fault related to Remote Desktop Gateway which is used to deliver RemoteApps to users:

RemoteApp Disconnected.

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

This fault looks like this:

Your computer can't connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Effort reconnecting afterwards or contact your network administrator for assistance.

If yous are facing one of the errors to a higher place, and so, most likely, the problem is that your computer tin't resolve the public FQDN name of your Remote Desktop Gateway server. In some cases, the public RDGW proper noun tin can't match the hostname.

To fix this problem:

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

   iisreset

Too, check your RDGW document. Your certificate must not be expired.

You can find your SSL certificate info by going to Server Managing director > Remote Desktop Services > Collections > Your_Collection > Tasks > Edit Deployment Properties > Certificates > RD Gateway > View Details. Check the certificate expiration date.

Get back to your client's PC, and try to showtime a new RDP session. The connection should be established successfully.

Remote Desktop Connexion: Error Code 0x904, Extended Error Code: 0x7

In modernistic versions of Windows 10/11 and Windows Server 2016/2019/2022, you may see another common RDP connectedness error:

Remote Desktop Connection

This estimator tin can't connect to the remote estimator.

Try connecting once again.

Mistake Lawmaking: 0x904

Extended Error Lawmaking: 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 slow. Try to reconnect to your VPN workspace or modify your ISP.

• Author
• Contempo Posts

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

montgomerywhily1994.blogspot.com

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

Share this post