Dave:
Heya. That's sort of the point of the scan: a lot of VNC
users have setups similar to yours wherein the IP address that
a VNC Viewer should use to connect to your VNC Server is *not*
the same IP address as the PC on which the server is running.
Something along the way (either, as you say, at the ISP or in the
router) is performing "Network Address Translation" or NAT.
So while NAT is fundamental to getting mass-market home
networks working, it makes remote-access solutions more problematic.
So I coded up this scan to help VNC users know where to look when
it comes to getting their connections to work. The IP Address that
you see on that scan page is the IP address that the "real world"
sees your packets are coming from, and so is the address that
VNC Viewer users should use to connect to your server.
cheers,
Scott
On Sat, 16 Aug 2003, Dave Clark wrote:
> I did this and it reported the IP address generated by someone or
> something -- probably either my ISP or the DSL modem/router -- and NOT
> this machine.
>
> Still cannot connect to work machine from home.
>
> Have Black Ice firewall running on the home machine.
>
> Dave
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
