On Friday, February 11, 2011 08:13:58 pm T L wrote: > I think that there is a confusion between a public address and a static > one. Dynamic DNS to the rescue? > > Thomas Nope, that doesn't seem to be the confusion here. His ISP has him behind NAT, so he doesn't have a public IP that can be connected to. Take my situation: firewall external IP address is assigned by my DSL router via DHCP as 192.168.254.2 The DSL router gets a "public" IP of 192.168.254.254 from the DSLAM. Something upstream does NAT. The IP that I see on the other end of my link is 74.38.80.1. Hitting a website like whatismyip.com gives me a random IP in 74.38.80.0/24, but I can't connect back to that IP from a remote host, stuff just dies at whatever is doing NAT. -- Thanks, Josh Paetzel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: This is a digitally signed message part. URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20110214/ae255b94/attachment.pgp>