I'm using the command:
ssh -fNC -l $USER -i /home/$USER/.ssh/id_rsa -R 1234:localhost:22 $HOST
This sets up a tunnel back to my house in order to bypass a draconian firewall to allow me to ssh back into my server. Well, everything connects just fine, but when I try to ssh into the remote on port 1234, it pauses, and then comes back with connection refused.
The exact same script works just fine on my slackware box... yes, I removed the line from hosts.deny... I just can't figure it out.
Funny, it works some times.... but not others. Seemingly random....
It might be your draconian firewall that's killing the idle connection. But that doesn't seem right if it worked just fine in slackware...
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
the script was a cron job with an if statement to check to see if it was running. It runs every ten minutes in cron. I wrote an echo into the file so I could log its actions, and it is indeed running on schedule, and establishes a connection when it needs to. Funny that it only sometimes gives me the connection refused error even when I check on the remote machine that the connection is there. It just doesn't make any sense.
I don't know what the big difference between slack and arch would be to cause that problem.