I agree: if the end-user has administrative access to their router, setting up a port-forward is pretty easy, and getting easier
(Pure Network's "PortMagic" tool skips the whole router UI altogether).
Combining that with a dynamic-DNS client is a good solution for many
situations.
However...when the target VNC server is online via a broadband connection at a hotel, airport, Starbucks, customer's site, etc., configuring the port-forwarding is a non-starter. In such cases, I think a relay-sever approach like EchoVNC's is the easiest solution. All of the Internet traffic appears to be "outgoing", so no router configuration is needed, and the relay-server login names provide the same function as a dynamic-DNS client.
cheers, Scott
Configuring a router normally involves creating a port-forward for port 5900 to the computer's local IP address. The interfaces provided for setting this up on most routers are incredibly trivial.
Is there some other factor that you think makes it difficult?
Regards,
Wez @ RealVNC Ltd.
-----Original Message----- From: Scott C. Best [mailto:[EMAIL PROTECTED] Sent: 27 April 2005 17:46 To: [email protected] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: newbie question
Wez:
Heya. I need to politely disagree: if Scott's wife was on a network behind an unconfigured firewall/router, your suggestion doesn't fully address his needs -- if she were using a dialup modem only, of course it would. But if not, then the unknown firewall/router issue is a much more substantial hurdle (IMO) that VNC Personal Edition doesn't yet address.
<snip> _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
