What this is all about:

I'm attempting to get a fileserver set up at my home for remote file retrieval. I'd like to have the ability to dump stuff on my server at home and pick it back up whenever I need to, as well as set up a development webserver. Here's the list of stuff I've got, and my particular network setup:

The first step I took was a clean install of OSX on the iMac. The Barricade handles all of the PPPoE duties, so I connect to it via DHCP. I then installed a copy of DNSupdate, and puzzled through the setup routine. Essentially, what you need to do is set up the client and the hostname. You'll want to find a screen with two checked boxes reading "OK" when you're done. It runs as a daemon in the background on boot, so you don't have to start it each time you reboot your Mac.

Next, I turned Personal File Sharing and Personal Web Serving on in OSX (Preferences -> Sharing -> Services Tab) and then turned the Firewall on (Preferences -> Sharing -> Firewall Tab). This starts up Apache and your AFP sharing, so that you can see your personal webserver on the network: open Safari and enter "http://127.0.0.1/~yourusername" in the URL bar. Theoretically, you should see the Apache install screen, or whatever page you've replaced it with.

I then signed up for an account with dyndns. Go to their site, choose "dynamic DNS," and create an account. Free and easy. Then, add a host. What you're doing is creating the name (the Hostname) you'll point your webserver to in your browser. Use the pulldown menu to choose a free domain (e.g. dyndns.org), and make sure your computer's IP address is present. Check Enable Wildcard, and ignore Mail Exchanger (I'm not covering that here.) Then click Add Host.

I configured the Barricade, at first, to open ports to the iMac by specifying the IP address. I opened port 80 for web serving and ports 548 and 427 for Personal File Sharing. Web sharing worked internally, resolving lockardugan.dyndns.org and showing me the Apache install screen from the iMac, but outside of the house I was unable to connect.

 

Updates

10.17.03: After waiting around for a while, I Googled and found that Verizon is in fact blocking port 80 for inbound HTTP requests because of the stupid Code Red virus. I may try to open port 8080 on Monday to see if that can make it through. Even so, it looks like Apple File Protocol can't make it through on port 548 as well, even though that works perfectly inside the house. Arrggh!

10.9.03: Apparently I had set the DNS client to look at the wrong connection (Built-in Ethernet instead of PPPoE). I also put the iMac outside the firewall in the DMZ, so theoretically it should be seen to the outside world. It's very possible that Verizon has port 80 shut down, but I'd love to be able to at least get the filesharing working. I have to figure out how to point the webserver to port 8080 tonight. I also have to open the AFP ports on the router (athough technically it's out in the DMZ already) and turn the firewall in OSX on.

10.7.03:No luck getting the hostname to work in the client.