- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Hello - Is your EC2 instance in a public subnet? Check if the routing table of the subnet that you used has a route to an internet gateway for the VPC. Also, verify if you are using the correct username and password. Sometimes, some workstations automatically add a domain (example "domain\Administrator") in the username field.
You may refer to the following AWS documentation for other troubleshooting tips: https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/troubleshoot-connect-windows-instance.html
Hi,
Check the below configurations:
- Security Group(s) rules applied to your NAT Instance and Target EC2 instance.
- NACL rules (both inbound and outbound) applied to Subnets.
- Route Table Routes (e.g. Your EC2 instance subnet is connected IGW).
You can utilize the AWS VPC Reachability Analyzer feature to troubleshoot your issue. This is really nice feature to troubleshoot such connectivity issues caused due to SG, NACL, or RT misconfiguration.
Regards, Ashish Patel
Contenuto pertinente
- AWS UFFICIALEAggiornata 10 mesi fa
- AWS UFFICIALEAggiornata 7 mesi fa