Solved

Connecting Exchange Servers Across the Internet

Posted on 2008-10-27
4
207 Views
Last Modified: 2010-04-21
Our main Exchange 2003 server is at a hosting provider.  We have a site-to-site VPN connection to them but we always access the mail server through the Internet, not the VPN.  I recently added an Exchange 2003 backend server plus an Exchange 2003 frontend server at our local office in preparation to move all email locally.  This would be a gradual transition where mailboxes would be moved over a few at a time. I've done testing on this setup and all servers can communicate with each other fine through the VPN; all mail is delivered to the appropriate mailboxes.  I moved my mailbox to the new local server and used the new frontend server for a week without incident.  When I went live with this new configuration, I made the change in internal and external DNS to point all users to the new frontend server.  Things were fine for a day or two but then the VPN hardware on our side became nonresponsive.  Turns out it could not handle the load.

My question is is there a way for the local and hosted Exchange servers to communicate with each other over the Internet instead of the VPN route?   Every search I've done on this topic involves using a VPN connection.  I'm looking for a definite yes or no on whether this can be done, and if it can what are the steps to do it.
0
Comment
Question by:Nyacton
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 6

Expert Comment

by:ajeab
ID: 22814907
you mean you still have most of the user on host and some on local, right?

Then why can't you change the DNS to the way it was?? since you have less user on your local.  So when  the user that reside on the HOST connect it will connect directly with HOST. but when you want  to connect to your mailbox it will first contact the HOST server first then the HOST server will forward the request to your FE server.  This way the VPN traffic should be minimal.  

Also, Check your VPN configuration.  It should not matter where the user connected to. Either HOST or FE server. there should be only 1 tunnel open between your server and HOST.

to link both exchange over internet, I think it is possible but you will have to open lot of ports. which is increase security risk for your server too.

port use by exchange need to open
http://searchexchange.techtarget.com/tip/1,289483,sid43_gci1124126,00.html

0
 

Author Comment

by:Nyacton
ID: 22815562
Thanks for the response.  Right now, all live accounts are on the hosted Exchange.  I have a test account on the local.  DNS is back to the way it was.  If I connect to OWA, which is pointing back to the hosted server, with an account that has a mailbox on the local server, it's going to fail.  That's why I need the front end server...I don't want to have to have multiple OWA addresses or manually configure email clients.  As for the VPN, there is only one tunnel.  The device itself becomes nonresponsive after a while (can't ping or get to web interface) but machines on the other side are still accessible but intermittently.
0
 
LVL 6

Accepted Solution

by:
ajeab earned 500 total points
ID: 22816756
I don't think HOST server willing to connect to your site. How many users are you talking about??

The problem is you can't move few users at a time. because your domain MX record is point to HOST server not your Front End (FE).  If you do move some user over to your server, those users will not get new email unless you forward them  but you can't forward to your own domain.

Ask your HOST if they can provide PST file for all of your users.(they can use Exmerge), If they can. Then you create all users Email box on your BE server.
Notify your user of downtime.
Change MX record from you domain registrar to point to your FE instead of HOST (allow up to 24 hrs for worldwide change)
Change your Internal DNS to modify OWA address to point to your BE server
Change your External DNS to modify OWA address to your FE server IP
 Copy PST file to your BE server.
Then Exmerge PST into your BE server.

This way you user will use the same address.  when user connect locally, they will connect using LAN.
when they connect from home. They will connect to FE and FE will connect them to the right server.

If you currently connect OWA via internet right now. what is the purpose of the VPN site-to-site then??
0
 

Author Closing Comment

by:Nyacton
ID: 31510395
Everything I've been reading says it's bad news to open the Exchange servers to the Internet which is my original question.  Thanks for the help.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Read this checklist to learn more about the 15 things you should never include in an email signature.
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question