Updating receive connector on Edge 2010 gets overwritten by TMG

I have a 2010 Edge box with TMG installed, and every time I change the IP ranges in the Receive Connector, it gets overwritten by TMG. As a workaround, I can stop the EdgeSync service in TMG and change the individual IP addresses, but I cannot add a range (I want to add a whole subnet).

What if I remove the receive connector completely and replace it with a new one with a different name? Would that still get overwritten by TMG?

Running Forefront TMG 2010 Service Pack 2, Exchange 2010 Service Pack 3 RU4     

January 20th, 2015 6:54pm

Hi,

Please check the thread below.

"When I stop the TMG Control service it does not get overriden, I also read somewhere that you can also disable the TMG / Exchange integration. What I am after is another receive connector on the edge server that will listen on another NIC with different security settings so it can relay mail from the management network - so far only got it to work while the TMG control service is stopped to stop it overriding it."

https://social.technet.microsoft.com/Forums/en-US/b049a950-6c8d-4965-b5c9-9f40505aa6bb/is-it-possible-to-create-an-addition-receive-connector-in-tmg-on-exchange-edge-server?forum=Forefrontedgegeneral

Best Regards,

Joyce

Free Windows Admin Tool Kit Click here and download it now
January 21st, 2015 11:06am

Joyce,

I have seen this, however do you leave the service stopped simplywhile you make the change, or permanently?

Thanks

January 21st, 2015 12:08pm

Have you seen this article? http://blogs.technet.com/b/yuridiogenes/archive/2010/04/02/unable-to-add-an-additional-ip-on-receive-connector-on-exchange-edge-when-using-e-mail-protection-feature-on-forefront-tmg-2010.aspx


Free Windows Admin Tool Kit Click here and download it now
January 27th, 2015 12:18am

This does not work for adding an IP range. You can only add individual hosts using this method.


I found that this is the best solution: 

http://blogs.technet.com/b/isablog/archive/2010/10/15/the-exchange-edge-default-receive-connector-gets-unexpectedly-disabled-even-though-the-email-policy-is-not-configured.aspx

  • Marked as answer by snorri788 Tuesday, January 27, 2015 9:07 AM
January 27th, 2015 12:07pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics