<html><body bgcolor="#FFFFFF"><div>Jim,</div><div>The problem is NAT, Network Adress Translation. Most home routers have to do this because you only get one public IP address. Your router then gives all of your local computers a private IP that can not be routed on the Internet. NAT does some fancy things with tcp/udp ports and tracks your connection. Essentially everything going out your router looks like it is coming directly from your router not from your PC. Then the return traffic needs to be translated by the router using its tracking tables. This means that connections can not be made to your internal PC from the Internet without some trickery like port forwarding.</div><div>You'll have to look up any further info. My thumbs are getting tired.</div><div><br class="webkit-block-placeholder"></div><div>Mike Robbery<br><br>Sent from my iPhone</div><div><br>On May 9, 2008, at 10:28, "Jim Hutchinson" <<a href="mailto:jim@ubuntu-rocks.org">jim@ubuntu-rocks.org</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><br><br><div class="gmail_quote">On Fri, May 9, 2008 at 7:22 AM, Kevin Fries <<a href="mailto:kfries@cctus.com"><a href="mailto:kfries@cctus.com">kfries@cctus.com</a></a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Both firewalls are Nat firewalls. So machine A might have an address of<br>
<a href="http://192.168.1.100" target="_blank">192.168.1.100</a> and machine B might have an address of <a href="http://192.168.0.2" target="_blank">192.168.0.2</a>. But<br>
they are not on the same segment and using addresses that are not able<br>
to be routed over the Internet. If either had a public, static IP, VNC<br>
alone could be a solution. But, without one side or the other having a<br>
public IP, neither side can initiate the communication to the other.<br></blockquote><div><br>Not being an expert in networking I may be missing something, but I'm unclear how you can have computers that don't have a public IP (assuming of course that they have internet access). They must be connected to a router (to get the lan IP) which is connected to a modem which connects to the internet and has an IP address. Are these boxes on a private lan with no external access? Or do they have a dynamic IP and that is the problem? If dynamic, why not try dyndsn? It works for me.<br>
<br>I'm sure you know what you are doing but something is missing in this picture - at least as I see it.<br><br>---- <br></div></div>Jim (Ubuntu geek extraordinaire)<br>----<br>Please avoid sending me Word or PowerPoint attachments.<br>
See <a href="http://www.gnu.org/philosophy/no-word-attachments.html"><a href="http://www.gnu.org/philosophy/no-word-attachments.html">http://www.gnu.org/philosophy/no-word-attachments.html</a></a>
</div></blockquote><blockquote type="cite"><div><span>-- </span><br><span>Ubuntu-us-co mailing list</span><br><span><a href="mailto:Ubuntu-us-co@lists.ubuntu.com">Ubuntu-us-co@lists.ubuntu.com</a></span><br><span>Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-us-co"><a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-us-co">https://lists.ubuntu.com/mailman/listinfo/ubuntu-us-co</a></a></span><br></div></blockquote></body></html>