Exchange Server Share

… Information sharing on Exchange Server …

Exchange 2013 – Setup Error: A Receive connector must have a unique combination of a local IP address & port bindings and remote IP address ranges

avatarYou may get an error while Exchange setup checks Receive Connectors for local IP address/port bindings and remote IP address ranges for the server where you are installing Cumulative Update. This error would come up at “Mailbox Role: Transport Service” step of setup/update process. Here is the detailed error message.

 Error:

Error:
The following error was generated when "$error.Clear();
 $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
 foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };
 " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ConnectorMappingConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "EX2013\Incoming from Internet - Dummy". A Receive connector must have a unique combination of a local IP address & port bindings and remote IP address ranges. Change at least one of these values.
 at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
 at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
 at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
 at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
 at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Error:
The following error was generated when "$error.Clear();
 $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
 foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };
 " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ConnectorMappingConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "EX2013\Default Frontend EX2013". A Receive connector must have a unique combination of a local IP address & port bindings and remote IP address ranges. Change at least one of these values.
 at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
 at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
 at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
 at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
 at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

RemoteIPError1

Explanation:

You can not have same values of Local IP Address:Port bindings and Remote IP Address Range both on two Receive Connectors so essentially you have to change anyone of these on one of the Receive Connector.

Now problem is you won’t be able to open Exchange Admin Center (EAC) or Exchange Management Shell (EMS) to modify Local IP Address:Port Bindings or Remote IP Address Ranges on one of these receive connectors.

Solution:

Exchange saves configuration information in Configuration Partition of Active Directory so you can use any AD Editor like ADSIEdit.msc or ADExplorer.exe to modify this value. (Be careful while using these raw AD Editors!)

  • Open ADSIEDIT.MSC.
  • Navigate to the following location: CN=SMTP Receive Connectors,CN=Protocols,CN=<ExServerName>,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=<ExOrg Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<DomainName>,CN=Com
  • Right-click one of the Receive Connector which is showing up in error and then click Properties. (It is recommend to modify the Receive Connector created manually and not the “Default Frontend ServerName” connector.)

Now change the value of either msExchSmtpReceiveRemoteIPRanges or msExchSmtpReceiveBindings following below setps.

  • Locate the msExchSmtpReceiveRemoteIPRanges attribute. This attribute stores values for Remote Network Settings that you see in EAC.
  • Remove the values here and add some unique IP address or IP Range back.

RemoteIPError2

 

OR

  • Locate the msExchSmtpReceiveBindings attribute. This attribute stores value of Network adapter bindings that you see in EAC.
  • Remove the values here and add them back with different Port instead of 25.

RemoteIPError3

Personally I would prefer to change msExchSmtpReceiveRemoteIPRanges and give some unique IP or IP range.

After this Exchange 2013 Cumulative Update installation goes fine!

Written by Amit Tank

July 14, 2014 at 10:02 pm

46 Responses

