1 Answer
- Newest
- Most votes
- Most comments
0
Hi Fahad,
When you're able to connect to your EC2 instance using its public IP but not through a private IP over a VPN, and you've ruled out the Windows Defender Firewall, there are still several things to check:
- VPN Configuration: Confirm that your VPN is correctly configured to route traffic to the VPC and that the private IP is accessible through it.
- Network ACLs and Security Groups: Check that the Network ACLs and security groups associated with the EC2 instance allow inbound RDP traffic from the VPN's network range.
- Route Tables: Verify that the VPC route tables have the necessary routes to direct traffic from the VPN to the EC2 instance.
- Instance Settings: Make sure that the instance is configured to listen for RDP connections on its private IP.
- RDP Service Status: Check that the RDP service is running on the instance and is configured to accept connections.
- Network Connectivity: Test the network connectivity from within the VPN to the EC2 instance's private IP using tools like ping or tracert.
If you've checked all the above and the issue persists, it could be worthwhile to look into VPC flow logs to see if the traffic is reaching the instance and if there's any pattern of denied traffic.
I'm here to help. Give me more details if it didn't work.
answered a month ago
Relevant content
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago