For more information, see Reset a lost or expired Windows administrator Verify that the password has not expired. (use AWSSupport-TroubleshootRDP to enable Remote Desktop connections). Verify that Remote Desktop connections are allowed on your instance Port, which by default is 3389 (use AWSSupport-TroubleshootRDP to read the current RDP port and change it back to 3389). Verify that you are connecting to the correct Remote Desktop Protocol Verify that the Remote Desktop Service (TermService) Startup Type isĪutomatic and the service is started (use AWSSupport-TroubleshootRDP to enable and start the RDP service). That are not part of an Active Directory domain (use AWSSupport-TroubleshootRDP to disable NLA). Verify that Network Level Authentication is disabled on instances Restore its root volume because of a disk signature collision. You must complete the following steps or you won't be able to boot the original instance after you (Optional) If your temporary instance is based on the same AMI that the original instance is based on, Select the key you just loaded and navigate toĬontrolSet001\Services\SharedAccess\Parameters\FirewallPolicy.ĮnableFirewall from 1 to 0. Specify a key name when prompted (you can use any name). Connect to the temporary instance, open the Temporary instance using the AWS Windows AMI for Windows Server 2012.Īttach the root volume from the affected instance to this You restore its root volume because of a disk signature collision.Īlternatively, select a different AMI for the temporary instance.įor example, if the original instance uses the AWS Windows AMI for Windows Server 2008 R2, launch the You must complete additional steps or you won't be able to boot the original instance after If your temporary instance is based on the same AMI that the original instance is based on, Instance that is not configured for AWS Systems Manager, use AWSSupport-ExecuteEC2Rescue, or use the following manual steps: You can useĪWSSupport-TroubleshootRDP to disable the Windows Firewall profiles using SSM Agent. We recommend that you disable Windows FirewallĪnd control access to your instance using security group rules. Verify that Windows Firewall, or other firewall software, is not blocking ForĬustom route table (Internet Gateways) in the Traffic destined outside the VPC to the internet gateway for the VPC. Verify that the route table for the subnet has a route that sends all ( Amazon EC2 User Guide for Linux Instances). Verify that the instance has passed status checks. That you missed a character or got an extra white space character when you Not work, try typing them manually when prompted. If you copied the password but get the error Your credentials did More information, see Create a security group. Verify that your security group has a rule that allows RDP access. For more information, see Configure IPv6 on Your Instances in the Not automatically configured to recognize an IPv6 address assigned to the If you launchedĪn instance from a Windows Server 2008 SP2 AMI or earlier, your instance is To connect to your instance using an IPv6 address, check that your localĬomputer has an IPv6 address and is configured to use IPv6. If not, you canĪssociate an Elastic IP address with your instance. Verify that your instance has a public IPv4 address. You do not see a public DNS name, you must enable DNS hostnames. (IPv4) in the details pane.) If your instance is in a VPC and (In the Amazon EC2Ĭonsole, select the instance and check Public DNS Verify that you're using the correct public DNS hostname.
0 kommentar(er)
