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

Unable To login using ENI static Ip

0

I have a redhat instance on which i have attached a Network interface at index 1.That network interface is having a static ip . when i am trying to connect the ec2 with the static ip of netwrok interface it is giving connection timeout error.

4 Answers
0

If you can't connect to an Amazon EC2 instance or an elastic network interface that has an attached Elastic IP address, be sure that:

Security group rules for inbound traffic allow connection to the port or protocol. Inbound and outbound network access control list (network ACL) rules allow connection to the port or protocol. The route table for the subnet of the elastic network interface has a route to send and receive traffic from the internet. The OS firewall on the Amazon EC2 instance allows traffic to the port or protocol.

profile picture
answered a month ago
  • Can you check NACL and route table entries.

  • i can see the route table subnet associations is having the subnet defined my ec2 is having 2 eni attached . i am able to login using the IP of ENI placed at eth0 unable to login using the IP of ENI placed at eth1

    i tried adding it to the route ip route add default via 10...* dev eth0 proto dhcp metric tab 1

    Now i am getting a prompt for login as on my another static Ip but after giving login as it is giving connection timed out

0

If you try to connect to your instance and get an error message Network error: Connection timed out or Error connecting to [instance], reason: -> Connection timed out: connect, try the following:

Check your security group rules.

You need a security group rule that allows inbound traffic from your local computer's public IPv4 address on the proper port.

profile picture
answered a month ago
  • Hi , I checked the security group it is having the port and cidr defined but still getting Network error:Network error: Connection timed out

0

After you assign a secondary private IPv4 address to your instance, you need to configure the operating system on your instance to recognize the secondary private IP address. If you are using Amazon Linux, the ec2-net-utils package can take care of this step for you. It configures additional network interfaces that you attach while the instance is running. If you are using another Linux distribution, see the documentation for your Linux distribution. Make sure to mark the answer as accepted once your issue is resolved.

profile picture
answered a month ago
0

Can you confirm if your issue is resolved ?

profile picture
answered a month ago

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