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 ...Access through router using different port than port 80Access through router using different port than port 80
Previous
 
Next
New Post
2/27/2006 7:15 AM
 

In our set up we want to run DNN on a box behind our ADSL router. Typically we use NAT to route different ports to different boxes and applications.

For example: http://dnn.example.com:28888 would get routed to 192.168.1.11 which is running DNN on port 80.

DNN seems to have trouble with this. I get the home page up, but clicking any link gives me a page not found error as the port number (28888) is not used in the link.

Is it possible to configure DNN to do this?

Thanks,

 

Mike

 
New Post
2/27/2006 7:47 AM
 

I haven't had this situation, so not an expert but have you looked at the host/settings /advanced and looked to see if you can add port options there.. or is that the mail (don't want to confuse you sorry) but also - what about adding in a portal alias - adding the port in under the portal alias.

I think my first thought might have been relating to email. But surely you could try and see what result by adding in the portal alias table.

Hope this gives some insight.

Nina Meiers


Nina Meiers My Little Website
If it's on DNN, I fix, build, deploy, support,skin, host, design, consult, implement, integrate and done since 2003.
Who am I? Just a city chic, having a crack at organic berry farming.. and creating awesome websites.
 
New Post
2/27/2006 9:30 AM
 

Thanks Nina,

I had previously tried fiddlying with the portal alias, but never got it to work. I had a look at host/settings/advanced; there isn't a post setting, but I tried setting the HostURL to include the post number, but this didn't work either.

So I'm still looking for a solution, if there is one.

 

Thanks again,

 

Mike

 
New Post
3/14/2006 12:30 PM
 

This is what I did:
In IIS - add port 8080 to the list of "listening" ports

In DotNetNuke - add yourdnsname:8080/dotnetnuke

The trick was adding the port 8080 in IIS

This worked for me.

 
New Post
3/15/2006 5:33 AM
 

espenalb wrote

The trick was adding the port 8080 in IIS

Thanks for this. Actually I was doing some configuration on IIS yesterday and saw that option and figured it might be worth trying out, but I haven't do so yet.

 

I'll try it later and report back.

Thanks again,

 

Mike

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Access through router using different port than port 80Access through router using different port than port 80


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