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 ...Newb - IIS vs VS 2005 built-in web serverNewb - IIS vs VS 2005 built-in web server
Previous
 
Next
New Post
6/11/2007 12:37 PM
 

Hi all.

I'm new to both .NET and DNN.  I have dnn 4.3.7 installed and I can run it in VS 2005, on my XP machine, using the built-in web server inclueded with VS.  I've followed all the instructions I can find to set up the virtual directory in IIS (5.1).  However, if I type in the URL (http://localhost/website) into explorer, all I get is 404 or 403 errors. 

If I run the app in VS, and then copy and paste the resulting URL, which now includes the port number (http://localhost:xxxx/website), the app will run just fine.

How do I set it up to get around having to do that?  I'm just trying to experiment with DNN as a simple intranet, to be run on our network domain, from an XP box.

I'm hoping this problem is the result of some, basic practice for asp.net apps, that I've yet to learn. 

Any suggestions?

 
New Post
6/11/2007 1:04 PM
 

Now that I've played with it a little more, I see that it will only run on the VS web server and not IIS. 

I get get as far as being able to navigate to the URL (http://localhost/website) and get a directory listing, but if I try to go any farther, as in clicking on the "default.aspx" link, I get HTTP Error 403 - Fortbidden...

 
New Post
6/11/2007 1:41 PM
 

bogjacket,

I would suggest the following:

Add default.aspx as a "default document" in IIS (right click on the directory in IIS and select "properties" -> select the "documents" tab)

Also, you will want to make sure that the ASP.Net Machine Account (ASPNET) has the appropriate permissions on your directory (full control is probably fine for your local environment).

hope that helps,

Ian


Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
New Post
6/11/2007 2:21 PM
 

Thanks, Ian. 

I should've provided more info.  I've already done both of the things you've suggested.  I've opened the physical and virtural directories up as wide as I can, giving full permissions to just about anyone, including the aspnet account.

 
New Post
6/11/2007 3:11 PM
 

If you have set up default.aspx as a default document, I don't see how it could be giving you a directory lising with default.aspx included.  Can you make sure that you've done that on that specific virtual directory?

Also, problems that we run into a lot with giving permissions is giving the permissions to the domain ASPNET account, rather than to your machine's ASPNET account.  If you are on a domain, double check which ASPNET account you've given permissions to.


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Newb - IIS vs VS 2005 built-in web serverNewb - IIS vs VS 2005 built-in web server


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