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 ...Server with multiple URLs causes bad linksServer with multiple URLs causes bad links
Previous
 
Next
New Post
5/2/2006 4:35 PM
 
Keith Talbot

Joined: 1/23/2006
Posts: 4

I have a development server which is accessed using different URLs from inside and outside or our firewall. Normally this causes no problem with ASP.NET development. But DNN has a problem. In this case DNN 4.0.3.

I have tried running the install script as either http://internalname/dnn and http://externalname/dnn. In both cases DNN insists on redirecting to the internal name. If I then add an alias for the external name I can display the first page but all of the links on that page have the internal name in them.

Please help.
 
New Post
5/2/2006 4:53 PM
 
John VandenBrook


www.vandenbrook.com
Joined: 9/26/2003
Posts: 92

Hello:

What you will need to do is change your URL in the Portal Alias table.  This is the only location the DNN application picks up the http://localhost and re-directs to this.  You can change this to http://RawIPAddress/VirtualSiteName, or http://DNSName/VirtualSiteName.  If you don't want to use an IP address and don't use a DNS server for name resolution, you can also modify your hosts file under c:\windows\system32\drivers\etc.  Your entry would be your IP address and the name you would like to use.  Also, make sure your external clients can ping you IP address otherwise these suggestions will only work for those joined to your domain, i.e. Intranet users.

Good luck!

John 
 
New Post
5/3/2006 12:29 PM
 
Keith Talbot

Joined: 1/23/2006
Posts: 4

Thanks, but..

I'm pretty sure I have the alias added correctly. In fact compared to the suggestion of using a full URL which causes a very strange redirect to http://http/dnn it appears to be correct to put only the name/path in the table such as "externalname/dnn". This causes an unwanted but otherwise correct redirect to http://internalname/dnn.

Can someone answer this question..

If I simply have multiple URLs which point to the same IP, as far as DNN is concerned, should one of them be the primary and then all others get overlaid by the primary?

For example, if I use http://some_other_url/dnn, when the page displays should the link under login be http://the_installation_url/dnn/home/tabid/36/ctl/login/default.aspx? Because that's the effect I'm getting. And both URLs are in the PortalAlias table, one added during the installation and one afterwards.

Cheers, Keith
 
New Post
5/3/2006 2:17 PM
 
Michael Flanakin


Michael Flanakin's Avatar

michaelflanakin.com
Joined: 4/5/2004
Posts: 994
I have a bunch of servers that are all using multiple URLs. One, for instance, is directly accessible via the server name and also has a separate URL that is supplied by an single sign on (SSO) server (not Active Directory). Both work just fine. All URLs you get back will use the alias you used to get to the portal. So, if you get there using http://externalname/dnn, then all URLs will be relative to that URL. If, instead, you're getting redirected to http://internalname/dnn, then that means that DNN doesn't recognize your portal alias.

Here's the real question, tho: How is the router/firewall forwarding the request to your server? The SSO solution I used had to reference the server by IP. This means that all requests came in as http://123.123.123.123/dnn, instead of http://externalname/dnn. Based on this, I had to add the IP-based URL as a portal alias. You might want to try this same thing.
Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
New Post
5/4/2006 5:00 PM
 
Keith Talbot

Joined: 1/23/2006
Posts: 4

Firstly, thanks for confiming how aliases and the redirect process is supposed to work.

Despite quizzing our sys admin at length regarding the firewall situation we were unable to see exactly where the error was occuring. Finally I decided to install the source and debug the code. And what I found was this..

The code .. Request.Url .. does not return the actual URL used to access the server when the "externalname" is used. This is true for non-DNN pages too. It doesn't even return the "internalname". What it returns is "internalname.subdomain.domain". Which doesn't match any table alias.

So my question is now simply. What might cause Request.Url to return a URL other than the one I entered?

Cheers, Keith
 
 Page 1 of 3
123Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Server with multiple URLs causes bad linksServer with multiple URLs causes bad links


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