Hello all, We are migrating to a new domain name, from www.town.org to www.townma.gov. For OWA, there is a script running to redirect users from mail.town.org to mail.townma.gov, and also to use https instead of http. When one types "mail.town.org" into a browser, you are brought to the page which says "A password for mail.town.org is required" I type this name and password in, and I am brought to another login box asking for a user name and password for mail.townma.gov. I type in the user name and password again, and get to yet another login box. This one is asking me for a user name and password for mail.town.org again. I type the name and password in and I get to my mailbox. We want to get to https://mail.townma.gov and cannot seem to be able to. Any help/advice/suggestions with my Exchange 2003 issue is greatly appreciated.

Hi, Did you register mail.townma.gov? Why didn't you input the https://mail.townma.govdirectly? For this issue, please just register mail.townma.gov that points to your Exchange IP address. After that, please test this issue Thanks Allen

Hello Allen, I have typed in https://mail.mytown.gov into my browser and it brings me to a login screen for mail.mytown.gov and it also indicates that the certificate is for the .org site, and not the .gov site. I enter my credentials, and I get brought to the mytown.org OWA login screen. Our 2 websites (mytown.org and mytownma.gov ) are registered with our ISP, so I do not think that is the problem, but I have not discounted the possibility. It appears that either in Exchange 2003 or in IIS 6 that all OWA mail logins are directed to the mytown.org site. The person who set up the new site is no longer working here, and this was assigned to me even though I have little experience with Exchange and IIS. It is quite a learning experience, though!

Hi, Before going on, I would like to explain the process how IIS handle the request from the client: The first step is the most obvious, the client opens up their browser and enters http://mail.domain.com or if SSL is configured https://mail.domain.com. DNS is used to resolve the domain name to an IP address and then a request is made over the appropriate port, TCP 80 for HTTP or TCP 443 for SSL. The IIS service on the Exchange 2003 server will be listening on port 80/443 and will determine which website should handle the request.There would only have the Default Web Site and the request would be sent there. However, if there are more than one Default Web Site, such as theserver is also a web server hosting other websites, IIS will need to figure out the right website to direct the request. This is done using either the Port, the IP address, or a host header. Now, I suggest we open IIS, expand Web Sites, create a new site, input the Host header value as mail.mytownma.gov, then apply with the certificate for this site. After that, please try to stop Default Web Site and access the new site. What's the result? Thanks Allen

Hi Allen, I have a theory about what is happening. In out IIS manager, there is only the Default web site. So if a user tries to access mail for mytownma.gov, and since that website does not exist, IIS sends the user to the Default web site (which happens to be mytown.org). That seems to make sense to me. What I plan to do is to simply add a Host Header in the Default web site to read "mail.mytownma.gov". It is my hope that this will bring the users to the correct site. I am not 100% sure if that is the correct solution or if creating a second web site is the way to go. We are planning on decommissioning the mytown.org mail AND website shortly after this OWA issue is fixed.

Hi, Absolutely right. Please try to implement the steps based on my suggestions. Thanks Allen

Allen, I just read that Host headers cannot be used when SSL is enforced. This is a problem since that is what is required for our webmail. Any suggestions?

Hi, Please refer to the below link to troubleshoot this issue: http://support.microsoft.com/kb/187504 Thanks Allen

Hello again, Nothing I am trying seems to resolve my issue. The biggest hurdle for me is that I am not knowledgeable enough about Exchange 2003 and IIS 6 to ask the correct questions. I am learning, though. Is there some reading material you would recommend for adding a second SMTP domain? My thinking is that the person who initially set this up never let Exchange, IIS, or both of the new domain that we are trying to use. Where is this new domain defined? We have DNS set up, both externally and internally. Once again, thanks for your assistence and patience.Craig