Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...DotNetNuke 5 access problemsDotNetNuke 5 access problems
Previous
 
Next
New Post
1/29/2009 10:32 AM
 
Darren Brennan

Joined: 1/22/2009
Posts: 2

 

Hoping someone can help me with this.  It MAY be an IIS problem or maybe a DNN5 problem....not entirely sure at this point.  Any help or guidance would be appreciated.

I have been tasked to create a company Intranet and I have recently installed a copy of DotNetNuke 5 on a Windows Server 2003 R2 box.  It is setup in a virtual directory (called Intranet_Live) under the Default website.  I can access it locally using http://localhost/Intranet_Live/Default.aspx with no problems. 

The problem arises when I try to connect from another computer on the network using http://<server name>/Intranet_Live/Default.aspx or http://<server ip>/Intranet_Live/Default.aspx.  With either option I get a failed to connect error message and strangely the browser web address changes on the remote computer to http://localhost/intranet_live   Very strange!

So far I have tried the following:

  • Uninstalled and reinstalled IIS.  Reran asp_regiis for .Net 2.0 after this.
  • Competely reinstalled the DotNetNuke installation from scratch.
  • Folder permissions are tested as part of the DNN install.  However for further testing I have given the ASP.NET, IUSR, IWAM & NETWORK SERVICE users Modify, Read/Execute, List & Write permissions from wwwroot down (excessive I know but I would have revoked unnecessary rights had it worked....it didn't)
  • I've had our Sys Admins look into the problem and they cant see anything wrong.

Incidently I dropped in a test.htm file into the folder and the remote computers can access that page no problem.  This I believe proves that the permissions are ok and possibly suggests that there is a problem with .Net and/or dynamic content.  However other .Net websites on the same IIS work fine both locally and remotely.

I have spent two days on this thus far and I am now unsure what else to try.  Any guidance would be greatly received.

Many thanks

Darren

 
 
New Post
1/29/2009 11:20 AM
 
Mike Horton


Joined: 7/16/2003
Posts: 4865

When you create the DNN website it's initial alias points to whatever the address was when you installed it. So if you install it locally on the server the portal alias is http://localhost/..... What you need to do is to give it an alias for the server address which can be done at the bottom of Admin->Site Settings (you may have to be logged in as Host).
 
New Post
1/29/2009 11:45 AM
 
Darren Brennan

Joined: 1/22/2009
Posts: 2

Hi Mike

That worked!  Thank you so much for your help.  I thought I was going crazy with this!

Does appear to be a bit of a gotcha for first time users though....I think they should maybe mention that on the install documents.

Many thanks for your assistance

Darren
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DotNetNuke 5 access problemsDotNetNuke 5 access problems


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