Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 783
  • Last Modified:

why my aws ec2 can not be connected with port 80?

Hi,
I am using aws to do evaluation.
I have started one aws ec2 instance, also, the security group open the icmp and http port.
I have bought one elastic ip and bound it to that ec2 instance.
The EC2 has private ip: 10.146.33.203
EC2 has public ip: 54.248.119.32
My machine public ip is: 180.157.7.67
The Zend server ce was installed on that EC2 machine. And it works as http://localhost/
When I access it from http://54.248.119.32 , nothing return to my web browser.
I do test using telnet 54.248.119.32 80 to see what happens.
I capture the packets in the EC2 instance and saw the incoming TCP session was being requested by my machine(That proves the aws security group configure well)
Unfortunately, there was nothing replied out from ec2!
What is the problem?
Can anyone help me out?
Please see the attached screen capture for information.
Thanks!
tcp80-nok.JPG
0
matiascx
Asked:
matiascx
  • 3
  • 2
2 Solutions
 
shalomcCommented:
Try the server's local firewall...
0
 
matiascxAuthor Commented:
Dear Sir,
What do you mean for the local firewall?
I can capture the incoming traffic for the tcp connection request to port 80.
Can you give more explaination?
I doubt the problem is located at Zend CE itself??
0
 
shalomcCommented:
A windows server has a built-in firewall, and often it is not allowing ingress communications to apache web server.
Can you verify that it allows ingress traffic?
0
 
matiascxAuthor Commented:
Dear shalomc,
Thanks to your expertise proposal.
It really works now.
The root cause is windows local firewall block the traffic.

matiascx
0
 
matiascxAuthor Commented:
Thanks!
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now