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 8080 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

Ideally I should have port 8080 forward to port 8080 on my dev system and IIS should also answer that port as well. Do you know the Vista IIS7 steps to do this?

Regards,
/DaveS

BTW: 5Mb isn't really much faster than 1.5Mb. The portion of a page load that is the Http Request and depends on latency, the physical distance between nodes and the speed of light takes the same time. The data transfer component of a web page access that depends on bandwidth is usually small.  It could be much faster downloading large files such as DNN Creatives videos except the servers usually limit the bandwidth that a sinngle user can consume.  The tend to limit it do about 1.5Mb I have discovered. So while I can get great numbers with Speedtest pages I don't see them many other places. I had the option of 50Mb. I'm glas I didn't opt for it.

Dave,

I haven't yet made it into the world of IIS running Vista, so I'm not going to be a lot of help. As a matter of fact, I'm keeping some XP machines in operation because I can mostly find my way around IIS on Vista.

That said, it would seem as if the port specification ought at least be similar ... I guess not, or you wouldn't be asking. I do think that Michael Washington has some information relative to Vista and IIS. They may be hidden in some module development articles, though ...

But, with Lee's tutorial from Issue 31, I did get IIS installed.

And I just took a look ... perhaps you want to look at the "Bindings" property when you've selected ASP under IIS on the IIS manager. I see something there that has a port specified ...

There are at least two issues here.

1. IIS seems to want me to have a "site" per port, so I have to create another site in addition to the "default site." When I do this using parameters that seem to be reasonable IIS puts a big red X on it.

As usual MS's help is useless.

2. What else do I have to do within DNN?


Somewhere the must be a webmaster that is running on multiple ports who knows the magic

Ideally I should be able create a separate domain at the same IP and have IIS route the requests to the correct place via the domain name portion of the URL without using two ports. I have no idea how to do that, but this is what is happening when you have multiple portal aliases for the same site.

Thanks for trying,
/DaveS

Hello,

I haven't experimented with ports, but I have successfully set up multiple parent portals in vista and IIS, don't know if that will help, if it's of interest let me know and I will post the information. thanks,

It really depends on what "multple parent portals on Vista" means to you.

I have 40+ parent portals on www.AgingSafely.com  hosted at my ISP. When I clone that system on my localhost a have IIS setup to display a few of them. For example:

www.AgingSafely.com becomes localhost/asi3 and ???.dyndns.com/asi3
Basic.AgingSafely.com becomes localhost/basic and ???.dyndns.com/basic
etc.

This setup is easy and is all under the default site on port 80

Due to Verizon's "no port 80" FIOS setup I need to re-think and re-implement this.  Since I have had no luck figuring how to set ISS up for for both port 80 and 8080 maybe I should change the localhost to be ONLY on port 8080 and do it that way.

/DaveS

I finally put my thinking cap on and realized that I didn't need a second IIS site. All I needed to do was enable port 8080 on the default site. I assumed that I could only have one port per site but that isn't true. 

changed my aliases from localhost/asi3 to localhost:8080/asi3 and xxx.dnsalias.com to xxx.dnsalais.com:8080/as3

Forwarded port 8080 in my router to port 8080 at 192.168.5.12

And uncommented the line in web.com abouy ports other than 80.

So much for Verizon's blocking port 80

Now is 5Mb/2Mb was actually faster than 1.5Mb/384Kb when downloading Lee's video's   Actually I just checked and this is one of the few sites that I actually can get 5Mb download speed from.  Good work Lee

/DaveS

great! - glad you got it sorted