The problem is that your pipe isn't encrypted.  VNC (with just the 3.x
password feature) isn't encrypting the traffic.

SSH and IPSec create a tunnel between client and server (work and home,
viewer and vnc daemon, etc).

Kevin can't create a SSH host on his Windows box to connect securely to.
He's been connecting to another box in his network and then utilizing it
to connect to his Windows box.


Kevin has several options:

1)  Install SSH
        http://www.cygwin.com/ or http://sshwindows.sourceforge.net/

2)  Use Remote Desktop for Windows
        It natively encrypts data although I recommend port forwarding
thru the firewall on a non-standard port.  In the RDC client, you can
connect to non-standard ports by just adding in :PORT.  So
home.domain.com:45678

3)  Use port forwarding.
        SSH from client to server but on the server, have that port
redirect to another system.  Normally you SSH to, say, port A on your
box to access a service running on port B (same box).  You could
redirect to another system and redirect your traffic.

4)  VPN (what I do).
        Tunnel all traffic to that subnet to another system.  In essence
you're "on that network".  XP handles the routing table very nicely here
- OSX not so well.  Linux is fine if you know your chains and tables.

/David.
 
David Sommers, Architect  |  Dialog Medical

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
Lieman
Sent: Monday, October 10, 2005 3:36 PM
To: [email protected]
Subject: Re: [Hardhats-members] Port forwarding wizardy wanted...

On 10/10/05, Kevin Toppenberg <[EMAIL PROTECTED]> wrote:
> Thanks everyone for the input.  I think I have decided it is too
> difficult to accomplish.  I was hoping that I was missing something
> obvious.
>
> Thanks
> Kevin
>

I need to draw a picture, let me show you how I do it...

My Workstation.  ( Linux, running vncviewer )
aa.bb.cc.dd
|
|
The Internet
|
|
xx.yy.zz.aa
Remote Office Linux Firewall
192.168.1.1
|
|
|
Windows PC. (192.168.92.150 )

What I do is fire up a  vncviewer, and use the -via command line
option to bounce it throught the remote office linux firewall. 
Basically, it sets up the tunnel between my workstation and the remote
office linux firewall, and then the vnc connection to the windows pc,
without the dual overhead.

$ vncviewer -via xx.yy.zz.aa 192.168.92.150

and viola.  I'm on the 150 box.


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads,
discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to