Managing Active Directory can get complicated. Often, the native tools for managing AD are just not up to the task. The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.
Solved
Exchange 2010 Multiple NICS in CAS and HUB Servers
Posted on 2012-12-22
We are setting up a new Exchange 2010 environment. We will have individual servers for each role. 2 CAS Servers, 2 HUBS, 3x Mailbox.
The CAS server will be front-ended with a HW LB, so we will not be using NLB. We will set the CAS in a CAS Array.
We are considering putting two NICS in the CAS and HUB servers. I'll call them the "Front End" and "Back End" NICs.
For the CAS servers one which will be facing towards the HW LBs (Front End) and ultimately the Internet to handle Internet based Client Access, which will be the only Client Access we will have for OutLook Anywhere and OWA, etc. The other NIC will be for the Back End MAPI network connecting to the mailbox and hub servers, etc. For the HUBs one will face the Internet for SMTP in/out and the other the MAPI network.
I have a few things I am trying to figure out with this approach.
1. Is it necessary and/or best practice to have two NICS in the CAS and/or HUB servers?
2. The "Internet Facing" NICS will have the gateway set to the FW/LB while the "backend" NIC will have no gateway, seeing as all the other Exchange servers are on the same subnet. That should be fine for now, but what if we put Exchange servers in another Data Center and need to and split a DAG across, and perhaps want to provide CAS and HUB servers from the secondary data center if the primary fails. Do we have to make sure that the CAS and HUB servers communicate via the MAPI nework rather than going out the "front-end"?
3. Finally, on the FW/LB facing NICS, should they be registered in AD DNS. I suspect note because we want all the MAPI traffic hitting the "backend" NICs.
The CAS server will be front-ended with a HW LB, so we will not be using NLB. We will set the CAS in a CAS Array.
We are considering putting two NICS in the CAS and HUB servers. I'll call them the "Front End" and "Back End" NICs.
For the CAS servers one which will be facing towards the HW LBs (Front End) and ultimately the Internet to handle Internet based Client Access, which will be the only Client Access we will have for OutLook Anywhere and OWA, etc. The other NIC will be for the Back End MAPI network connecting to the mailbox and hub servers, etc. For the HUBs one will face the Internet for SMTP in/out and the other the MAPI network.
I have a few things I am trying to figure out with this approach.
1. Is it necessary and/or best practice to have two NICS in the CAS and/or HUB servers?
2. The "Internet Facing" NICS will have the gateway set to the FW/LB while the "backend" NIC will have no gateway, seeing as all the other Exchange servers are on the same subnet. That should be fine for now, but what if we put Exchange servers in another Data Center and need to and split a DAG across, and perhaps want to provide CAS and HUB servers from the secondary data center if the primary fails. Do we have to make sure that the CAS and HUB servers communicate via the MAPI nework rather than going out the "front-end"?
3. Finally, on the FW/LB facing NICS, should they be registered in AD DNS. I suspect note because we want all the MAPI traffic hitting the "backend" NICs.
[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 Comments
Active 1 day ago
No, it isn't best practise to have multiple NICs in this scenario and I don't see any benefit in doing so. The only server that multiple NICs are recommended is the mailbox servers, so that the MAPI traffic can be seperated from the DAG traffic.
Dual homing Exchange causes nothing but problems, so I would put in a single NIC only. I don't think I would even consider anything else and I don't remember it being in any of the design documentation from Microsoft, so might not even be a supported scenario!
Simon.
Dual homing Exchange causes nothing but problems, so I would put in a single NIC only. I don't think I would even consider anything else and I don't remember it being in any of the design documentation from Microsoft, so might not even be a supported scenario!
Simon.
Unless its a very large system, say for more than 10k users, or it generates a very large amount of mail, I can't see the logic in separating the HT and CAS roles.
I wouldn't expose the CAS servers directly to the Internet. I would always do this via TMG but sadly you can no longer buy TMG licences, you have to now buy UAG which also requires CALs.
I wouldn't expose the CAS servers directly to the Internet. I would always do this via TMG but sadly you can no longer buy TMG licences, you have to now buy UAG which also requires CALs.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
A list of top three free exchange EDB viewers that helps the user to extract a mailbox from an unmounted .edb file and get a clear preview of all emails & other items with just a single click on mailboxes.
This article will help to fix the below errors for MS Exchange Server 2013
I. Certificate error "name on the security certificate is invalid or does not match the name of the site"
II. Out of Office not working
III. Make Internal URLs and Externa…
In this video we show how to create a Shared Mailbox 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 Recipients >> Sha…
The video tutorial explains the basics of the Exchange server Database Availability groups.
The components of this video include:
1. Automatic Failover
2. Failover Clustering
3. Active Manager
Suggested Courses
Course of the Month11 days, 4 hours left to enroll
719 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.