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 ...Portal AliasPortal Alias
Previous
 
Next
New Post
10/16/2009 5:53 PM
 

I installed DNN 5.1 on a Windows Server 2003 box. I placed DNN into a directory called DotNetNuke under C:\Inetpub\wwwroot\ and pointed a virtual directory named DotNetNuke at it in IIS and the install completed without errors. I setup IIS for ASP2.0, set all directory permissions, etc. All works well.

The following aliases work well <localhost\dotnetnuke> and <173.9.8.59/doynetnuke>.
I setup another alias of www.esimedia.com.
I redirected the "A" records for www.esimedia.com to point to 173.9.8.59.

My problem is that if I type in www.esimedia.com into a browser I get the standard IISStart.htm page and not my portal page.
My default website points to c:\Inetpub\wwwroot should it point to c:\Inetpub\wwwroot\dotnetnuke?
The install documentation does not state to do this, it simply indicates to setup the virtual directory.
Do I need to do something in IIS to get this to work?

Thanks in advance.

 
New Post
10/16/2009 6:07 PM
 

It does not seem to matter if I point my default website to wwwroot or to wwwroot\dotnetnuke, same problem happens.

 
New Post
10/16/2009 8:29 PM
 

Try to login on DNN whith Host acount, then go to Host - Portals, edit your Portal and add www.yoursite.com on HTTP alias 

 
New Post
10/17/2009 12:11 PM
 

 Hi,

I had this issue with my first installation of DNN about 2 years ago. My understanding is that if you are setting up DNN for the local environment what you have done will work perfectly. However, for web access it will create permission's issues.

In the install instruction's ensure you follow the part for web deployment and not for local host. Don't use the virtual directory - put the install files directly into your home directory and startup your install using your www.yoursite.com from a remote computer. This will correctly configure the environment for web deployment. Of course be sure that you have your permissions configured properly for your alias.

There are lots of blog post on how to make the install process. I suggest Mitchel Sellers or Chris Hammonds. They both provide great info.

Cheers,

Pat


Healing the world one spine at a time. Chiropractic Websites using the DNN Framework.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Portal AliasPortal Alias


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