Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After yum update, when I restarted aws ec2 instance,i was not able to connect the instance using putty.It was showing "Network error: Connection timed out".
I have enabled port 22 also.
Could you please help me to resolve this issue.
When you say you have enabled port 22, I presume you mean that it is allowed through your firewall.
E2C is an acronym used for a couple of things: please provide more detail.
Example: http://www.hqmc.marines.mil/e2o/E2C-ExFOB/
General first step:
#1 Have you verified that you can ping the remote (e2c) node? Network path (routing) and addressing is required, ping is one way to verify.
#2 Have you verified that sshd is running on the remote node? Check your process list and sshd configuration please.
#3 Have you checked your netstat report and verified that sshd is listening on port 22 on the remote node, and at the proper address on that node?
Have you checked the screenshot of the instance to make sure that it came back up successfully to the login prompt?
Is it running on a public or private subnet? If on private, have you verified your NAT/Bastion/jumpbox is up and port forwarding is working?
If it's on a public, do you have an elastic IP? If not, have you checked if maybe your IP changed from the reboot?
If you're using AWS DNS to connect, if you don't have an elastic IP, did you check if maybe your AWS DNS has changed?
Last edited by Timothy Miller; 08-11-2017 at 12:12 PM.
Thanks for your quick response.Instance has elastic ip. I had stopped and restarted instance with no success.
Network at our end has no issues.
Please help me.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.