![]() ![]() In the output of the preceding command, verify that TcpTestSucceeded is True. Open a PowerShell window from your local device, and then run the following command: Test-NetConnection -ComputerName -Port 3389Ģ. ![]() Confirm you're using the correct firewall and network configurationġ. Verify that port 3389 isn't blocked by your AWS security group, network ACL, OS firewall, or antivirus software. The instance is unreachable on the public IP address behind the NAT Gateway. If the instance is in a subnet that uses a NAT Gateway, make sure that you're connecting to the instance's private IP address. Verify that you're using the correct IP address Test connecting to the instance through RDP again.Attach the secondary network interface to the instance.If the screenshot indicates that the instance operating system (OS) boots successfully but fails instance status checks, then complete the following steps: You can view an instance screenshot for visibility into the instance's status. Troubleshoot using an instance screenshot If you receive the RDP error message "An internal error occurred", then see Step: 1 Check the RDP port on the Microsoft website. Resolution Troubleshoot the error message "An internal error occurred" ![]()
0 Comments
Leave a Reply. |