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 ...IIS7 Binding SettingsIIS7 Binding Settings
Previous
 
Next
New Post
6/25/2010 3:28 PM
 
No, you want port 81 out of the deal completely. As for did you do it correctly, you need to make sure IIS 7 thinks your virtual directory is set to run as an application (right click the virtual directory in IIS, if it says Manage Application it is already one. If it is not, it will give you the option to Convert to Application). Then, try calling localhost/VirtualDirectoryName in your browser and see if it comes up. 

Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
6/25/2010 4:06 PM
 
Chris, In the Edit Site Bindings subwindow, I'm using IP Address = All Unassigned and Hostname is blank. When I delete 81 from the Port field, the OK button grays out. How do I set this up without a port? The virtual directory is now setup. I did click on Convert to Application and now have a Manage Applicaton option on the flyout menu. I know this is more an IIS issue, vs. a DNN one, but nonetheless I really appreciate your help and guidance. Please let me know what else I need to do. Thanks, Sid
 
New Post
6/25/2010 4:15 PM
Accepted Answer 
Sid, you can leave the old port 81 there and deal w/ it later (ie. delete it as a site in IIS). You need to put this virtual directory under the localhost server (typically, Default Web Site). To clarify, when you open IIS Manager, you will see the following: [Machine Name] which is the top level node. This should contain 2 nodes: Application Pools & Sites. When you expand sites you will likely see two more nodes, "Default Web Site" and whatever the new one was named you created. 

Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
6/25/2010 4:31 PM
 
Chris, Thanks so much! I had created a separate IIS site called DNN and had the virtual directory under it. I created a new virtual directory under Default Web Site and I'm now getting the DNN setup screen when I browse http://localhost/dnnfiles. Thanks again!! Sid
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...IIS7 Binding SettingsIIS7 Binding Settings


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