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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...New Parent Portal Alias WoesNew Parent Portal Alias Woes
Previous
 
Next
New Post
5/5/2006 1:56 AM
 
smehaffie wrote
 SlicerX wrote

Option #2
1) Update your C:\WINDOWS\system32\drivers\etc\hosts file so that any domains you want to point to your DNN install point to 127.0.0.1 same as local host does.  So using the example above you would have 3 entries

127.0.0.1 localhost
127.0.0.1 Parent1.com
127.0.0.1 Parent2.com

2) Create new parent web site using one of the domains you created an entry for in step #1.

3) You will still get an error when you try to access the site using the new domain.

** At this point you will stil get an error that you cannot access the site.  The reason for this is the new parent domain point to the root of the default web site and not the DNN virtual directory.  So you need to take additional steps to get this to work.

4) Access site using the original URL and login as host.

5) Go to Host / Portals and edit each portal.  At the bottom of the screen you will see the alias you created the new Parent with (Parent1.com, Parent2.com, etc).  So it access the DNN directory you would need to edit the alias and add the DotNetNuke_2 virtual directory (Parent1.com/DotNetNuke_2, Parent2.com/DotNetnuke_2, etc)

I was having a similar problem where I would install DotNetNuke to my preferred Virtual Directory, but when I opened my portal, it would attempt to redirect to http://localhost/DotNetNuke_2 every time. After I created a Virtual Directory named "DotNetNuke_2", it would open the portal. I searched throught the file system for anything that might be redirecting to the DotNetNuke_2 Virtual Directory, but was only able to find a redirect in the default.aspx page to something coming from the Database. I was using SQLExpress, so I couldn't just open up the database in Sql Server Management Studio, it had to be something configurable within the portal. I followed steps 4 and 5 of SlicerX's recommendations and am now able to open my portal with my preferred Virtual Directory and Alias.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...New Parent Portal Alias WoesNew Parent Portal Alias Woes


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