- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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?
That would be a good question. They said they are all on the same subnet so nacls wouldn’t come into play here.
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.
They said they are all on the same subnet. No routing needed
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
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