I clone my production site www.AgingSafely.com on my localhost as localhost/asi3. I also had port 80 forwarded thru my wireless router to my Vista development system. I have a DynDns.org dynamic name (???.dnsalias.com) assigned to this system so that I could access the web server from outside of my LAN. I keep ALL of the portal alliases in my production system so that I don't have to change paramters when cloning the production system at home.
These tools combine to make it easy to have W3C's validator access the pages on my developments system.
Last week I upgraded my DSL 1.5Mb internet connection from Verizon to their fiber FIOS 5Mb internet. On DSL Verizon didn't block port 80, but the do on their fiber network.
I have added ???.dnsalias.com:8080 as a portal alias, adjusted my router's port forwarding to forward port 80 to port 80 and added < add key="UsePortNumber" value="true" / > to the web.config. Whith this config I can access one page at a time only since the "8080" isn't getting added to the links in the menu and other places. Ideally I should have port 8080 forward to port 8080 on my dev system and IIS should also answer that port as well. Looking at Vista's IIS 7 it wants a whole new site tree in addition to the "default site" if I add a second port. I have tries what seems to be reasonable parameters but IIS places a big red X on the site element. Got any ideas how to IIS to use more than the default port?
Regards,
/DaveS |