Hi -

I have a DNN installation running behind an ISA 2006 server in a reverse proxy configuration.  I'm struggling to find the applicable portal alias.

IIS has a virtual directory (we'll call it DNN) mapped to the DNN root.  It's set up correctly as localhost browsing works as it should and apparently uses the /localhost/DNN    portal alias.

http://customers.mydomain.com leads to our ISA box in a DMZ, which then serves as a proxy by directing the request internally to http://123.456.789.123/customers  .  The ISA function works as it should as a test.htm file placed in the root of the DNN directory is served fine @ http://customers.mydomain.com/test.htm

It seems that a portal alias of 123.456.789.123/customers would do the trick, but it doesn't.  I've of course tried every permutation ever made with customers.mydomain.com and that dummy IP with no luck.

Any tips?  Any gotchas for DNN with reverse proxies?  A look at the logs didn't offer any clues... I suppose I need to sniff the traffic to see what is really being requested from the ISA box.

More generally, this is certainly the only portal that will run out of this DNN installation.  I'd be perfectly happy to essentially hard code it so that all requests go to a given portal.  Advice on how to do that?

Many thanks-
kel way

Hi glocar,

Actually, yes, I would call it very very good luck.

The key is that the portal alias needs to be publicly accessible, so having an ISA box that translates to an internal URL doesn't do the trick.  My solution was to add the public customers.mycompany.com to the hosts file of the ISA box and point it to the internal IP address of the internal web server.  I added the same hosts entry to the web server itself. 

I created a dummy default2.aspx page with tracing turned on and accessed it from a machine through the ISA box and noted that the host field in headers section was just "customers".  So, I changed the ISA "This rule applies to this published site" option to point to "customers.mydomain.com" and then made sure to have a customers.mydomain.com portal alias in place, and it worked.  In all my troubleshooting, I also moved my DNN installation to the root of a new (non-default) website.  I'm pretty sure that one or more of these steps aren't necessary, but as a whole they did the trick.

Hope that helps a little... am happy to share more detailed configuration if you like.  Good luck!

I was getting very nervous at the 95% project completion stage and felt that this might be a real show-stopper!