Exchange 2007 OWA redirecting to another OWA server

We have just added a second Client access serer to our Exchange 2007 infrastructure, as a second server with its own external IP and host name with SSL cert.

server1 has as internal and external address which has been working for the last 2 years with out any problems, due to company growth and for redundancy we decided to add a second CAS server we set it up with again for both internal and external address.

the strange thing is that when you go to webmail.... its seams to redirect to webmail1, and sometimes give the wrong certificate i.e. your redirected to webmail1(Server2) but been issued the SSL for Webmail(Server1)

Activesync and outlook AnyWhere seams to be working normally.

All servers are running Windows 2008 R2, Exchange version is 2007 SP1

We have 4 Database servers 4 Hub-transport Servers and 2 CAS servers

Thanks in advance.
Who is Participating?
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
Sure about this:

Windows 2008 R2, Exchange version is 2007 SP1

As that isn't a supported combination.
If you are still on Exchange 2007 Sp1, then upgrade to Sp3.
If you are on a mixed version then you need to get them up to the same versions.

Otherwise clarify exactly what you have.

The behaviour or proxy vs redirection has changed in later updates.

Scott JohnstonSystems ConsultantCommented:
External DNS does it have 2 MX records?
Does the your firewall have routes added for the second exchang server OWA?
GardITAuthor Commented:
Hi, thanks for your reply

Yes both servers have there own external IP, which have firewall and NAT rules which directs them the right server.

We have 3 MX servers for our domains, but email is flowing normally, its just the webmail which is redirecting, its all most like Exchange is doing some sort load balancing.
GardITAuthor Commented:
Yes Windows server 2008 R2, and all our Exchange servers are 2007 SP1,

it may not be supported, but its been working for the last 3 years,
Simon Butler (Sembee)ConsultantCommented:
Previous behaviour isn't an indication that things will continue to work.

Not only is that combination not supported (I guess it was installed before the blocks went in to stop it) but Exchange 2007 Sp1 hasn't been supported for at least three years. I am actually surprised it would work!

I would strongly suggest an upgrade to Exchange 2007 SP3 and then see if the problem continues.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.