What is this???

Captain Code

Captain Code

Moderator
Staff member
Mod
I have port forwarding from my work machine to my home SSH server over an SSH tunnel.

This has worked fine before, but now I am getting this strange error in the tunneling program:

to mail.macosx.com:110.

Reason: Opening the channel was administratively prohibited.
Server error details:
bla bla

The "bla bla" part seems really strange and makes me wonder what is going on here..

Has anyone come across this before?
 
Sounds like /etc/sshd_config may be set to disallow port forwarding.

Sometimes, this is in /etc/ssh/sshd_config

WHY must we use underscores in unix... we know better....

anyway,

could be a software update disabled port forwarding in an effort to tighten up security.

If you can't figure it out, post more details (complete error message, any useful console output on either computer, and of course, sshd config files).

Oh, and before I forget, try adding several -v options to your ssh client:
$ ssh -v -v -v bla bla bla
 
Well, I know it's not that port forwarding isn't enabled, because I use it all the time. It's just that sometimes it'll work great, and then it won't and in the log of the tunneling software I'm using it'll have that error. I'm not sure if it's sshd that is giving the error or if it's the software on my work computer called Entunnel.

I know it's not a config problem because it will just start doing this and then start working normally again.

It *could* have something to do with my ISP and this might be a message sshd gives if it can't connect. I have been having a few strange things happen with my ISP where the connection(DSL) will just not work, and drops all packets, and then a minute later will work again.

If this is happening, the ssh server might be throwing this error, but I don't know for sure.

I thought it was strange to see an error of "bla bla bla" :confused:
 
Wait, it actually says "bla bla bla" ?!

Grep the source code of the ssh client you use, and see what you can come up with. And, remember, try using verbose options with your ssh client - the error may be a bit more informative if you do.
 
Yeah, it actually says "bla bla bla" :confused:

Unfortunatly I don't have the source code of the client because it's a shareware windoze application.

The sshd is what comes with OSX 10.1.5(which I really should update!), which I think is OpenSSH but I don't know what version.
 
You must log in or register to reply here.
Back
Top