Differences between version 19 and predecessor to the previous major change of SSHErrors.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 19 | Last edited on Friday, December 16, 2005 1:58:26 am | by JoachimSchiele | Revert |
| Older page: | version 18 | Last edited on Friday, October 7, 2005 3:42:25 am | by AshleyWard | Revert |
@@ -73,11 +73,11 @@
If you get an error similar to <tt>Permission denied (publickey).</tt> you probably have not put your public key into the authorized_keys file in ~/.ssh or else you may have corrupted that file.
!!! <tt>channel ''n'': open failed: administratively prohibited: open failed</tt>
-Despite this error message, this just means it wasn't able to open a port forward. Generally this is because the address you have set for port forwarding is wrong, or the port that you are pointing to is incorrect. Check your -L or -R options for accuracy. This
is also the message you'll get if your slave SSH server is running port filtering software like "Little Snitch" or have a firewall setup on the slave side.
+Despite this error message, this just means it wasn't able to open a port forward. Generally this is because the address you have set for port forwarding is wrong, or the port that you are pointing to is incorrect. Check your -L or -R options for accuracy. For example this command will bring up the error mentioned above caused by a wrong usage: ssh -L 9999:<b>user</b>@host:22, the problem is that you are not allowed to specify a user here. On the other hand this
is also the message you'll get if your slave SSH server is running port filtering software like "Little Snitch" or have a firewall setup on the slave side.
This can also be if the server you are connecting to has AllowTcpForwarding set to no in its sshd_config file.
----
Part of CategorySecurity, CategoryNetworking, CategoryErrors
