Support for remote access error (Windows)

Available in Classic

This document describes the symptoms of server remote access errors in Windows, as well as their causes and solutions.

Check windows server remote access settings

To remotely access the Windows server, ensure that the IP or subnet of the server to access is applied to the ACG. If not applied, see Set ACG and change the ACG settings.

If there is no problem in ACG settings, check the following matters:

• Check if the server allows access to SSH/RDP service.

  • SSH service: TCP, allowed port 22
  • RDP service: TCP, allowed port 3389
  Note

  If the port setting on the server has been changed, update the settings accordingly.

• Check the port forwarding settings.

  • If both public IP and port forwarding are set simultaneously, you cannot communicate through a public IP. When using a public IP, remove the port forward settings.

Even if no problem is found as a result of checking the above, the SSH service port or the RDP service port may not work normally for various reasons. In such cases, the [Server connection console] button is activated in server information of NAVER Cloud Platform. To resolve this issue, see Troubleshooting Windows server remote access errors.

Troubleshooting Windows server remote access errors

If Windows server remote access errors occur, follow the following steps to troubleshoot them.

1. Check if the remote access is allowed
2. Check service status
3. How to resolve This could be due to CredSSP encryption Oracle remediation
4. Check firewall
5. Check routing

1. Check if the remote access is allowed

Check if the remote access is allowed on the Windows server.

1. Click This PC > Properties on the Windows server.
   
2. Click Remote Settings.
   
3. Click the [Remote] tab and click to select the Allow remote connections to this computer of Remote desktop.
   

4. Click the [OK] button.
   • The settings are saved.

2. Check service status

Check the status of the Windows server remote access service.

1. Run services.msc in the cmd window.
2. From Services, check if Remote Desktop Configuration, Remote Desktop Services, and Remote Desktop Services UserMode port Redirector are Running.
   • If they are stopped, after right-clicking, click the start menu to start the service.
     

3. How to resolve This could be due to CredSSP encryption oracle remediation

To resolve the error of This could be due to CredSSP encryption oracle remediation:

1. Run gpedit.msc in the cmd window.
2. Click Computer Configuration > Administrative Templates > System > Credentials Delegation > Encryption Oracle Remediation, in that order.
   
3. Select Enable, select Vulnerable in the Protection Level, and click the [OK] button.
   
4. Run gpupdate /force in the cmd window.

4. Check firewall

By default, the firewall is off. If the firewall is run, add an inbound rule so it can operate normally.

1. Run wf.msc in the cmd window.
2. In the [Inbound Rules] tab, select Remote Desktop - User Mode (TCP-In), right-click, and click Enable Rule.
   

5. Check routing

If there is no default route for the private IP, communication may not work. Run the route print command in the cmd window to check the routing table of the Windows server.