2

We're using SSH with public key authentication.

The user can connect from one machine, but not from another machine on a different network.

He was previously able to connect.

When we run ssh with -vvv we can see that our server is reached, but the ssh connection times out before he can do anything:

debug1: connect to address 1.2.3.4 port 30000: Operation timed out

(I've disguised our ip address above)

We turned on password authentication, and he can't connect with that either, from one machine,

We figure there is some sort of auto-generated blacklist, but don't know where to check.

EDIT: Well, magically, when we left it alone for a few minutes and tried again, the connection worked...

1
  • 1
    Have you tried waiting a few minutes and trying again? :-) Jan 12, 2010 at 12:44

2 Answers 2

1

That sounds like there was no TCP connection, rather than an authentication failure. Have you tried looking for his traffic by running tcpdump on the server?

3
  • where do I find tcpdump? Jan 12, 2010 at 11:22
  • when the connection is not established to the server, you will not see anything in tcpdump on the server.
    – Christian
    Jan 12, 2010 at 11:30
  • Sure, but that's what you want to find out... if there's no packets getting to the server, you're wasting your time fiddling with ssh authentication when you should be figuring out what is going on with the network. apt-get install tcpdump should get you a tcpdump, and tcpdump -n 'port 22 and tcp[tcpflags] & (tcp-syn|tcp-fin) != 0' is the command you want to use to see if the TCP SYN packets are in fact arriving. Jan 13, 2010 at 6:22
1

try to telnet to your ssh server: telnet ssh-server 30000. When this does not work it is most likely that you have a firewall between the two networks. do you have a local firewall on the client or the server? is there a central firewall between the two networks?

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .