[ExchangeList] Re: Joining Exchange 2003 server to a remote domain
- From: "John T \(Lists\)" <johnlist@xxxxxxxxxxxxxxxxxxx>
- To: <exchangelist@xxxxxxxxxxxxx>
- Date: Fri, 12 May 2006 15:29:20 -0700
As George has alluded to, it is critical for the Exchange server to
reliablely and continually communicate with AD. If it is absolutely required
that this Exchange server be at this remote site, then it is best to have a
second server as well (NOT THE EXCHANGE SERVER ITSELF) as an additional AD
server and also a GC server.
John T
eServices For You
"Seek, and ye shall find!"
-----Original Message-----
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Taylor, George
Sent: Friday, May 12, 2006 3:06 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Joining Exchange 2003 server to a remote domain
I'm guessing your corporate location has good internet capabilities, but do
they have a good firewall and VPN device? An inexpensive solution on your
end could be a SonicWall with a cable modem to create a site-to-site VPN.
Not the best performance and I've never tried to put a server on the far end
of a VPN, but if your getting a couple meg out of the cable modem you should
be in good shape. Just remember that if your connection is down for any
length of time you'll hose up replication and Exchange is not gonna be a
happy camper. The expensive part is at the corporate side, you'll need some
kind of VPN concentrator or appliance. The Cisco ASA 5500 Secirity
Appliance is very nice and very secure.
Take a look at Cisco and SonicWall web sites for several scenarios on how to
setup a VPN.
On the other hand have you thought about the same scenario but leaving the
Exchange server at corporate and having your users use OWA? Could work for
a low user count.
George Taylor
Systems Programmer
Regional Health Inc.
_____
From: Jabber Wock [mailto:jabberwock99@xxxxxxxxx]
Sent: Friday, May 12, 2006 3:48 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Joining Exchange 2003 server to a remote domain
Hi,
No it is not. It is a newly installed server, not yet joined to any domain.
JW
On 5/12/06, Michael B. Smith <michael@xxxxxxxxxxxx> wrote:
Is the server already a member of the domain?
_____
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Jabber Wock
Sent: Friday, May 12, 2006 3:44 PM
To: [ExchangeList]
Subject: [ExchangeList] Joining Exchange 2003 server to a remote domain
Hi,
I have a need to set up an Exchange 2003 server which is located hundreds of
miles away from the corporate location, where the AD (DC) resides. What
would you recommend for this scenario? VPN? Other? Will Microsoft VPN (
i.e. RAS server running on the same server as the Exchange server) work for
setting up a VPN tunnel?
best regards
Mike
Other related posts:
