SC:
Heya. Not to nit-pick too much...but something of the whole
point of "server initiated connections" (ie, via the "Add New Client"
command on the server and a "Listen Mode" viewer) is so that there
need be no adjustments made at all to the firewall/router on the
VNC server side of the connection. Sure: you'd need to adjust the
*viewer* side (forwarding port 5500, rather than the usual 5900), but
you shouldn't need to touch the *server* side.
In general, whoever *receives* an Internet connection has
to worry about their firewall/router settings. If you're the one who
*initiates* the connection to an awaiting service (VNC, web page,
FTP, etc.) everything about the firewall/router, even with NAT'ing,
should be transparent. I wrote a white-paper about this once, about
a million years ago:
ftp://ftp.echogent.com/docs/FTP_and_Firewalls.pdf
Hope it helps!
cheers,
Scott
> you might want to try the listening vncviewer on the client and then 'Add New
> Client' on the vncserver. if the vncserver behind the firewall has a NAT'ed IP
> address i don't think you'll be able to connect though without portmapping the
> proper ports [5800/5900/5500] to the correct internal IP. sounds like this is
> something the firewall admins probably would not do for you so good luck.
>
> ]Greetings!
> ]
> ]The PC running the server is behind a firewall. Is there any way for the PC
> ]running the server behind the firewall to initiate a connection to a client
> ]viewer waiting to connect to it? This appears to be the only way I would be
> ]able to control this PC that's behind a firewall as the firewall adminstrators
> ]won't allow any other means.
> ]
> ]Thanks,
> ]
> ]Rob
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
