Installed Exchange 2013 SP1 and configured in coexistence with existing SBS 2008/Ex 2007. All tested OK, mail flow OK, can migrated between etc. as per MS blog here:

http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx

Stopped at page 4 as says changes in Public Folder migration requirements when installing CU7 so thought best to at this point look into this and install latest CU (CU9).

This is the command as part of the steps on this blog I ran to create the receive connectors on the EX2013 machine:

New-ReceiveConnector -Name Inbound -Usage Custom -Bindings 192.168.10.3:25 -RemoteIPRanges 192.168.10.0-192.168.10.253,192.168.10.255-192.168.10.255

(This just matches the SBS2008 config)

During installation of CU9 it failed at step 10 with the following 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.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "*****EX01\Inbound". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
   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.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "BLSVREX01\Default Frontend BLSVREX01". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
   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)".

I am now unable to open OWA or ECP on the machine and any of the test mailboxes I have on there or have migrated to the EX2013 machine will not connect. Unsure how I can change the receive connector or what I am even meant to change it to... As said just believe I matched the existing config sans changing the listener address.

I cannot open the Exchange Management Shell on EX2013 machine either.

I've moved the mail. addresses DNS back to the SBS machine and will have to now also change all the web addresses back to mail. on there to ensure mail continues working for now. Really urgent I get this sorted.

• Edited by Allister Wade 2 20 hours 53 minutes ago

Hi 

Please find the reason for this error and the solution

Issue

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 wont 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

Open ADSI edit 

Go to Configuration, and drill down Services, Microsoft Exchange, First Organization, Administrative Groups, Exchange Administrative Groups, Servers, <Your Server Name>, Protocols, SMTP Receive Connectors

Find the offending connector and delete it.

Setup will resume as normal, and recreate the connector after setup completes.

Followed this:

http://social.technet.microsoft.com/wiki/contents/articles/25372.exchange-2013-setup-error-a-receive-connector-must-have-a-unique-combination-of-a-local-ip-address-port-bindings-and-remote-ip-address-ranges.aspx

Fixed thankfully and installed OK now, ECP and such up and running, client access OK again. Thew.

Not sure what went wrong.. Appears there is a default Receive Connecter set to every IP and port 25 and I guess that + my created one as per that guide were the issue.

The guide does say to create on port 24, so maybe they foresaw this and I was trying to hard to be clever or something. I just assumed port 24 was because they were talking about TMG and was something to do with that?

Edit - not fixed. Client access not working for the test accounts I moved to EX 2013 machine even after correcting the DNS. Prompts for credentials and on correct credentials tells me:

Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed."

Recreating the profiles of my test accounts seems to have resolved this but not very reassuring.

• Marked as answer by Allister Wade 2 20 hours 26 minutes ago
• Unmarked as answer by Allister Wade 2 20 hours 26 minutes ago
• Edited by Allister Wade 2 20 hours 18 minutes ago

Hi Sathish

Got to the same solution via Google but thanks for that.

Any chance you can advise RE the technet blog saying to use port 24 - do you think this is because of this issue or just something specific to them using TMG?