I am getting to the bottom of this but still don't have a resolution. To explain further...
As I now understand, I need to configure a portal alias. I have done this for the URL in question. Let's call it www3.company.com (
www.company.com is my primary machine and I don't wish to tinker with that yet). So, I have the appropriate DNS entries and when I call
http://www3.company.com I hit the right physical server. However, the content that is served is the standard IIS banner for a new IIS installation (with no sites configured).
What presumably needs to happen is for DNN to "intercept" the incoming request and resolve to the appropriate portal. Further, I assume that's the intent of the portal alias. So, I enter "www3.company.com" as a portal alias. But this doesn't seem to help. I still see the regular IIS banner (from the IIS home directory) when I navigate to
http://www3.company.com. In short, DNN doesn't seem to be involved in the request - it just serves content like a regular web site.
Also confusing is that if I navigate to
http://www3.company.com/dotnetnuke I get a Page Not Found error. If I TS into the server and access through
http://localhost/dotnetnuke then I can fully access my portal.
What am I missing?
Thanks.
Mark