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 ...Publishing a DotNetNuke sitePublishing a DotNetNuke site
Previous
 
Next
New Post
7/9/2007 4:33 AM
 

I have a question about publishing a DotNetNuke site. I have installed DNN on a server and performed a default installation. The server hosting the DNN website (and other non-DNN websites) is on a private network, behind a ISA 2006 firewall. We have one public IP address through which we can access the server hosting the websites. In ISA a rule has been defined to direct HTTP requests to the server hosting the websites. The other (non-DNN) websites which are hosted can all be accessed from the Internet, but the DNN website cannot. All sites, including the DNN website, can be accessed from the private network.
What makes the DNN website different from the other websites, in particular with regards to ISA 2006 (for that is where I suspect the cause of the problem lies). I have tried to find a solution to this problem on the Internet, but I have only come across people having a similar problem and not to a solution to this problem.
Could any one on this forum help me solve this problem? I would really appreciate it.

 
New Post
7/18/2007 4:41 PM
 

I have same problem...

Today I installed DNN on internal server at port 8008. Access from internal network by http://server.internal.com:8008 is Оk. This server hosted some webs at ports 8001, 8002, etc.

At ISA server exist some publishing rules from different external names to this internal IIS. This rules working fine.

But when i create new publishing rule http://external.com to http://internal.com:8008 (http://external.com added to portal aliases at DNN) DNN return to external client page contained with internal links like http://internal.com:8008.

How can i resolve it?

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Publishing a DotNetNuke sitePublishing a DotNetNuke site


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