Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN Confiiguration IssueDNN Confiiguration Issue
Previous
 
Next
New Post
6/22/2015 5:04 PM
 

we are almost identical

if i bind to all unassigned the site will work after creation and be accessible locally but not outside the webserver, if i change the binding to a specific IP address it throws the under construction iis website.

 
New Post
6/23/2015 4:50 AM
 
>>if i bind to all unassigned the site will work after creation and be accessible locally but not outside the webserver

I think you have to tell us what actually happens. All Unassigned works for me. I believe it's the right setting on the ground that the binding is inspecting an incoming request and deciding which of several sites to route it to.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
6/23/2015 9:49 AM
 

ok so starting from ground floor this morning.  Blew every site away that i had tested on.  here are the steps i follow

1. Create folder outside of wwwroot and inetpub on seperate drive for dnn installs, give network service full rights to the folder root level

2.  extract contents of the zip install file into new folder named test.domain.com

3. create website in IIS, assign physical path to folder created above, create new app pool and assign as the default, select IP address from the drop down menu, give app pool full rights to the physical folder path in step 2

4.  Start new site, browse via fqdn, it goes directly to IIS start page, no dnn install wizard. If i attempt initiate the install by putting /install i get a 404 not found and they physical path is pointing to inetpub rather than the directory specified during site creation.

 
New Post
6/23/2015 12:15 PM
 

OK so as odd as this sounds it is now working and here is the sequence i followed.

1. bind site to default ip address, no specific binding, proceed through install wizard, browse to the site.  

2. go back into IIS, add a binding for the IP in the website and do not set a hostname, restart IIS, verified browsing to fqdn and IP address both internal and external from webserver

3. head back to IIS, add alternate header to IP binding, change original test.domain.com binding to the specific IP address desired, restart website and app pool.

4. verfied browsing via both fqdns from internal and external

5. stand up secondary site and just assign IP address above and set hostname, works without a hitch.

 

It almost looks like IIS had to make a binding just with the IP to learn what it needed to use it for before it could actually start routing traffic accordingly.   I am going to add another IP address this afternoon and see if i have to follow the same sequence or if everything will work properly now.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN Confiiguration IssueDNN Confiiguration Issue


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out