OWA on a second exchange server

[titresfct]

We recently added a new exchange server and are currently in the process of moving mailboxes from the old server to the new one. Both servers will be running for awhile but the goal is to take the old server off the domain.

I have moved only 2 mailboxes for test purposes, everything works fine except for OWA.

OWA still works for the mailboxes on the old server but for the two mailboxes on the new server i get redirected to newserver.domain.local/exchange. I then get an authentication windows but no credential works. I have tried domain\username with the same results.

Both servers are windows 2003 R2 with SP2 and both are running exchange server 2003

Can anyone help?

 

[58sniper]

Is this when you try it internally, or externally, or both?

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[titresfct]

Internally i have to enter a username and a password twice externally no credential works.

 

[58sniper]

Well, internally, it's likely because the first time you're attempting it, it's on the old server, which then promptly sends you to the new server, and you need to authenticate again.

Externally, it's likely because no publicly accessible path to the new server exists through the address used.

Internally, if you go directly to the new server

https://newserver/exchange

does it work as designed? If so, then what I listed above is the case. That's as designed.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[titresfct]

You are right it does work if i go directly to the new server.

So basically what you are saying is that there is no way to have OWA access on both servers at the same time?

OWA will only work properly once all the mailbox are moved and the firewall is reconfigured to send traffic to the new server?

 

[58sniper]

Unless you dedicate another IP and A record for the second server, that's correct.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/