Hi Miroslav,
> > So, this is the problem. The telnet hangs after printing:
> > $ telnet 127.0.0.1 5911
> > Trying 127.0.0.1...
> > Connected to localhost.localdomain (127.0.0.1).
> > Escape character is '^]'.
>
> What is your SSH client? With Mindterm I get exactly the same behaviour.
But
> if
Hi, Sergey.
> So, this is the problem. The telnet hangs after printing:
> $ telnet 127.0.0.1 5911
> Trying 127.0.0.1...
> Connected to localhost.localdomain (127.0.0.1).
> Escape character is '^]'.
What is your SSH client? With Mindterm I get exactly the same behaviour. But
if I connect to t
Privet, Miro!
> OK, let's try the next step. When logged
> through ssh on your mysshd machine, try
> "telnet 127.0.0.1 5911" and see if you
> get a string like "RFB 003.003"
Thank you very much!
So, this is the problem. The telnet hangs after printing:
$ telnet 127.0.0.1 5911
Trying 1
Privet, Serjoza,
> This is the output of the "netstat -an |grep 5911 (I use 11-th screen)
> tcp0 0 127.0.0.1:5911 0.0.0.0:*
> LISTEN
> tcp0 0 127.0.0.1:5911 127.0.0.1:2793
> ESTABLISHED
> tcp0 0 127.0.0.1:279
Jonathan,
> >(at least OpenSSH), then sshd listens only on 127.0.0.1:portnumber.
>
> Fix this using the -g parameter (listen to everywhere, not just
> localhost).
"-g" is a ssh, not sshd parameter. That means if you use "ssh -g -L", then
ssh will listen on 0.0.0.0:port, otherwise (without -
Hi Miroslav,
> > I waited several hours, but nothing happened. Is there
> > anybody succeded in
> > connecting to VNC server through the tunnel, organized by
> > "ssh -R" option?
>
> It works. But my experience is that when "ssh -R" is used with sshd on linux
> (at least OpenSSH), then sshd li
> > I waited several hours, but nothing happened. Is there
>> anybody succeded in
>> connecting to VNC server through the tunnel, organized by
>> "ssh -R" option?
>
>It works. But my experience is that when "ssh -R" is used with sshd on linux
>(at least OpenSSH), then sshd listens only on 127.
Hello, Sergey.
> I waited several hours, but nothing happened. Is there
> anybody succeded in
> connecting to VNC server through the tunnel, organized by
> "ssh -R" option?
It works. But my experience is that when "ssh -R" is used with sshd on linux
(at least OpenSSH), then sshd listens only o
> > > That might be a DNS-reverse-lookup problem. Leave it for a few
> > > minutes and see if it completes the connection.
> >
> >Hi Jonatan, will you please instruct me in details what should I do
> >and what may be the source of such DNS-reverse-lookup check which
> >failed, - VNC server, vie
> > That might be a DNS-reverse-lookup problem. Leave it for a few
> > minutes and see if it completes the connection.
>
>Hi Jonatan, will you please instruct me in details what should I do
>and what may be the source of such DNS-reverse-lookup check which
>failed, - VNC server, viewer or ssh
On Tue, 4 Dec 2001 23:28:48 +
Jonathan Morton <[EMAIL PROTECTED]> wrote:
>
> That might be a DNS-reverse-lookup problem. Leave it for a few
> minutes and see if it completes the connection.
>
Hi Jonatan, will you please instruct me in details what should I do and what may be
the source o
>Thank you, I tried now to connect at linux server from another port, but
>with the same result.
>The interesting thing is that while 'ssh -R' tunnel is established vnc
>viewer does not return any messages, but when I close the tunnel it
>immediatesy tell to the consol I started it from that VNC s
m that VNC server closed
connection.
Sergey.
- Original Message -
From: "SI Reasoning" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 04, 2001 4:28 PM
Subject: Re: ssh -R to hear ports outside the firewall
> if this is a linux machine try -R
if this is a linux machine try -R 5901:0.0.0.0:5900
the reason being that port 0 is always taken by
Xwindows in linux.
--- Sergey Ivanov <[EMAIL PROTECTED]>
wrote:
> Hi all,
> I easily connect from inside the firewall the
> machines outside the
> firewall with command
> ssh -L 5900::590
14 matches
Mail list logo
