Re: Help with VNC Please....

I don't use VNC through a SSH tunnel but I have used Remote Desktop through a SSH tunnel in the past. In my case I used PuTTY. Here is an example of that. It may be of some help. Note in the example shown the computer name maps to a local LAN address on my home LAN, ie. Ashtabula = 192.168.11.11 and Norman = 192.168.11.12 for example.

http://theillustratednetwork.mvps.org/Ssh/RemoteDesktopSSH.html#Install_and_configure_PuTTY
http://theillustratednetwork.mvps.org/Ssh/RemoteDesktopSSH.html#SSH_Tunneling_the_Remote_Desktop_session

Since your using the SSH.com client have you tried their tech support?

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

<amerar@xxxxxxx> wrote in message news:1158943453.327721.71090@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

That was a good example. However, one of two things happen:

First, either I get the same error message as before OR the vncview.exe
process starts but I never see my remote computer? The process is
running as I see it in the task manager and all......

Where it asks for my IP in the tunnel setup, is that going to be my
internal IP (192.168.x.x) since I'm connecting via SSH, or is that my
public IP?

Additionally, do I need to forward any ports on my router, like 5900 or
5901??

Thanks!



Sooner Al [MVP] wrote:
Have you seen this from SSH?

http://www.ssh.com/documents/50/VNC_CompatibilityNote.pdf

Here is an example of doing the same thing but using PuTTY...

http://www.dslreports.com/faq/11544

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

<amerar@xxxxxxx> wrote in message
news:1158935850.530097.145540@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi Everyone,
>
> I know this is probably basic stuff, but I'll need someone to walk me
> though this. I installed VNC and I'm trying to acess my box through SSH
> at home from work and I keep getting this error message: "Connection
> Closed Unexpectedly".
>
> So, here is my config:
>
> Server:
> OS: Windows XP
> Server is running on Windows box and firewall is enabled.
>
> Client:
> OS: Windows XP
> SSH Client: Secure Shell (from www.ssh.com)
> Tunnel Config:
> Comp Name: Monster Listen Port: 5900 Host: 192.168.1.100
> Destination Port: 5900
> Comp Name: LocalHost Listen Port: 5901 Host: 127.0.0.1 Desination
> Port: 5901
>
> Why am I getting that message? Are my tunnels not set up correctly?
> I try to connect using: localhost:1
>
> Thanks for any help and walking me through the setup.
>


.

Relevant Pages

  • Re: What is The SSH?
    ... Building and Using SSH Tunnels ... What is an SSH tunnel? ... how to use it to make a connection to a server. ... You will need a working SSH client and server installation to build and test ...
    (microsoft.public.windows.server.networking)
  • Re: Prot Forwarding
    ... Personally I use a Secure Shell tunnel to access multiple XP Pro boxes ... don't need to tunnel UDP ports. ... SSH does not support UDP through the tunnel. ... automatically launch a Remote Desktop session when the SSH tunnel is ...
    (microsoft.public.windowsxp.network_web)
  • Re: Remote Access to multiple PCs on a network
    ... Actually i want my users can connect ONLY through tunnel. ... through a Linksys router and T1 with 10 static IP's. ... individual PC behind the router with Remote Desktop? ... Or you could setup a VPN or SSH tunnel and only open one hole on the router ...
    (microsoft.public.windowsxp.work_remotely)
  • RE: HOWTO Ping LAN???
    ... SSH to the box, and tunnel to other internal machines ... > network is by tunneling. ...
    (freebsd-questions)
  • SSH TCP forwarding: works with v1, not with v2 ssh
    ... that they're setting up the tunnels with no problem, ... I can get to the work ssh daemon: ... debug1: Connections to remote port 65002 forwarded to local address palimpsest:22 ... something answers (if I get "connection refused" there's no listener); ...
    (FreeBSD-Security)