Hot answers tagged tcp
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. Other people seeing this error may not have an MTU mismatch, but it could ...
You have probably a legion of masquaraded/NAT-ted connections, too. Linux handles them in a static hash table, which can overflow. After that, you will get exactly this mystic problem. A command cat /proc/sys/net/netfilter/nf_conntrack_max says you, what is the upper limit of this hash map. Multiple this with 13 and set it with the command echo ...
Only top voted, non community-wiki answers of a minimum length are eligible