Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Our lab's compute cluster has a two-interface 'gateway' machine which we use to access the cluster nodes. Call this Normally I access this machine from my laptop, like this:


I have set up a public key in .ssh/ on laptop, and copied that to .ssh/authorized_keys on gateway1. Ordinarily this works fine.

Today I am using a public access point rather than my usual work connection. When I do


I get the response:

Permission denied (publickey,gssapi-with-mic).

Apparently it won't accept my id_rsa credentials (Problem 1) and I am not prompted for a password (Problem 2) even though ordinarily when I log in from a previously unknown host I am prompted for a password.

I am still able to ssh to gateway1 from another machine (call it without problem, either with password or (after setting up the relevant id_rsa* files) with publickey authentication. I can also log into otherhost itself using publickey credentials from laptop, so I know there's nothing fundamentally broken about laptop's ssh setup.

Finally, even when I delete my public key form .ssh/authorized_keys on gateway1, I still get the same "Permission denied" message and no password prompt.

So I guess my question is, what can cause gateway1 to reject my publickey credentials from my laptop, and prevent password login, but not from another host? I have confirmed that the on laptop and authorized_keys on gateway1 are in sync.

EDIT: I haven't been able to duplicate the problem since I originally posted, because it only happened when I was connected to a particular wireless access point (not belonging to me or to my lab). I still don't know how this could occur.

share|improve this question

Someone might be using the AllowUsers directive in the configuration of the server, or you might be using the wrong version of the SSH protocol.

Try adding -v (or two of them) to step up the verbosity; you might find something more helpful than simply denied.

Similarly, you can initiate ssh without a key exchange, rather than removing it on the server's authorized keys list. Read about it on the man page for ssh.

share|improve this answer

Are you running debian? Might this be caused by blacklisted SSH keys?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.