I have a new install of DNN on a new server...  have a new parent portal that I want a web name to point to.  I have the domain pointed at the server - and see the basic IIS 7 page.

What do I do to tell IIS to send web requests to DNN?  From what I understand about DNN, it handles the routing, etc of website requests - but I can't get to DNN - I just get to IIS.

If Ian's post doesn't hit the mark exactly, I interpreted your post perhaps slightly differently.

The first main task is to be certain you have setup IIS7 to support ASP.NET (it's not configured that way by default).

After that, you want to assign one IP address to each instance of DNN (or other web technology) you have running. Eg. If you have two DNN instances like 4.8.4 and another 4.8.4 or a 4.8.3, each DNN instance has to have its own IP address. As you noted, within each DNN instance you can have multiple portals but there can be reasons why you might want to have more than one instance/installation of DNN running on the same machine. Note that you <can> configure multiple DNN instances to use the same IP address and use different ports, but that would be very inconvenient to be typing the port number all the time... and you <can't> use the same IP address and use Host Headers to differentiate the DNN instances and still enjoy the full ability to support multiple websites within each instance.

In summary, when setting up at least one and more DNN instances,

• Use different IP addresses.
• Don't use different ports or Host Headers.

Now, a few hints when setting up DNN...

1. When a DNN install fails, WIPE OUT the files and the database. Start again by copying brand new files and creating a brand new database.
2. Setup your initial website using Localhost or the loopback address (usually 127.0.0.1) because that website will then always be accessible launching a browser from the same machine, even if there are problems later. You can then go into the Portal's properties later and add "Alias" which are the IP address and FQDN Users will use to access the website.
3. Don't scrimp on machine resources. Be certain your machine has adequate RAM and processing resources, the install doesn't return useful errors when the install fails due to insufficient memory or processing power. I recommend 512mb RAM, 600mhz, decent disk subsystem as minimal regardless of docs.
4. Maybe should be considered first, but be certain your website is configured to use the proper version of dotNET Framework in IIS.

HTH, in particular these 3 "hints" should get you installed properly. Don't try to configure a remote FQDN until you're sure the first website works perfectly.

Tony

Still not sure exactly what to do... here is what I currently have;

I have an install of DNN that runs using "localhost/dnninstall".  I went into this install and added a new DNN Portal (Parent).  The new portal is named for a domain name that is set to point to the IP address where the web server resides.

When I browse the domain, all I am getting right now is the generic IIS7 form...  I don't know what to do to direct IIS to send the http requests to DNN.  I have been told that DNN handles the requests and serves up the appropriate portal.  I know this is something basic and simple - but I do not know what to do to get this going.  Your help is appreciated.

I am actually trying to move several sites from one server to another - and I was not involved in the initial install of DNN on the first server.  It works, and I am being told by those that are asking me to do this - to look at the current running server and use its setup.  But I see nothing that points me in the right direction.  All I see is the basic stuff that I am familiar with - nothing about how to redirect this or that.

BTW... I am a professional developer and not a network admin.  I am familiar with networking and servers, but I am not intimate with the setup of webservers, etc.