Thanks. Yes, I have that. To recap, here's what I have set up right now...

• I have two parent portals set up.
  • The original portal when I installed DNN, which is localhost/dotnetnuke
  • A new portal with the portal alias www3.company.com
• I have created a host header for www3.company.com (all unassigned IP addresses)
• DNS points www3.wednet.com to the server (resolves to the right physical server)

The current results are:

• If I navigate on the server (Remote Desktop) to http://localhost/dotnetnuke I see the original portal. That's OK.
• if I navigate on the server to http://www3.company.com I see the default IIS banner in the root of the default IIS web site (not good)
• If I navigate on the server to http://www3.company.com/dotnetnuke I am redirected to http://localhost/dotnetnuke (so, I see a portal but it's the wrong one - I have no idea why this redirection is happening since I have two separate parent portals)
• If I navigate over the Internet to http://www3.company.com I see the defailt IIS banner
• if I navigate to http://www3.company.com/dotnetnuke I get a Page Not Found error (presumably because the redirection to http://localhost/dotnetnuke is kicking in and this can't be resolved remotely)

So, still pretty confused. :-(

Mark

 Yep, have those in place (that's what I meant when I mentioned that I had configured the host headers - sorry if I wasn't more clear).

Thanks.

Mark