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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DotNetNuke: redirection problem...DotNetNuke: redirection problem...
Previous
 
Next
New Post
5/3/2007 4:50 AM
 

Halo everyone!

I have a problem making my DotNetNuke portal visible to anyone outside my intranet. The portal has to be configured in such way so that it goes public behind a firewall. The alias used for calling the portal from an external machine is http://dotsoft.dyndns.org:6969/kombos (i have added the url in the Portal Aliases). The message that i get in Mozilla when trying to access the portal from outside is: "The page isn't redirecting properly - Firefox has detected that the server is redirecting the request for this address in a way that will never complete." although i could see the portal the first time that i added the portal alias. When i try to access the portal usng IE 6 i get a message that the page can not be found. I have some experience in asp.net web applications, but it is the first time that i use the DotNetNuke platform. The version is 4.1.

Can anyone help me with this please?
Thanks in advance!

 
New Post
5/3/2007 9:30 AM
 

is the internal portnumber the same as the external portnumber? if not, that might be the cause of your issue here


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
5/3/2007 9:39 AM
 

Thanks for the reply ErikVB! The internal port number is 80. But isn't the alias supposed to point to the same location as the internal url (that uses the default port)?

 
New Post
5/3/2007 9:53 AM
 

I'm not quite sure ASP.NET picks up on the fact that it is running on port 6969 instead of port 80. So what you might try to do is to run the site on port 6969 internally as well (first add the correct internal alias or you will not be able to get into your site...)

The other option would be to change the external port number to 80


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
5/3/2007 10:15 AM
 

In addition to what Erik suggested, you may also want to try having an HTTP sniffer on your browser outside the firewall to find out exactly what requests are being made. Here's a free one: http://www.blunck.se/iehttpheaders/iehttpheaders.html

Nik

 


Nik Kalyani
Co-founder
DotNetNuke Corporation
Blog | Twitter | FaceBook
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DotNetNuke: redirection problem...DotNetNuke: redirection problem...


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