hmm...
So you just setup a mapping from the WAN side to the LAN side on the NAT
device?
There is something similar setup to get to our email server, basically
"punching a hole" in the NAT device.
So then when you connect with the VNCViewer, would you specify the port
that you opened up on the NAT device?
Meaning, if I want to be able to host 10 simultaneous VNC sessions through
the NAT, I would need to open up 10 static maps to the internal LAN?
-Rod Strumbel
-----Original Message-----
From: Lee Allen [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 10, 2001 6:58 PM
To: [EMAIL PROTECTED]
Subject: Re: VNC as a VPN ?
Rod Strumbel <[EMAIL PROTECTED]> wrote:
> Have been trying (in vane) for the last couple weeks to configure
> VNC to work as a VPN to my internal LAN.
>
> My LAN is behind an Instant Internet 400 box (NAT device).
>
> I can vnc all over INSIDE the LAN, but am unable to access the LAN
> devices from outside the II-box because of the NAT mappings.
>
> I have users on all sorts of OS (Win95/98/2k/ME, Linux-RH/Mdk/SuSE) and
> accessing
> the net through all sorts of methods (ISDN, Dialup 56k, DSL, Cable etc...)
> Primarily the users need to access their own onsite workstations (which in
> turn
> would access the servers).
>
> I need to implement a solution ASAP, as one of my users is about to
> head out on maternity leave and needs remote access now.
>
> I am also researching VPN hardware solutions from WatchGuard and Cisco,
> but they are pretty spendy.
>
> Anyone ever made this configuration work? And if so, how?
I am VNC-ing into systems on 3 different LANs that are behind NAT firewalls.
On two of the firewalls (1 is LRP and 1 is Netgear) I have set up
port-forwarding rules on the firewall. Very simple.
On the third LAN we have a commercial hardware VPN server. Altiga, which
has been aquired by Cisco. So we load the VPN client software on the client
(viewer) PCs, which makes them 'virtually' part of the LAN.
There are less expensive hardware VPN servers. You can also build one
yourself, using Linux and FreeSWan (IPSec) or just SSH.
I hope you understand you have a networking challenge here, not a VNC issue.
-Lee Allen
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
