On 8/5/07, Sean Kamath <[EMAIL PROTECTED]> wrote: > > > Open a port on *your* router, then forward that port to your machine > you use VNC to control their machines. Have them start vnc and > connect to a "listening client" and point to your machine (if > necessary, a dyndns hostname). > > Then you never need to configure their routers/nat/firewall, and it > always "just works". > > For a while, I dropped shortcuts or whatever they're called on PCs > (pifs?), that did winvnc4.exe -connect "my ipaddr", labeled them "get > help" and would tell my mother "click on get help". :-)
This sounds like exactly what I would prefer. I've never used the listening client before so I figured I'd give it a shot. I just tried running the listening client on my workstation and ran "winvnc4.exe -connect <ipaddr>" on the machine I wanted to control but I keep getting an error "Unable to locate existing VNC Server". From what I've read the viewer listens on port 5500 so I have that opened in my firewall, and when I have the viewer running in listen mode I can telnet to that port so I know the firewall is set up properly. Do I also need 5900 opened up as well or is there something else I'm missing? -Bruce _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
