Multi-site Exchange2003 internal/external name resolution
I have a customer with 2 sites, both are in the same domain domain.local with a DC+Exchange 2003 on each site. There are mailboxes on both Exchange servers. The sites are connected by vpn using a 3rd party thing I know little about. They each obviously have their own internet connection and reasonably autonomous. Both sites are set up so that mymail.washingtonoffice.co
Either site will let me open OWA, but when it tries to authenticate and the mailbox whose credential I use is stored on the OTHER server I get forwarded. Which would be fine but it forwards my browser to the INTERNAL fqdn of the other server. Internally they are using a .local domain so obviously I cant set up DNS for them!
Is this meant to happen? Is there a way round it? I found the following technet article and the submitter is having precisely the same problem as me but nobody has replied yet. I thought I would ask the real experts :o)
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2174627&SiteID=17
Quinn
Either site will let me open OWA, but when it tries to authenticate and the mailbox whose credential I use is stored on the OTHER server I get forwarded. Which would be fine but it forwards my browser to the INTERNAL fqdn of the other server. Internally they are using a .local domain so obviously I cant set up DNS for them!
Is this meant to happen? Is there a way round it? I found the following technet article and the submitter is having precisely the same problem as me but nobody has replied yet. I thought I would ask the real experts :o)
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2174627&SiteID=17
Quinn
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
When a client introduces a second Exchange server I tell them that they need to budget for a third server to act as a frontend. Trying to run a multi server environment without one is challenging.
Simon.
--
If your question has been answered, pleased remember to accept the answer and close the question.
Simon.
--
If your question has been answered, pleased remember to accept the answer and close the question.
ASKER
Suppose I do the following:
Create a web page, plain old html that has 2 links, one that says "click here for sheffield users" and another for washington users. Those links then forward to the OWA page for the relevant Exchange server/site.
Obviously that relies on the mailboxes being held on the right servers/sites and the users clicking on the right thing. What do you reckon?
Create a web page, plain old html that has 2 links, one that says "click here for sheffield users" and another for washington users. Those links then forward to the OWA page for the relevant Exchange server/site.
Obviously that relies on the mailboxes being held on the right servers/sites and the users clicking on the right thing. What do you reckon?
That is one way.
Or the users need to know which server their mailbox is on.
Simon.
Or the users need to know which server their mailbox is on.
Simon.
ASKER