Re: Remote exchange 2000 server

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Matthew Byrd [MSFT] (matbyrd_at_online.microsoft.com)
Date: 04/21/04


Date: Wed, 21 Apr 2004 13:25:36 -0400

Hi Lars,

Based on the information here I would recommend the following:

1) Place the East Coast DC/GC and E2k server in a separate AD Site this will
ensure that AD generates a proper replication topology and will ensure that
the East Coast E2k server doesn't try to talk to the West Coast DC/GC

2) Place the two E2k servers in separate Routing groups. This will allow
you to have better control over the message flow between the two while also
giving your control over public folder referrals so that the East coast
clients are not connecting to west coast replicas of Public folders.

3) You will need to setup an SMTP connector on the West Coast box with an
address space of * this will cause that server to be preferred for all
outbound email ... otherwise each exchange server will send its own outbound
email.

Hope this Helps,

-- 
Matthew Byrd
Microsoft PSS
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
"larssven1" <larssven1@excite.com> wrote in message
news:e7644e.0404210657.6544fd4d@posting.google.com...
> Our company (West coast) bought another company (East coast).  We are
> using Windows 2000 with exchange 2000.  We are going to set up a
> remote windows 2000 server integrated into our active directory(on the
> east coast).  We would also like to set up a remote exchange 2000
> server on the east coast.  The two sites will be connected with a
> reliable, fast VPN.  All the internet email will first come to our
> exchange server.  If email is received for an east coast user, we
> would like the message to be forwarded to the east coast exchange
> server.  When an east coast user sends email, we would like it to be
> forwarded to the west coast exchange server then out to the internet.
> My question is how to I set up the remote exchange server?  Do I use
> routing groups? Will the east coast exchange server be in the same
> routing group as the west coast, or will it need to be in a different
> routing group.  I think the server itself will need to be in a
> different site under Active Directory Sites and Services, but I am not
> positive.  Any help would be much appreciated.  If any knows of a good
> White Paper, that would also be a great help.
>
> Lars


Relevant Pages

  • opening attachments is slow
    ... I am running 4 exchange 2000 clusters in domain A on the ... server is a bridge head server. ... offices on the east coast connecting to 1 exch2003 cluster ... server on domain B located on the west coast. ...
    (microsoft.public.exchange2000.connectivity)
  • split organization. Now get NDRs and SMTP event 7010 xech50
    ... Set up an Exchange server 2003 for a company whose west coast office split off from the East coast. ... On the East coast server I created contacts to forward mail for users at the old domain name to the new domain for the west coast company. ...
    (microsoft.public.exchange.admin)
  • Re: Remote Desktop Connection becomes graphically confused
    ... Is there any way to try to reproduce this on the network the server is on? ... > east coast showed this behavior via a couple clients running RDC here ... The problem also showed up via an RDC client running ...
    (microsoft.public.windows.terminal_services)
  • Re: FreeBSD vs. Linux TechTV Clip - Edited and Synced
    ... For anyone interested a further mirror is available from the ... This server is in Japan @ 100Mbps. ... > Please use it if you are east coast. ... To unsubscribe, ...
    (freebsd-newbies)
  • Re: FreeBSD vs. Linux TechTV Clip - Edited and Synced
    ... For anyone interested a further mirror is available from the ... This server is in Japan @ 100Mbps. ... > Please use it if you are east coast. ... To unsubscribe, ...
    (freebsd-questions)