New answers tagged

0

The AWS instance install is the most obvious common point in this scenario, followed by your internet connection / router. First try ssh'ing in from a spot instance in the same AZ and check it's reliable, to make sure it's not your VM. You could try from an AZ in a different region to double check. This should cost you around 10c total. Next try from a ...


0

The fact that you reached a key rejection message proves out the transport piece. Hop over to the server via rdp and read your sshd or security logs to see what is happening. If I were to guess, I'd say it is either a reverse lookup taking forever, or some hiccup loading up the shell and env (not as likely but worth checking).


-1

I have been connecting to AWS all the time using wifi. Make sure you allow SSH traffic to your IP as part of your AWS security group associated with your EC2 instance. Use whatismyip.com to get what IP is your ISP service as established for you. I have seen this change sometimes. Also, make sure you use the .pem file for authentication.


-1

I know that ssh in cygwin would support keytabs. Follow these instructions for setting up kerberos and ssh in cygwin: http://computing.help.inf.ed.ac.uk/kerberos-cygwin Instead of the step 'kinit username' execute: kinit -kt /path/to/keytab username (Then ssh as normal.)


0

I was looking for many solutions for this when using Docker machine (both locale and on machines set up by system administrator). In my Putty everything was fine (I had UTF-8), I was using also other SSH client and had exact same problem. Running: mc -ac was solving the problem (but not completely) and I was looking for complete solution. After reading ...


1

Running mc this way (set locale to en) works for me: $ LC_ALL=en mc


0

just change keepalives setting on your putty



Top 50 recent answers are included