Re: VNC Through WinSSHD

From: Wilfried Hennings (nospam_at_fz-juelich.de)
Date: 08/27/03 

Date: Wed, 27 Aug 2003 11:08:28 +0200

bobsmith10@hotmail.com (bob) wrote:

> >
> > So you don't know which port it uses? But you NEED to know the port
> > number for establishing the tunnel.
>
> Its easily changed to 5900 (or anything else)... np
>
> > (means local vnc viewer should connect to localhost, display x)
>
> How can I determine what the localhost address and display info is?
> Is it listed within VNC or WinSSHD program's?

When starting the local vnc viewer, you must enter the "remote" host
name or IP address and the screen number. However as you want to tunnel
it, you must connect to the local port which is supplied by tunnelier.
So for host name use "localhost" or "127.0.0.1" literally.
The local port number which you must specify in tunnelier is the result
of adding 5900 + the local screen number you set in the local vnc
viewer.

> > Destination host: remote.host
> > (insert correct name)
>
> Is this the same as one above? or can it just be (exactly) "localhost"
> per screenshop via bitvise?

For the remote end of the tunnel you specify either the real name or the
IP address of the remote host.
Maybe you also have to specify the username with which you are allowed
to log in to the remote host's ssh server (in the format
user@remotehost).

>
> > Dest. port: 590y
> > (for this to work, you must ensure that the remote VNC server serves diplay y)
>
> Again... how can I determine what the correct info is?

The correct info for the dest. port is the result of adding 5900 + the
screen number of the vnc server running on the remote host.

Example:

local vnc viewer connects to "localhost" and screen number (say) 1

common address for local vnc viewer and local end of tunnel is
"localhost" port 5901

tunnel connects "localhost:5901" to (say) "xyz.uvw.opq:5900"

common address for remote vnc server and remote end of tunnel is
"xyz.uvw.opq" port 5900

remote vnc server connects to "localhost" and screen number 0

Note that each the vnc server and the vnc viewer connect to "localhost"
because you want each to connect to the end of the tunnel which is local
to it. 

--
email me: change "nospam" to "w.hennings"
Dipl.-Ing.(=M.Sc.Eng.) Wilfried Hennings c./o.
Forschungszentrum (Research Center) Juelich GmbH, MUT
<http://www.fz-juelich.de/mut/index.php?index=3>
All opinions mentioned are strictly my own, not my employer's.

Relevant Pages

  • Re: Looking for remote access software
    ... > port forward 3389 from the router to the host you wish to access. ... Remote sessions are NOT the same thing as remote control. ... Try out VNC first. ...
    (comp.security.firewalls)
  • Re: [SLE] Remote desktop?!? [SOLVED Again!]
    ... > vnc module to XF86Config as suggested in readme file. ... I would not select "Open firewall port", ... Now on XP connect with vncviewer to Linux as usual but add ":1" to the ... Then you need to open an encrypted tunnel from you XP to Linux that is ...
    (SuSE)
  • Tunnel netbios over ssh
    ... You've got one end of the tunnel set up - but what about ... NetBIOS ports. ... Out of the box SSH talks on port 22 - you need to get the ... remote machine to talk on port 22 as well. ...
    (microsoft.public.windowsxp.network_web)
  • Re: accessing a system across the internet
    ... I have the vnc listener and software setup ... The remote machine may be behind a firewall or two. ... Specified Custom Port Probe' button. ...
    (microsoft.public.windows.server.networking)
  • Re: PLINK and/or PuTTY -- Logon to Linux with no Privileges
    ... port 443 so it would look like HTTPS to a firewall (is that right ... We've tried just regular VNC, with no luck, then tried it on port 80, ... and would rather me run a tunnel than pay to have anything ...
    (comp.security.ssh)