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 ...Localhost works, remote doesnLocalhost works, remote doesn't
Previous
 
Next
New Post
2/16/2007 4:44 PM
 

Hi there!  (Brace yourself...get a coctail...this is long)

I've read a ton of postings, and none of the resolutions posted have worked for me...YET! But I'm soooooo close  : )

The Basics:

DNN 4.4.1 / ASP .NET 2.0

C:\Inetpub\wwwroot\DotNetNuke4\Website (folder contains Default.aspx)

IIS 5 / Windows 2000

Created a Virtual Directory under the Default Web Site called DotNetNuke4 and specified the

local path = C:\Inetpub\wwwroot\DotNetNuke4\Website

Installation of DNN on my test server worked GREAT! So happy! I logged in as host, created a portal alias called www.mytestdnn.com. Wonderful! So smooth!  On this server, the site comes up as http://localhost/DotNetNuke4/

Ok great..now technically, I should be able to use my computer and access the test server I just installed DNN on, by using the portal alias I created.  Also, I added an entry on my local machines host file mapping www.mytestdnn.com to the ip of the remote machine. So, on my machine, I type in:

www.mytestdnn.com  - I get Under Construction

www.mytestdnn.com/DotNetNuke4 - The page cannot be displayed / currently unavailable

but I know I'm getting to the server, because in the Website directory under DNN I created a test file called jenifer.htm and when I try http://www.mytestdnn.com/dotnetnuke4/jenifer.htm I get my file...so i know i'm accessing the remote server and I'm in!  But Why doesn't my DNN site come up?

http://www.mytestdnn.com/default.aspx - I get "Server Error  in '/' Application. The resource cannot be found.

I've seen postings say that IIS doesn't know that I want Dnn as my default web page...so it's trying to start the IIS default web page, then mine and I'm in a loop...therefore I get notta!  But I'm not sure if this is true, and I don't know how/where to tell IIS to use my DotNetNuke4 as its default web site.  Under the IIS settings, under Default Web Site, I changed the Home Directory from C:\Inetpub\wwwroot\ to C:\Inetpub\wwwroot\DotNetNuke4\Website  (Which i don't think i'm supposed to do.)

Went back to my machine, type int http://www.mytestdnn.com and I get under construction.

Tried C:\Inetpub\wwwroot\DotNetNuke4\Website AND I'M IN.....but again...I think I'm not supposed to change the home directory on the Default Web Site.

So, the other way I got this site to work remotely...

Instead of Creating a Virtual Directory under the Default Web Site...I created a new stand alone web site on the server.

Specified a description and a Host Header.  I pointed it to the path where my Dnn install resides C:\Inetpub\wwwroot\DotNetNuke4\Website.

Then, went back to my machine..typed in

http://www.mytestdnn.com - got under contruction

C:\Inetpub\wwwroot\DotNetNuke4\Website - IM IN REMOTELY!!!!!!!!!!!!!!!!!!!!!!!!!!! 

BUT  HOW COME IT DOESN'T WORK WHEN SET UP AS A VIRTUAL DIRECTORY? 

Can someone pleaseeeeeeeeee tell me what I'm doing wrong?

Thanks for any help someone can provide...I'm sure it's just me, and I'm doing something wrong or missing something.

-Jen

 

 

 
New Post
2/17/2007 1:53 AM
 
Looks like I'm having the same problem.  I've completed the build under MS Web Developer 2005 Express, and within WD2005 I can browse the default.aspx file and everything looks peachy.  If I go to IIS and try to browse it -- I get a Page Not Found.  If I try to browse it remotely, I get 'The page cannot be displayed'.   In WD2005, it goes to:  http://localhost:4063/dnn/Default.aspx.  IIS is configured with port 80.

I'm remote desktoped into my web server (WS2003) and configured a regular IIS website, pointing to the dnn directory where the default.aspx file is located and fixed the IIS config so that default.aspx is the only document choice (removed the other default choices to reduce the variables). 

Like Jen I can remotely browse other files in the directory -- such as a logo file.

-pfs
 
New Post
2/19/2007 2:17 PM
 

Ok, I got it working... I knew it was right under my nose!

For me, having created my Virtual Directory under the Default Web Site....When I created my portal alias www.mytestdnn.com I should have added the Folder DotNetNuke4 after it!  So it should have been this www.mytestdnn.com/DotNetNuke4

Now I can access my site remotely from my desk machine...using  www.mytestdnn.com/DotNetNuke4

Yipeeeeeeeeeee!

Cheers!

-Jen

 

 
New Post
2/19/2007 3:10 PM
 

As a virtual directory it is a "sub folder' under your default website.  So for example your default website is http://localhost, then a virtual directory of "DotNetNuke4" under that directory would be called by http://localhost/DotNetNuke4.  If you are pointing to a remote server's root you would be using the same logic, unless you setup a new website to handle the requests to a specific location.

Also, if you are using DotNetNuke you need to make sure that default.aspx is set as the default page in IIS, if you don't do that you will have a large number of problems...


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
2/19/2007 3:28 PM
 
Yes, Thank you!  I finally understand the folder structure!
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Localhost works, remote doesnLocalhost works, remote doesn't


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