A client of ours has been unable to access OWA since changing their domain name. Their emails have been changed from alias@old_domain.com to alias@new_domain.com.au. Their website is now www.new_donain.com.au, but RWW/OWA/etc is still on remote.old_domain.com. Email through outlook are working fine, no problems there. Just having an issue with OWA. Going to remote.old_domain.com/exchange presents me with the normal log in screen. But as soon as i authenticate I am given a HTTP error 404 page. However, going to remote.old_domain.com/remote/alias@old_domain.com or remote.old_domain.com/exchange/alias@new_domain.com.au both give me access to my mailbox. The Local Path for the Exchange virtual folder is pointing to \\.\BackOfficeStorage\new_domain.com.au\MBX which I assume correct. Im guessing theres gonna be one mention of old_domain.com that needs to be changed to new_domain.com.au (or the other way around), but I'm a bit stuck as to what that might be. Any advice would be appreciated. Thanks.

Did you remove the old domain from their email addresses? That is probably the problem. What you should have done was leave the email addresses exactly as they were, added the new domain and made it primary and NOT removed the old domain. There is a connection between the default domain (which matches the Windows domain) and OWA in Exchange 2003. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Yeah, left the old email addresses associated with the account, just added the new one (and set as primary).

How do you authenticate to your OWA-Site? User name: alias@new_domain.com.au and the corresponding password? Which URL is presented when receiving error 404? I would try to recreate the Exchange virual directory using IIS-console. Kind regards Eduard

The email domain in the Exchange virtual directory path URL is completely irrelevant. Unless you have renamed the domain (which with Exchange is usually a bad idea) this path to the Exchange virtual directory is not valid: \\.\BackOfficeStorage\new_domain.com.au\MBX The domain in that URL needs to be the WINDOWS domain, rather than the email domain. The fact that you have changed the user's email address is completely ignored by Exchange for OWA access, and if you have changed anything more than the email address and recipient policy to take in to account the new email domain, then you have broken things, as it wasn't required. I would suggest that you reset the virtual directories using this KB article. http://support.microsoft.com/kb/883380 Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Normally, authentication is windows username and password. I just tried alias@old_domain.com and alias@new_domain.com.au and was given username/password incorrect. username@windows_domain.local and password authenticates but again results in a 404. The URL im getting the 404 on is https://remote.old_domain.com/exchange/eurl.axd/<guid> I've tried recreating the virtual directories as per that article, with no luck. As far as I could tell, that made no difference at all. Not that I'm trying to pass blame here or anything, but im not that one that did the change over, so im not 100% sure exactly what happened. Point being, now its not working and I was the lucky one to get the job of fixing it. As far as im aware, it was meant to be a simple case of change email addresses/recipiant policy and everone should be on their new email address. Obviously something has gone a bit wrong in that process. Happy to provide any more details if needed. Thanks.

Accordning to this article - How system administrators can troubleshoot an "HTTP 404 - File not found" error message on a server that is running IIS The Web server returns the "HTTP 404 - File not found" error message when it cannot retrieve the page that was requested. The following are some common causes of this error message: The requested file has been renamed. The requested file has been moved to another location and/or deleted. The requested file is temporarily unavailable due to maintenance, upgrades, or other unknown causes. The requested file does not exist. IIS 6.0: The appropriate Web service extension or MIME type is not enabled. A virtual directory is mapped to the root of a drive on another server. Hope this helps Eduard

Thanks Eduard. I understand what causes a 404 error. Just in this case I'm not sure what needs to change to fix the problem. There is obviously a reference somewher to either their old domain that needs to be changed to the new domain, or the other way around. I would of thought recreating the virtual directories would sort out the IIS side of things? So im more inclined to believe the problem lies somewhere in exchange? Would that be a correct assumption?

Hi Chris_d33 - Even after you did the DS2MB (Delete and recreate the virtual directories)...still the issue is there? What is the value @ the \\.\BackOfficeStorage\new_domain.com.au\MBX Is that the new_domain.com.au or the old_domain.com.au? Cheers Aravind

Delete and recreate virtual directories had no effect at all. Still having the same problem. dir \\.\backofficestorage lists only new_domain.com.au The old domain is no longer there. \\.\backofficestorage\new_domain.com.au\MBX contains everyones mailbox. Or have i missunderstood what you're asking for? Do you mean what is the local path for the exchagne virtual directory in IIS? If thats what you mean, its pointing to \\.\BackOfficeStorage\new_domain.com.au\MBX

So just to confirm my understanding. At this point of time: Normally, authentication is windows username and password. I just tried alias@old_domain.com and alias@new_domain.com.au and was given username/password incorrect. username@windows_domain.local and password authenticates but again results in a 404. am i correct? Testing basic IIS pages: > can you choose the iistart.htm or any other images files @ the "Default web site" Configure that pages to have the basic-authentication Then try with the same Authentication repsonse (which you provide for OWA) check for the results. Note: My expectation is that OWA and basic pages should work similar way. As in both the cases the IIS depends @ AD to get the authentication Cheers Aravind

Thats correct, Arvindpe. Logging in with an email address (old or new) as username results in incorrect username/password. Windows username is authenticating but 404ing. Changing to basic auth had no effect at all. Still getting the same 404 after logging in. I dont believe authentication has anything to do wtih my problem. Users can authenticate to RWW with out problems. And to OWA when appening the URL with their email address.

Thanks for your comments chris_d33 --> when OWA works with the URL and email address...this should be an explict OWA logon For any server, OWA should work fine both with the explict and implicit logon >> can you please explain your problem once again for me. (i.e, what is working and what is failing to http 404) Cheers ARavind

The problem is that an implicit logon results in a 404 error. Explicit logins work fine.

The Local Path for the Exchange virtual folder is pointing to \\.\BackOfficeStorage\new_domain.com.au\MBX which I assume correct. Im guessing theres gonna be one mention of old_domain.com that needs to be changed to new_domain.com.au (or the other way around), but I'm a bit stuck as to what that might be. Any advice would be appreciated. Thanks. Hi, The only thing I can think of that would change \\.\BackOfficeStorage is that you edited the Default recipients policy and added new_domain.com.au as the Primary address. I would suggest that you create a new Recipient Policy with the new smtpdomain and remove the same smtpdomain from the Default Policy. That should change the path back to \\.\BackOfficeStorage\old_domain.com.au\MBXMartina Miskovic - http://www.nic2012.com/