At 12.48 2005.05.05 -0700, you wrote:
>You have to have an IP, period.  But typically you get a dynamic IP
>that changes every so often or when you shut your modem down for a
>certain length of time.  So to run VNC you don't use an IP, you use a
>domain name that reflects your current IP. 
>
>Try no-ip.com or dyndns.org for the domain name pointer, then get the
>utility from them to update your IP on a timely basis.  Mine checks
>every ten minutes or so, even though my IP stays the same for months. 
>Then I vnc into my domain name.  Works great.

I know for sure that there are some providers that put you on the Net
as if you were in a LAN and don't make you control port-forwarding.
The result is that you have a public IP (as shown by www.whatismyip.com
and equivalent methods) but it's totally useless: you can't listen nor
accept connections, i.e. you can run any server-like software on your
PC.

If Verizon is one of these providers (we in Italy have Fastweb of this
breed, for example) then the only way he can use VNC is my the inverse
method I explained in another post.
 
 
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist