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 2:25 PM
 
Good Morning All,

I have already installed DNN but needed to re-create the site in IIS7.  The IIS7 site is pointing to c:\dnn, bindings have been set to IP Address Unassigned Port 81.  So, when I go to http://localhost:81 on my dedicated server, I'm presented with my DNN site. 

The issue I'm having is when I click on Login.  Insead of being taken to the DNN login page, my search engine of choice pops up with results for localhost 81 default.  Also, when I click the Register link, I receive Resource cannot be found for register.aspx.

Something is not quite right with my IIS bindings.  Can someone help me?  Please keep in mind that we're running Plesk, although I'm using RDP to access the server now, and that the DNN install will be hosting several top-level domains.

Thanks,
Sid
 
New Post
6/25/2010 2:47 PM
 
Is there a reason you are not using the default port (port 80) locally? I assume your production environment will just use port 80. 

Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
6/25/2010 2:54 PM
 
Hi Chris, In IIS7, the Default Site is already set to use port 80. When I set the DNN "site" to the same port, I receive a message stating that another site is using the port. Would it be acceptable to create this duplicate binding? Thanks, Sid
 
New Post
6/25/2010 3:05 PM
 
Sid, you cannot have two using the same domain (in this case, it is localhost). However, you can setup a virtual directory and point it to whatever directory you want (ie. localhost/dnn, where dnn is your virtual directory name. You would like have it pointed to the c:\dnn\Website folder though in IIS). I recommend going this route to save the headache of dealing w/ the ports when you really don't need to. 

Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
6/25/2010 3:13 PM
 
Chris, To make sure I'm following you, you're saying to keep the port set to 81? I created a virtual directory associated with my DNN "site" in IIS pointing to c:\dnn. Is that the correct approach? Sorry for all the questions, first time working on a dedicated server, not used to all the "freedom". Thanks, 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