on 11-23-2012 9:10 PM
Hi Experts,
Can anybody help me out to understand what goes wrong while creating connection between AWS EC2 and Putty.
My EC2 instance work fine. But after putting all the require inputs in Putty the console has open but it did not show any
login prompt and after few times it shows time out.I have no clue. Please guide me to overcome this issue.
I am using windows Vista as OS.
Regards
Kaushik
I have seen similar behavior from Putty when port 22 is somehow blocked. That could be in the AWS configuration (enable port 22 for your IP address or, if you are brave, for all IP addresses) or possibly if you a traversing a corporate firewall.
Best of Luck
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Joe,
Thanks for your answer. I have stop Vista Firewall as well as McAfee and also assign Port:22 /TCP as allowable program through Firewall Exception functionality.
Currently,Port 22 is open and I am able to log in in my PC through Putty. But still struggling to make communication with EC2 instance. For your reference , I am putting current status of Port 22.
C:\Users>netstat -ant | find "22"
TCP 0.0.0.0:22 0.0.0.0:0 LISTENING InHost.
Further more, i have create one new Instance and try to reconnect this instance through Putty.But still no hope.
I still not have any clue where it went wrong for all the suffering.
My ISP is Reliance and I am using Netconnect Broadband.
I am going to stop my instance if you want me to share the instance id for your checking , feel free to inform me.
Regards
Kaushik
It certainly appears that you have both the AWS side and your PC setup so that you should be able to communicate on port 22. I would suspect a problem with your ISP or perhaps your local router connecting to the ISP. I encountered something like that last week when I was in Madrid for our TechEd conference. At the hotel, it appeared that the network connection was blocking port 22. At the conference site, the public internet there seemed to have no trouble with port 22.
To debug this as inexpensively as possible, you might want to use one of the AWS linux micro instances which cost only a few cents per hour. You do not need to do anything on the instance, but when you know that you can connect to it on port 22 with your private key, you should then be able to connect to a SAP HANA One instance in the same way.
Hello Joe,
Thnx for your reply . I am also suspecting the same that it may be problem with my ISP. This ISP using multiple cross routers and everytime while connect with my node it is using different IP. If I send you brief information as output of "ipconfig -all" command would it be possible to you locate the problem, so that i can ask my ISP's network support eng.
to help me to sort out this issue.
Secondly, if you want I can send one of my instance id to you to check you are able to connect it or not.
I am using AWS EC2 instance which cost me 99 cent/ph after exhaust my $25 free coupon. U can check the instance details from below note:
Instance id:i- XXe XfbXX 'X- implies numeric figure'
AMI ID-ami-XXddXXXX 'X- implies numeric figure'
ami description-SAPHANAOne-Rev38-2
Platform-Other Linux
Owner-AWS-Marketplace
Root Device-ebs
Type-CC2 8 extra large.
Thank you again for your time and help.
Regards
kaushik
Kaushik,
We will contact you via private email since there may be information that we want to exchange that should not be publicly displayed.
For the record, I will note that while "ipconfig /all" is useful in understanding the characteristics of your local machine and it's connection to the Internet, it is of almost no value in understanding the various routers and firewalls that may lie between your machine and the AWS data centers.
User | Count |
---|---|
75 | |
10 | |
10 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.