How can I limit the servers that can relay email from Exchange 2013 to an outside target when using a Load Balancer?

I am using Exchange2013 CU 5 on Win 2012 R2. I want to be able to control servers that can relay email to outside recipients. Before we had a Load Balancer, I would just add the IP of the servers to relay email to the Receive Connector and set the Authentication to Externally Secure. But we have purchased a Kemp VM Load Balancer. My testing found that, while keeping it Externally Secure,  I had to add the IP of the Load Balancer into the Receive Connector or I could not relay email to outside from any of my servers. Further testing found all I needed in the receive connector was the External Secure and the one IP of the Load Balancer. This is easier but I can no longer limit the servers that can relay SMTP email to an outside recipient.

Can anyone tell me how to limit servers that can relay SMTP email to outside when using a Load Balancer?

Thank you,
swfwmd2Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
You need to reconfigure the load balancer so it is transparent for SMTP traffic. That way Exchange will see the true IP address of the remote server. I haven't got my Kemp running at the moment so cannot look up the command... but someone else has blogged what needs to be done.

http://jaggudon.wordpress.com/2010/11/06/kemps-load-balancer-and-exchange-2010/

Simon.
0
Zacharia KurianAdministrator- Data Center & NetworkCommented:
You better disable SNAT in Kems and set default gateway on all Exchange Hub Transport Servers to Kemps.

This is the only option you can do and I don't think any other option would work for you.
0
swfwmd2Author Commented:
Thank you Simon for the reference document (Zacharia missed the step to check the Transparancy box on the LB configuration)

While I understand the reason for checking the Transparency box, I am not as clear about unchecking the Server NAT box.  Can you explain why this was checked in the first place (what benefit did it provide), why it needs to be unchecked for my purpose and what I will not be able to do with it unchecked?

As far as the redirecting the Default Gateway of the Real servers – with only two Exchange servers in this site with the Load Balancer (we have one other in another site for Backups and DR), is there any big benefit of setting this gateway to the Load Balancer or big problem if we do not?

Thank you,
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

swfwmd2Author Commented:
Disregad my last update -

Here is my current status:

I still cannot relay from the Load Balancer without putting in the IP of the Virtual Server in the Exchange receive connector.

I have done the following:
•      Checked to Transparency box on the LB

•      Unchecked the Server NAT

•      Added the Load Balancer’s Interface Address as the Default gateway on the Exchange servers


I have tested the Receive connector by successfully connecting directly to the Exchange server and able to relay but when I connect to the Load Balancer virtual IP for SMTP I cannot relay (I can relay from here if I add LB IP to Receive connector)
I can successfully send email to my inside address and when I look at the header of the email I see the IP of the LB SMTP virtual service and do not see the IP of the originating server.

Any suggestions?
0
Simon Butler (Sembee)ConsultantCommented:
The problem must still be with the KEMPs somewhere. The default gateway setting shouldn't have caused any problems. Have you spoken to KEMP support?

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
swfwmd2Author Commented:
The Kemp Tech Support told me:
"Transparency will not work properly for clients that are on the same subnet as the virutal service, and real server. The load balancer will selectively disable transparency for those connections as the gateway of the server will not be taken into account, it will try to directly return traffic to the other machine on its local subnet."

They have another option (which I am in process of testing)-

"The only way for these connections to be transparent is to use a layer 4 service and configure for Direct Server Return (DSR). This involves creating a loopback adapter on the server so it can respond directly to the client using the VS ip address. Documentation on how to do this can be found here https://support.kemptechnologies.com/hc/en-us/articles/202380328-Configuring-Real-Servers-for-Direct-Server-Return-DSR-"

Does anyone see any issues with this course of action?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

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.