Skip to main content
added 114 characters in body
Source Link
barlop
  • 277
  • 3
  • 10

I saw this error on cygwin and this should be true of linux too and worked for me. In my case i'd done ssh -ND *:1234 [email protected] and when I connected a browser to that comp-socks server , it browsed, but on the comp where I ran that ssh command I got that error appearing at the console with each request - for one site at least, though the browser retrieved it through the proxy or seemed to, at least to the extent that I saw the main age. But making this change got rid of the failed message

http://linuxindetails.wordpress.com/2010/02/18/channel-3-open-failed-administratively-prohibited-open-failed/

While trying to do some SSH tunneling, here is the error I got : channel 3: open failed: administratively prohibited: open failed To avoid this kind of error, have a look at the SSH daemon configuration file : /etc/ssh/sshd_config Add possibly the following line : root@remote-server:~# echo “PermitTunnel yes” >> /etc/ssh/sshd_config Then, restart your sshd server : root@remote-server:~# service ssh restart or root@remote-server:~# /etc/init.d/ssh restart 

I saw this error on cygwin and this should be true of linux too and worked for me. In my case i'd done ssh -ND *:1234 [email protected] and when I connected a browser to that comp-socks server , it browsed, but on the comp where I ran that ssh command I got that error appearing at the console with each request - for one site at least, though the browser retrieved it through the proxy.

http://linuxindetails.wordpress.com/2010/02/18/channel-3-open-failed-administratively-prohibited-open-failed/

While trying to do some SSH tunneling, here is the error I got : channel 3: open failed: administratively prohibited: open failed To avoid this kind of error, have a look at the SSH daemon configuration file : /etc/ssh/sshd_config Add possibly the following line : root@remote-server:~# echo “PermitTunnel yes” >> /etc/ssh/sshd_config Then, restart your sshd server : root@remote-server:~# service ssh restart or root@remote-server:~# /etc/init.d/ssh restart 

I saw this error on cygwin and this should be true of linux too and worked for me. In my case i'd done ssh -ND *:1234 [email protected] and when I connected a browser to that comp-socks server , it browsed, but on the comp where I ran that ssh command I got that error appearing at the console with each request - for one site at least, though the browser retrieved it through the proxy or seemed to, at least to the extent that I saw the main age. But making this change got rid of the failed message

http://linuxindetails.wordpress.com/2010/02/18/channel-3-open-failed-administratively-prohibited-open-failed/

While trying to do some SSH tunneling, here is the error I got : channel 3: open failed: administratively prohibited: open failed To avoid this kind of error, have a look at the SSH daemon configuration file : /etc/ssh/sshd_config Add possibly the following line : root@remote-server:~# echo “PermitTunnel yes” >> /etc/ssh/sshd_config Then, restart your sshd server : root@remote-server:~# service ssh restart or root@remote-server:~# /etc/init.d/ssh restart 
Source Link
barlop
  • 277
  • 3
  • 10

I saw this error on cygwin and this should be true of linux too and worked for me. In my case i'd done ssh -ND *:1234 [email protected] and when I connected a browser to that comp-socks server , it browsed, but on the comp where I ran that ssh command I got that error appearing at the console with each request - for one site at least, though the browser retrieved it through the proxy.

http://linuxindetails.wordpress.com/2010/02/18/channel-3-open-failed-administratively-prohibited-open-failed/

While trying to do some SSH tunneling, here is the error I got : channel 3: open failed: administratively prohibited: open failed To avoid this kind of error, have a look at the SSH daemon configuration file : /etc/ssh/sshd_config Add possibly the following line : root@remote-server:~# echo “PermitTunnel yes” >> /etc/ssh/sshd_config Then, restart your sshd server : root@remote-server:~# service ssh restart or root@remote-server:~# /etc/init.d/ssh restart