Then yes, it's a one-to-one relationship. More clients, bigger
hardware on the OWA box. You can use SSL. Or if you want to skip the
OWA box, just have them VPN in (you ARE implementing the technology,
after all) and let them use an IMAP client or Outlook.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Posted At: Tuesday, August 14, 2001 6:28 PM
Posted To: MSExchange Mailing List
Conversation: Frame Relay or T1 line+VPN.
Subject: RE: Frame Relay or T1 line+VPN.
Hi, Tom
We have Exchange server 5.5 right now.
John Shi
-----Original Message-----
From: Tom Meunier [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 4:25 PM
To: Exchange Discussions
Subject: RE: Frame Relay or T1 line+VPN.
I'll take the OWA one. :)
The only version info I saw in the email was one reference to one
Exchange 2000 server. You'd use a frontend-backend scenario. You'll
have to buy Exchange Enterprise for your frontend server. Other than
that, you can use Standard version if it suits all your other needs.
The frontend server will find the server that contains the users'
mailboxes. If you REALLY wanted them to access OWA at their own sites,
you'd need to put an OWA server in each place. Sizing considerations
are left to the reader.
But that's ten months from now. You didn't say what you have NOW. So
I'm assuming Exchange 2k.
-----Original Message-----
From: Andre Toussaint [mailto:[EMAIL PROTECTED]]
Posted At: Tuesday, August 14, 2001 5:26 PM
Posted To: MSExchange Mailing List
Conversation: Frame Relay or T1 line+VPN.
Subject: RE: Frame Relay or T1 line+VPN.
John,
Replication should work fine... Once the VPN is up and running, you
should
be able to do whatever you want with win2k, and exchange etc. Getting
the
VPN setup is mainly just getting TCP/IP to work with all the sites
together,
in a virtually private way. Once that is working, you should be able to
play
around with multiple domains and their trusts, and other stuff, because
that
stuff all uses TCP/IP. You see, Win2k doesn't really need to know there
is a
VPN at all, it will just use normal TCP/IP operations to communicate
across
the VPN. To NT, the other VPN site will just be like another subnet.
I should note, that theoretically (and maybe someone else can shed some
light here) the VPN connection will be slower. Because they are
encrypting
all the data, so the router/VPN device must encrypt the data(some time
wasted there) and once the data is encrypted, it has some overhead. So,
you
may have to play with replication a little bit, but I think it would
work
fine.
As for your OWA question:
That is a good question... Translated= Hmmm, I don't know.
I guess at the office, the users could type the internal machine name of
the
exchange box they want to get to for OWA. But, what if they are at home,
ant
want to OWA to check their mail? Maybe set up a machine to just serve
the
OWA, and everyone use the same one?
I don't have any real experience with OWA in a multiple Exchange site
environment. Anyone else care to shed some light here?
Andre
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 3:10 PM
To: Exchange Discussions
Subject: RE: Frame Relay or T1 line+VPN.
Hi, Andre
How about Replication between all the W2K DC on different sites? If you
change some configuratin on W2K DC on the central stie, how would this
replicate to the remote sites through VPN?
If I want everyone remoste site to get to the OWA on their sites, how
would
this work if you have the private IP address? Currently, we have an
external
IP address for pop 3 for a remote site Exchange server.
Thanks
John Shi
-----Original Message-----
From: Andre Toussaint [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 2:49 PM
To: Exchange Discussions
Subject: RE: Frame Relay or T1 line+VPN.
If I understood you correctly:
The way each office connects to the internet should not matter for the
VPN.
And, the router at each office (the main router, one that sits between
the
office and internet) should handle VPN. Just make sure each router
supports
each other for VPN.
And, you would only need 1 Exchange server to be on a public IP (only
the
pop3 and smtp ports open). The non-public exchange servers would
communicate
with the 'main' exchange server over the VPN. (of course, each router
would
need a public IP)
At the company I work at now, at one point we had VPN going between
Frame
Relay (main office), DSL (other office) and Cable and DSL residential
services.
Each VPN location is treated as a different subnet. Once you have VPN
working, you can setup your network to use the subnets... Multiple
Exchange
Sites etc just pretend it's a normal, subnetted network. Exchange does
not
need to know about the VPN at all.
I hope this made sense, and I hope I read your question correctly.
Also, there are probably some better ways of doing this, and I'm sure
this
group will let you and me know about it real quick ;)
Andre
-----Original Message-----
From: John Shi [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 2:40 PM
To: Exchange Discussions
Subject: Frame Relay or T1 line+VPN.
Hi, Everyone
The Technology is changing very fast. I was more comfortable with Frame
Relay then T1 Internet VPN technology.
We have one central site and 4 remotes sites. Originally, I was thinking
to keep the frame Relay, but my boss thought the each site has its own
T1
line and VPN to our central stie is good as well. The issue is pricing
is
about the same on T1 to the Internet and frame Relay.
On the remote site, we are going to have W2K DC and Exchange 2000 server
10 months from now. The frame Relay contract is going to expire within 9
months. I want to find out if I should re-evaluate the T1 Internet and
VPN
options or I should keep Frame Relay. How would the W2K DC replication
work on the VPN at the different locations? I did not need to think
about
this when we are in the Frame relay.
If I go with VPN through T1 Internet. How would my Exchange server on
each
site commmunicate with each other throuh VPN? Does anyone see any need
that I should keep my Frame Relay based on our situation? If we use
Internet VPN on each site, does that mean we need to have public IP
address on the exchange server on each site.
Thanks
John Shi
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
