How do I make Exchange 2007 available on two different subnets?

We have a single Exchange 2007 server in our main HQ office. The plan is to have our other branch offices added to the domain over existing VPN subnets to connect to the Exchange server. We're trying to add bandwidth to our Exchange server by hosting it on its own T1 line and creating a new subnet for it, and also keeping it available on the HQ subnet by using multiple NIC cards. Are there any issues we should be aware of, especially concerning DNS?
ThukaungAsked:
Who is Participating?
 
MesthaConnect With a Mentor Commented:
I and many other Exchange MVPs have just seen so many issues with dual homing, getting email to flow correctly, OWA not working reliably etc. It is just a mess.
I don't see how dual homing will resolve your bandwidth issues any more than just putting the server on the main LAN and having the VPN terminate on the LAN itself. If you are trying to use the connection exclusively for Exchange, then that simply isn't going to happen, as trying to segregate AD traffic in that way will usually cause a problem. To get the traffic to use that link will mean some AD changes will have to be made.

-M
0
 
sandeep_narkhedeCommented:
just ensure that the exchange server name resolution works through FQDN from both the networks. you do not have any settings in exchange to make it work on different IP Subnets. Just ensure these two networks can ping each other & the hosts can resolve the names correctly through nslookup
0
 
ThukaungAuthor Commented:
Another thing:

From the HQ office, the exchange server will appear as x.x.1.234. From external offices, the exchange server should appear as x.x.6.234. We plan on having DNS managed by Active Directory, replicated over the VPN links to DC's in each office. How do we have external offices resolve the server address differently than workstations at HQ office and keep it replicated over AD?
0
 
MesthaCommented:
Dual homing Exchange is a bad idea, and not something I would recommend. Have the VPN links terminate on your existing LAN so that the clients can access the server on its own IP address. Don't forget the clients will also need to contact the domain controllers.

-M
0
 
ThukaungAuthor Commented:
Mestha:

What are the drawbacks aside from this DNS issue? As far as I know, dual homing would be the best way to solve our bandwidth issues while keeping Exchange on the HQ LAN.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.