Hello!

   I have the dnn application deployed on server with the following aliases:

  1) localhost/dotnetnuke (on IIS - this is a simple virtual folder)

  2) server1/dotnetnuke (on IIS - the same thing as above - server1 is the net name of server)

  3) server1:83 (on IIS - this is a separate web site on web server. it has the same home directroy as above)

  So, in our intranet everything works fine - no redirections to localhost/dotnetnuke when requesting 2) or 3) from any other computer.

  But we want the people to see the site through the internet. We got a firewall or a proxy that has an ip (lets say 222.22.22.22) and a special port (lets say 33).

When it gets the request it simply redirects it to server1:83. And here the troubles come - the user got redirected to localhost/dotnetnuke and he got "The page cannot be found" error.

   Can somebody help with that?

   Thanks

 

You will need to add a portal alias for the external URL as you did for the internal ones.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

Can you verify whether "Use Portnumber" in the appsettings (web.config) is set to true?

Also, i've had an issue like this a long time ago. Could you try making the external portnumber the same as the internal portnumber (or the other way around of course).

---

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

DNN Blog | Twitter: @erikvb | LinkedIn: