On Sun, Oct 15, 2006 at 09:08:56AM -0400, Debian user wrote:
> 
> This the syntax that I had to use to connect to the ssh tunnel server:
> 
> [EMAIL PROTECTED]:~$ ssh [EMAIL PROTECTED] -L 9000:news.astraweb.com:119
> Password:
> Last login: Sun Oct 15 05:44:47 2006 from cblmdm72-240-18
> 
> Cotse.Net SSH Tunnel Server (tunnel1.cotse.net)
> 
> This service listens on ports 22, 2222, 80, and 443 for connections.
> 
> Do NOT close this window or you will terminate the tunnels
> 
> Type password and hit enter to change your password.
> (passwords must be at least six characters long).
> 
> (CTRL-C to terminate connection)
> 
> Which shows that I am connected to the ssh tunnel server
> 
> Telnet still fails:
> 
> [EMAIL PROTECTED]:~$ telnet
> telnet> open
> (to) localhost
> Trying 127.0.0.1...
> telnet: Unable to connect to remote host: Connection refused
> telnet> open localhost:9000
> telnet: could not resolve localhost:9000/telnet: Name or service not
> known
> telnet>


You need to do:

telnet> open localhost 9000

> > > I cannot telnet to localhost either or 127.0.0.1 and that would tend to
> > > indicate that system is not allowing incoming connections which we know
> > > is not possible as I can send and receive e-mail and browse the web.
> > 
> > You mean, you receive email over the samme tunnel as you use to read news?
> > I am not sure that I follow.
> 
> I am sorry, that was confusing. What I meant to write was: I can connect
> to the tunnel server for browsing the web and so on. I open two seperate
> tunnels, one for web browsing and one for nntp service.
> 
> I could channel e-mail via the ssh tunnel connection if I wanted too,
> but I do not.

Ok. You should be able to telnet to any of your locally forwarded ports and see
the prompt of the server that you are tunneling to.

-- 
Søren O.

"Oh, bother" said the Borg, "we've assimilated Pooh".

Reply via email to