Re: error message: "channel 3: open failed: administratively prohibited: bla bla"
From: Richard E. Silverman (res_at_qoxp.net)
Date: 01/18/05
- Next message: chekov_1: "openssh on windows 2003 ends with "exit status 255" ==> solution"
- Previous message: Jonathan: "Re: error message: "channel 3: open failed: administratively prohibited: bla bla""
- In reply to: jonathan.buhacoff_at_gmail.com: "error message: "channel 3: open failed: administratively prohibited: bla bla""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 18 Jan 2005 02:47:25 -0500
> Anyone seen this message before?
> I'm at home, A, and I'm making a tunnel through B to C:
> A% ssh B -L 2000:C:2000
>
> And that works fine
Yes, because a local forwarding does not actually do anything on the
remote side until use.
> but then when I'm at A and I do this:
> A% telnet localhost 2000
>
> Then on B's console I see the error message above:
> channel 3: open failed: administratively prohibited: bla bla
The message is misleading; OpenSSH will say this if the remote TCP
connection fails to open for any number of reasons which do not have to do
with SSH administration -- including, for example, if the target socket is
closed. Have you verified that it's open, i.e. that C:2000 will accept
the connection from B?
-- Richard Silverman res@qoxp.net
- Next message: chekov_1: "openssh on windows 2003 ends with "exit status 255" ==> solution"
- Previous message: Jonathan: "Re: error message: "channel 3: open failed: administratively prohibited: bla bla""
- In reply to: jonathan.buhacoff_at_gmail.com: "error message: "channel 3: open failed: administratively prohibited: bla bla""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]