Tag Info  Hot answers tagged   I'm pretty sure that if you were
to telnet to port 22 you would see the Access Denied message.
Since the message of "Access Denied" is not a valid SSH protocol
handshake your ssh client generates a friendly error message on
the stage where the connection failed, the ssh key exchange,
which is the first stage of establishing an SSH connection.   I
think the real clue is here: %ASA-session-6-302014 You usually
see this on a Cisco ASA firewall, it looks like you are
triggering an event or rule in the Cisco firewall with your
traffic causing it to tear down the connection. If you have no
access to the Cisco ASA then give that log line to the person
who does and ask them to tell you why it stopped the ...   The
root cause of the issue wound up being a layer2 MTU mismatch,
which caused the openssl socket to time out part of the way
through the curl transaction. Full MTU-sized packets (i.e. 1500
byte IP payloads) failed because one side of the layer2 tunnel
would not allow them through