Subscribe to comments with RSS.

  1. Ran into this issue with CU5 upgrade after migrating all connectors from Exchange 2010 to our 2013 server. This was a LIFE SAVER at 3am – worked perfectly

    Tony

    August 6, 2014 at 9:55 am

  2. thanks a million really helped me out

    Yaasin

    August 12, 2014 at 11:28 am

  3. Saved the day for me! thanks a lot buddy !!! keep up the good work!

    Igor

    August 18, 2014 at 4:31 pm

  4. Life saved at 4AM. Thanks a lot.

    Erny

    August 19, 2014 at 3:27 pm

  5. massive help! thanks

    Will

    August 21, 2014 at 3:45 am

  6. Reblogged this on ig0rski and commented:
    Rwally usefull

    spootnikb

    August 27, 2014 at 8:25 am

  7. Another life saved here! FYI: this occurred with CU 6. THANKS SO MUCH!

    Mike

    September 5, 2014 at 9:14 pm

    • Awesome, glad that helped you on CU6 too… Thanks for notifying…

      Amit Tank

      September 5, 2014 at 9:17 pm

    • Great Work !!! Thanks Amit🙂

      Harry

      September 9, 2014 at 7:23 am

  8. hello, sorry but when i go to adsiedit, i do not see the services folder. do let me know if i need to enable something or if i am missing some steps..

    jheycie

    September 13, 2014 at 6:32 am

  9. found it, thanks~~

    jheycie

    September 13, 2014 at 8:59 am

  10. Many thanks, I save a lot time

    José

    September 15, 2014 at 5:23 pm

  11. Another big thanks for microsoft!

    Lazka

    September 25, 2014 at 8:18 am

  12. Hello, the whole thing is going fine here and ofcourse every one is sharing facts, that’s in fact
    good, keep up writing.

    exploits

    September 26, 2014 at 11:41 pm

  13. not installed CU5 yet(!) do you think this might be the case if I’m setting up a new receive connector? I’m getting the same error

    Katiehh

    October 1, 2014 at 5:19 am

    • Yes, in latest CU’s this check is there even when you create new connector, it checks both of the things with existing connector and complains to give another port or IP range….

      Amit Tank

      October 3, 2014 at 8:20 pm

  14. easiest way just to delete wrong ones

    Didey

    October 9, 2014 at 11:34 am

    • Agree Didey, and just recreate with different port/ip range after upgrade….

      Amit Tank

      October 11, 2014 at 10:53 pm

  15. after applying the second method (modify port to 24 in place of 25) to CU6 i got the error on eac: HTTP Error 500.0 – Internal Server Error

    and users (outlook) are still deconnected!

    ELT

    October 11, 2014 at 9:31 am

    • Hello ELT, Receive connector and HTTP are totally different things. Receive connector modification couldn’t cause issue with EAC or IIS virtual directories. It would be something else…

      Amit Tank

      October 11, 2014 at 11:02 pm

  16. You’re right Amit, it’s OK now it was problem of rights solved here –> http://www.outlook-web-app.com/owa-2013/owa-2013-faq/615-logging-into-owa-fails-after-upgrading-to-exchange-2013-cu2

    Thank you a lot!!!!

    ELT

    October 13, 2014 at 6:42 am

  17. Hey there, You’ve done a fantastic job. I will definitely digg it and personally recommend
    to my friends. I’m sure they will be benefited from this web site.

    wordpress.com

    October 21, 2014 at 5:10 am

  18. Yesss, thnx a LOT!

    Kevin

    October 31, 2014 at 9:07 am

  19. Another live saved… Thanks a million.
    Update from CU2 to CU6…

    SuperTrooper

    November 4, 2014 at 6:24 pm

  20. Update from CU2 to CU6… thanks for this page. saved my day

    Thomas H

    November 22, 2014 at 9:36 am

  21. thanks for this post, I passed the installation after change 25 port into custom port🙂

    ichwanzo

    November 26, 2014 at 12:25 pm

  22. You da man… I deleted the bad connector, as the two methods you had didn’t work, this saved me!

    Yois

    December 16, 2014 at 9:13 pm

    • BTW, this was for CU7 on 2013

      Yois

      December 16, 2014 at 9:14 pm

  23. Same here, CU7 on 2013 cu3 – deleted wrongly configured connector (relay hub transport with public IP customer site) giving another ip or – range did not work, same error.
    Thanks a lot !!!!

    Sander Dercksen

    January 8, 2015 at 12:36 pm

  24. Mate, thanks for sharing this.. it was obvious when i read through the error, but at midnight you seem to loose logic, thanks again it saved me a bunch..

    Troy D

    March 3, 2015 at 7:43 pm

  25. Thanks from me also – CU7 applying found a conflicting receive connector that hadn’t been causing an issue otherwise – touchy little blighter !🙂

    You explained things really well, thanks for your time.

    Stu

    March 30, 2015 at 12:05 pm

  26. Great Post!!

    Ward Vissers

    April 11, 2015 at 9:55 am

    • Saved my day!!! Great work and thanks for the great post! (RTM -> CU8)
      Deleting the Connectors worked for me!

      dermiesi

      April 28, 2015 at 7:09 am

  27. Saved the day for me! thanks a lot buddy ! You are the best!

    maevrick

    May 22, 2015 at 5:06 am

  28. Hello Amit, you save my live. Before I check your solution I was thinking to import a 15 days old export of my Exchange VM, the problem is that the Cumulative Update (CU8 in my case) change Active Directory entries and this would have forced to restore a backup of the AD (crazy task for me).

    Deleting the connectors worked for me!

    Thanks for all.

    itpref

    May 27, 2015 at 6:00 am


Comments are closed.

%d bloggers like this: