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 ...Setting up DNN as an actual website instead of virtual directory in IIS 6.0Setting up DNN as an actual website instead of virtual directory in IIS 6.0
Previous
 
Next
New Post
3/26/2007 2:33 PM
 

If you haven't figured this out already, here are the points to change:

12)  The website directory should be just c:\MyWebsite from the description you give.

The URL would be http://localhost:8081/ or http://{SystemName}:8081/

You need to specify the port in the URL if you use a non-standard port.  You also need to add/change the portal host entry in DNN for this to work correctly.

Jeff

 
New Post
3/26/2007 3:22 PM
 

ljoe:

Your steps were almost right.  Your issue is related to 1. lacking a host header and 2. DNS resolution to reach the intended site.  See the following post in which I described issues very similar to what you are facing: http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/117486/scope/posts/Default.aspx.  Notice the explanation on how the server can identify what site a request is intended for and the relationship of the IP address, the host header, and the port number.  Basically, you don't need to make your life more complicated by using a non-standard port.  If you have a domain already defined you could use something like "newdnnname.yourcurrentdomain.com" to reach your new DNN site.

Also, you should have installed the "Install" version of DNN and not the source.  There is no need to run the source unless you intend to do programming that will modify the core.  This is a common misconception.  The Install package is ready to run.

Go over the link above and post any questions you may have afterward.

Oh yes, the physical directory should just be c:\MyWebsite in your case.

Carlos

 

 
New Post
4/3/2007 5:41 AM
 

Hi Carlos and others,

Thank you all for your contributions. I actually haven't tried all these yet as I was only back to my work desk recently. But will try these out and get back to you guys.

Cheers,

Joe

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Setting up DNN as an actual website instead of virtual directory in IIS 6.0Setting up DNN as an actual website instead of virtual directory in IIS 6.0


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