On Fri, Jul 3, 2009 at 6:34 PM, Lisa Kachold wrote: > Yes, Quest didn't block port 80 last I knew. > > But for best results, compile your own Apache2 (small)! > > > On Fri, Jul 3, 2009 at 5:43 PM, Jim March <1.jim.march@gmail.com> wrote: > >> Well it turns out my steenkin' Apache server crashed internally, I >> *think*. It basically stopped serving web pages on me without me >> realizing it...even if I went to the camera server's console and went >> to "localhost" in a web browser. >> >> So...mucho thanks all but it turns out Port80 works with Qwest :). >> >> Also, ZM itself seems to have an authentication system so I've turned >> that on, am rebooting and we'll see if that works. >> >> Now to get the dyndns stuff working. And I'm starting to wonder if >> the whole thing might be more stable in Jaunty versus Intrepid...? >> >> Thanks, >> >> Jim >> --------------------------------------------------- >> > > > > From outside, nmap (with three firewalls turned down) of 174.18.245.74: [root@chipmonk certs]# nmap -PN 174.18.245.74 Starting Nmap 4.76 ( http://nmap.org ) at 2009-07-03 18:40 MST [root@chipmonk certs]# nmap -PN 174.18.245.74 Starting Nmap 4.76 ( http://nmap.org ) at 2009-07-03 18:42 MST All 1000 scanned ports on 174-18-245-74.tcso.qwest.net (174.18.245.74) are filtered Nmap done: 1 IP address (1 host up) scanned in 207.09 seconds [root@chipmonk certs]# telnet 174.18.245.74 80 Trying 174.18.245.74... ^C [root@chipmonk certs]# Either you have posted a bogus IP address, or you are not actually allowing any inbound ports. I should be able to get something here. If they say they are filtered, then you are not allowing the world to access. -- (503)754-4452 wiki.obnosis.com scientology.obnosis.com