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 ...Portal Alias not workingPortal Alias not working
Previous
 
Next
New Post
10/25/2006 6:31 AM
 

My head is getting sore from banging it on my desk...

Some information that may help:
I've got a clean install of DNN 4.3.5 running on Windows Server 2003. There is no website or header configured for the default website in IIS and DNN is installed in a virtual directory off the default site called DotNetNuke. I can access DNN locally with localhost/dotnetnuke. In attempting to get things working over the 'net I have set up portal aliases in DNN for www.domainname.co.uk, the server's IP address and www.domainname.co.uk/dotnetnuke. The latter is the only one that works; the others just take me to the 'Under construction' page kicked out by the IIS for the default website. The question is what do I need to do to get the portal running on just the domain name without the /dotnetnuke being appended? Is it a caching issue with DNN? I've restarted the website and IIS several times with no joy. Is it an IIS issue? Something in the web.config file?

Please help! ;-)

Thanks,

Pete

 
New Post
10/25/2006 8:25 AM
 
judas wrote

DNN is installed in a virtual directory off the default site called DotNetNuke.



If you've got DNN configured within IIS as a Virtual Directory then you will always have to browse to the site by appending /DotNetNuke to whatever hostname you have the IIS Website listening too.

Have you tried reconfiguring IIS to have DNN running off the root of the Default Web Site (e.g. change the Document Root of the default web site to point to the DNN install root).  Or create a fresh IIS Web Site and configure it with the document root pointing to your DNN install root.

Hope this helps.
 
New Post
10/25/2006 9:01 AM
 

 

You need to setup this DNN installation in it's own IIS website instead of having it run under the default website.

In IIS manager create a new website (not a virtual directory) and point it's home directory to the folder that DNN is in.


DotNetNuke Modules from Snapsis.com
 
New Post
10/25/2006 9:13 AM
 

OK thanks - I'll give that a go.

It would be helpful if the installation instructions were a little more clear on this and give options for such circumstances. :)

 
New Post
10/25/2006 9:30 AM
 

All working now thanks! :)

Ah, it's been a long week already...

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Portal Alias not workingPortal Alias not working


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