I think you missed Keith's point here, there is this funky thing
you can
do with VNC whereby the server (your customer) can say "let
jay.wooten.com
connect" and it'll search for your VNC client at jay.wooten.com and
set up
your connection. That way only you need the static IP address, your
customers just need to ping your VNC client to let you in.
Also, when did VPN come into the conversation, it was all about VNC
before!
HA! - Typo on my part sorry. Meant VNC.
think you missed Keith's point here, there is this funky thing you can
do with VNC whereby the server (your customer) can say "let
jay.wooten.com
connect" and it'll search for your VNC client at jay.wooten.com and
set up
your connection.
I got the point, but doing 'funky things' can sometimes complicate
situations. We are going for as drag-and-drop as possible.
Still, going back to our goal: no command line, drag and drop
install, a Mac-like experience, easy to maintain. So far,
REALSQLServer is the only database that has met those criteria for us
- and is the only database our users have been able to install and
set up with zero help.
We are also very interested in this technique of having VNC in a site
and having it allow a client connect without opening any ports and
automatically setting up the connection. That would be a huge time-
saver and really simplify working with the REALSQLServer at a client
location.
How do you set up the OS X built-in VNC server (our customer) to
search for/ping our VNC client? I would think that the built in
firewall in most routers would block that access. Also, without port
forwarding, how would the VNC client on this end know what computer
to access on the remote network?
- Jay
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
