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 ...Server with multiple URLs causes bad linksServer with multiple URLs causes bad links
Previous
 
Next
New Post
5/8/2006 4:47 PM
 
Have you tried setting your alias to the machine's IP address? I'm not sure as to why you'd be getting the result you're getting unless there's some network appliance that is changing the URL. Try adding an alias for the fully-qualified domain.

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
New Post
5/9/2006 3:13 PM
 
I too am confused. I have a multihomed server as well. I set this up in the primary web.  I have it working locally and it works there.  I have the headers entered in the settings in IIS.  I type the website info www.xxxxxx.com/dotnetnuke/default.aspx and it work but says it switched to localhost.  I have tried editing the config file and changing local to the website name, the host file local host to the ip number. Nothing works.  You can not use IP numbers when you are using an IIS multihomed server becuase the headers have to match. It does not work if it is not on the the local box. Other machines on the same network get errors.Any other idea?
 
New Post
5/10/2006 10:23 AM
 
I'm not sure what you're referring to, but, again, you need every URL that you plan on accessing DNN with setup as a portal alias. Only the host account can do this (as far as I know) and it's done on the Admin > Site Settings page.

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
New Post
5/10/2006 3:24 PM
 

Ok, after a short break I returned to this problem and now have both a reason for the bad redirecting and also a cure. As indicated above there was indeed 'some network appliance' changing the URL.

I traced the problem by first adding some debug code into UrlRewriteModule.vb which quickly showed that Request.Url was not returning the URL that I originally entered. A similar test with a separate ASP.NET page confirmed that was the case independently of DNN. I was then able to take this information to our sys admin who introduced me to the department's Microsoft ISA Server 2004 (now this is all new to me).

What we discovered together was that there is an innocent looking checkbox on the "Publish <whatever> HTTP Properties" dialog called "Forward the original host header instead of the actual one". This is NOT checked by default. However, without it all request appear to be addressed to the <internal>.<domain> named server. And that's teh case even if an IP address was originally used.

So with that checkbox checked I then went on to add all of the following aliases to my PortalAlias table, making sure that the first one is the <external> and therefore always accessible one.

<internal>/dnn
<external>/dnn
<internal>.<domain>/dnn
<external>.<domain>/dnn
<internal IP>/dnn
<external IP>/dnn

And now everything works exactly like it should.

Thanks for all the help given, Keith

 
New Post
5/11/2006 11:25 AM
 
I see nothing on the admin settings page that refers to portal alias tables. And why does the header info on the local machine change to http://localhost/ ?  That seems like it would be controlled by the WebConfig file, but I have tried a number of things and it does not seem to work. Where is this portal alias table I need to change?
 
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