2nd Server - redirects

I recently added a second Exchange 2003 std. server. Both machines
appear under Exchange System Manager\Servers.

Both machines have SSL certs for OWA, but cert names do not match
machine names, for example:

ServerA.domain.com(machine name) has a cert "mail.domain.com"
ServerB.domain.com(machine name) has a cert "mail2.domain.com"

My problem comes up when a user logs into the wrong machine.

If a user outside our network connects to "mail.domain.com", but
his mail resides on the other server, he logs in and is immediately
redirected to "ServerB.domain.com".

This creates 2 problems.

First, it generates a cert error, because the user has been
directed to "ServerB.domain.com" and the cert says "mail2.domain.com.

Second, once the user accepts the cert error and elects to continue,
he is forced to login a second time, then (finally) he is allowed to
view his mail.

So, what I would like to have happen is:

If a user outside our network connects to "mail.domain.com", but
his mail resides on the other server, he logs in and is immediately
redirected to "mail2.domain.com" instead of being redirected to
"ServerB.domain.com". This would eliminate the cert error.
Is that do-able?

And second, once the user is properly routed, I would like for the
user to not have to log in a second time.

Is all of this possible?

Any help on this would be greatly appreciated, whatever it takes
to get the PHB off my tail. :)

Thanks so much!


*$

aa#2290

Henry
Fri May 09 13:50:34 CDT 2008

Hi
you have to introduce a front end server into your configuration
that's what this box is for.
It provides all back end servers with a single name space

henry

"Starbuck" wrote:

> I recently added a second Exchange 2003 std. server. Both machines
> appear under Exchange System Manager\Servers.
>
> Both machines have SSL certs for OWA, but cert names do not match
> machine names, for example:
>
> ServerA.domain.com(machine name) has a cert "mail.domain.com"
> ServerB.domain.com(machine name) has a cert "mail2.domain.com"
>
> My problem comes up when a user logs into the wrong machine.
>
> If a user outside our network connects to "mail.domain.com", but
> his mail resides on the other server, he logs in and is immediately
> redirected to "ServerB.domain.com".
>
> This creates 2 problems.
>
> First, it generates a cert error, because the user has been
> directed to "ServerB.domain.com" and the cert says "mail2.domain.com.
>
> Second, once the user accepts the cert error and elects to continue,
> he is forced to login a second time, then (finally) he is allowed to
> view his mail.
>
> So, what I would like to have happen is:
>
> If a user outside our network connects to "mail.domain.com", but
> his mail resides on the other server, he logs in and is immediately
> redirected to "mail2.domain.com" instead of being redirected to
> "ServerB.domain.com". This would eliminate the cert error.
> Is that do-able?
>
> And second, once the user is properly routed, I would like for the
> user to not have to log in a second time.
>
> Is all of this possible?
>
> Any help on this would be greatly appreciated, whatever it takes
> to get the PHB off my tail. :)
>
> Thanks so much!
>
>
> *$
>
> aa#2290
>