By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Having issues with communications between EC2 vms on the same subnet

0

I have an issue with EC2 vms not able to communicate with each other and hoping perhaps you can assist.

  • I have 4 instances all on the same subnet and vpc.

  • I have all traffic allowed to the subnet range of /20 on both inbound and outbound with regards to the security groups

  • EC2 B can be pinged by all but A, C and D can’t be pinged by B or each other

  • Can’t telnet to listening port on B either and FW port is opened to subnet. (All Windows OS btw)

Things I’ve tried:

I started with more stricter rules (sorta) but using a /16 instead of a /20 but for specific ports however forwarding of logs was not working. And I couldn’t ping anything not even EC2 B.

What am I missing?

  • Gary Mclean EXPERT
    a year ago

    Double check they are in the correct security groups.

    Also have you tried turning off windows firewall.

    Windows server can be funny also trying to determine a private and public network interface

Topics
Networking & Content DeliveryComputeAWS Well-Architected Framework
Tags
Amazon VPCAmazon EC2Networking & Content DeliverySecurityWindows
Language
English
rePost-User-5031910
asked a year ago1022 views
2 Answers
0

Have you altered the NACL for the subnet? The default should allow all traffic but if you have altered them, check that. Have you checked the OS level for firewall settings?

profile pictureAWS
EXPERT
iBehr
answered a year ago
  • Gary Mclean EXPERT
    a year ago

    That would be a good question. They said they are all on the same subnet so nacls wouldn’t come into play here.

0

You may want to check the Routing table(s) you are using in this VPC and subnets. If you have the original default VPC and main routing table to compare settings, look for a route target with 'local' Target and correct destination CIDR block for your subnet. Also check each subnet for similar Route table settings for local traffic.

There is a new feature in AWS Console for VPC which displays a Resource map of your VPC, might give clues to whatever is missing or misconfigured.

profile picture
cyrk-aws
answered a year ago
  • Gary Mclean EXPERT
    a year ago

    They said they are all on the same subnet. No routing needed

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content