1. Create a service definition for the port used by VNC. 2. Create a host definition for the machine on the Internal network that is running the VNC software. 3. Create a DNAT rule using the host and service defined in the previous two steps, which maps the service from the host to the External ASL interface.
Where VNC-Port is the service definition you previously created, and PC-host is the definition for your internal host running the VNC software.
I hope this helps.
As a general bit of advice, I would suggest you reconsider doing this. By mapping the VNC port to the External interface you are creating an unnessessary security vulnerability. The preferred approach would be to use PPTP, and connect via a Roadwarrior VPN from the outside, and then run your VNC remote control connection inside the VPN tunnel. The same applies if you use the Microsoft Remote Desktop Client (into a WinXP or Win2K3 machine) from an external location.
Running desktop remote control naked (i.e. not inside an encrypted tunnel) over the public Internet is not such a good idea.
I understand the its not good idea.... but I'm running a real encoder I have to have access to re-start it asap..... some times I don't have time, or the ablity to conn via VPN :-)
on my home linux box I use SSH.... I understand what you are saying.... but I still need this ablity.... its also on a low profile com :-)
