Steve:
Heya. You're describing a very common use of VNC, and you
should be able to find a lot of existing documentation about getting
the router's port-forwarding setup, and combining it with a dynamic-DNS
client to achieve what you want to do. For example, one user's experience
is recounted here:
http://faq.gotomyvnc.com/fom-serve/cache/127.html
An overall easier approach, however, uses some modified VNC
applications to achieve a "single-click" solution. In this approach,
the person needing support (e.g., your father) would fire-up a
zero-configuration application that, once running, allowed you (and
only you) to remote-access his PC. The two most popular single-click
solutions are UltraVNC-SC and echoWinVNC:
http://www.uvnc.com/addons/singleclick.html
http://forum.ultravnc.net/viewtopic.php?t=4068
At the risk of being self-promotional, I think echoWinVNC
is easier to work with, but they're both pretty solid solutions.
hope that helps,
Scott
I have used VNC for a while to help my father with his PC.
He has recently upgraded his machine to XP and at the same time to
ADSL (he previously had SE and a dial-up connection)
He has installed VNC (version 3.3.7). When he hovers over the icon
the TCP/IP address displayed is 192.168.1.3, which is (by my
understanding) reserved for LANs.
When I try to connect to this IP address the client times out.
He is running the XP filewall but getting him to turn this off
doesn't make any difference. He's also loaded Bull Guard and I
haven't tried turning that off.
It seems to me that this isn't a 'valid' IP address and that I won't
ever be able to connect to it.
Any thoughts or suggestions welcome and appreciated, thanks.
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
