--- title: "Support for remote access error (Windows)" slug: "server-ts-remote-win-vpc" tags: ["troubleshooting", "vpc", "Server", "remote"] updated: 2026-09-17T09:17:55Z published: 2026-09-17T09:17:55Z canonical: "guide.ncloud-docs.com/server-ts-remote-win-vpc" --- > ## Documentation Index > Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # Support for remote access error (Windows) Available in VPC 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](/docs/en/server-acg-vpc#ACG%EC%84%A4%EC%A0%95) 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. Note If the port setting on the server has been changed, update the settings accordingly. - SSH service: TCP, allowed port 22 - RDP service: TCP, allowed port 3389 - 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](/docs/en/server-ts-remote-win-vpc#Windows%EC%84%9C%EB%B2%84%EC%9B%90%EA%B2%A9%EC%A0%91%EC%86%8D%EC%98%A4%EB%A5%98%ED%95%B4%EA%B2%B0). ![server-ts-remote-win-vpc_image01_en](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/server-ts-remote-win-vpc_image01_en.png?sv=2026-02-06&spr=https&st=2026-10-27T16%3A29%3A05Z&se=2026-10-27T17%3A29%3A05Z&sr=c&sp=r&sig=o7Dy1Yr51IjjK%2BeDkcbinntdQ3Et9edCTM63oiWZD%2F8%3D) ## Troubleshooting Windows server remote access problems If a Windows server remote access error occurs, check the following matters to take action. - [1. Check if the remote access is allowed](/docs/en/server-ts-remote-win-vpc#1%EC%9B%90%EA%B2%A9%EC%A0%91%EC%86%8D%ED%97%88%EC%9A%A9%EC%83%81%ED%83%9C%ED%99%95%EC%9D%B8) - [2. Check service status](/docs/en/server-ts-remote-win-vpc#2%EC%84%9C%EB%B9%84%EC%8A%A4%EC%83%81%ED%83%9C%ED%99%95%EC%9D%B8) - [3. How to resolve This could be due to CredSSP encryption oracle remediation](/docs/en/server-ts-remote-win-vpc#3ThiscouldbeduetoCredSSPencryptionoracleremediation%ED%95%B4%EA%B2%B0%EB%B0%A9%EB%B2%95) - [4. Check firewall](/docs/en/server-ts-remote-win-vpc#4%EB%B0%A9%ED%99%94%EB%B2%BD%ED%99%95%EC%9D%B8) - [5. Check routing](/docs/en/server-ts-remote-win-vpc#5%EB%9D%BC%EC%9A%B0%ED%8C%85%ED%99%95%EC%9D%B8) ### 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. ![server-ts-remote-win-vpc_image18](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/server-ts-remote-win-vpc_image18.png?sv=2026-02-06&spr=https&st=2026-10-27T16%3A29%3A05Z&se=2026-10-27T17%3A29%3A05Z&sr=c&sp=r&sig=o7Dy1Yr51IjjK%2BeDkcbinntdQ3Et9edCTM63oiWZD%2F8%3D) 2. Click **Remote Settings**. ![server-ts-remote-win-vpc_image19](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/server-ts-remote-win-vpc_image19.png?sv=2026-02-06&spr=https&st=2026-10-27T16%3A29%3A05Z&se=2026-10-27T17%3A29%3A05Z&sr=c&sp=r&sig=o7Dy1Yr51IjjK%2BeDkcbinntdQ3Et9edCTM63oiWZD%2F8%3D) 3. Click the **[Remote]** tab and click to select the **Allow remote connections to this computer** of **Remote desktop**. ![server-ts-remote-win-vpc_image20](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/server-ts-remote-win-vpc_image20.png?sv=2026-02-06&spr=https&st=2026-10-27T16%3A29%3A05Z&se=2026-10-27T17%3A29%3A05Z&sr=c&sp=r&sig=o7Dy1Yr51IjjK%2BeDkcbinntdQ3Et9edCTM63oiWZD%2F8%3D) Note The **Allow remote connections to this computer > Allow connections only for computers running Remote Desktop with Network Level Authentication (recommended)** option is supported only in the same RDP version. Disable this option if you are unable to connect remotely after selecting this option. 1. 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. ![server-ts-remote-win-vpc_image21](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/server-ts-remote-win-vpc_image21.png?sv=2026-02-06&spr=https&st=2026-10-27T16%3A29%3A05Z&se=2026-10-27T17%3A29%3A05Z&sr=c&sp=r&sig=o7Dy1Yr51IjjK%2BeDkcbinntdQ3Et9edCTM63oiWZD%2F8%3D) ### 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: Note Proceed with the following steps in the client you want to RDP access the Windows server. 1. Run `gpedit.msc` in the cmd window. 2. Click **Computer Configuration > Administrative Templates > System > Credentials Delegation > Encryption Oracle Remediation,** in that order. ![server-ts-remote-win-vpc_image22](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/server-ts-remote-win-vpc_image22.png?sv=2026-02-06&spr=https&st=2026-10-27T16%3A29%3A05Z&se=2026-10-27T17%3A29%3A05Z&sr=c&sp=r&sig=o7Dy1Yr51IjjK%2BeDkcbinntdQ3Et9edCTM63oiWZD%2F8%3D) 3. Select **Enable**, and select **Vulnerable** in **Protection Level**. ![server-ts-remote-win-vpc_image23](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/server-ts-remote-win-vpc_image23.png?sv=2026-02-06&spr=https&st=2026-10-27T16%3A29%3A05Z&se=2026-10-27T17%3A29%3A05Z&sr=c&sp=r&sig=o7Dy1Yr51IjjK%2BeDkcbinntdQ3Et9edCTM63oiWZD%2F8%3D) 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. ![server-ts-remote-win-vpc_image24](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/server-ts-remote-win-vpc_image24.png?sv=2026-02-06&spr=https&st=2026-10-27T16%3A29%3A05Z&se=2026-10-27T17%3A29%3A05Z&sr=c&sp=r&sig=o7Dy1Yr51IjjK%2BeDkcbinntdQ3Et9edCTM63oiWZD%2F8%3D) 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**. ![server-ts-remote-win-vpc_image25](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/server-ts-remote-win-vpc_image25.png?sv=2026-02-06&spr=https&st=2026-10-27T16%3A29%3A05Z&se=2026-10-27T17%3A29%3A05Z&sr=c&sp=r&sig=o7Dy1Yr51IjjK%2BeDkcbinntdQ3Et9edCTM63oiWZD%2F8%3D) ### 5. Check routing If there is no default route for the private IP, communication may not work. In VPC, also check the static route for 169.254.0.0/16. Run the `route print` command in the cmd window to check the routing table of the Windows server. ![server-ts-remote-win-vpc_image29](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/server-ts-remote-win-vpc_image29.png?sv=2026-02-06&spr=https&st=2026-10-27T16%3A29%3A05Z&se=2026-10-27T17%3A29%3A05Z&sr=c&sp=r&sig=o7Dy1Yr51IjjK%2BeDkcbinntdQ3Et9edCTM63oiWZD%2F8%3D)