I cannot connect windows 2019 base after created successful

Question

I cannot ping or telnet to rdp port(3389) from my NAT instance or my local PC event I already enabled all tracffics from any IPv4 for that instance.

I tried creating many times, but I got the same result.
I think the instance windows was not start normally.

In two weeks ago, I created one in HongKong zone and didn't face the problem.
Now, I tred in Singapore zone.

Thanks

Accepted Answer

So i am assuming that your windows instance is having public IP associated and we have the Security Group enabled for 3389 for your machine public IP ?? Or NAT instance in AWS are into same network with proper rule allowed?

Ideally if networking and firewall is correct we should be able to connect windows .. I tested and its working properly.

On Ping:-
In terms of ping what i have seen on windows that if you dont enable icmpv4 packets from inbound windows firewall rules that will not allow you to ping.

Let me know if above pointers are useful.

Answer

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.

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

I cannot connect windows 2019 base after created successful

相關內容