CU5 failed due to issues with receive connectors

Question

We have a CAS server (mail1, 10.1.0.26) and Mailbox server (mbx1, 10.1.0.25).  When I ran the update on the mailbox server, it failed with the following errors (see below).  The update completed successfully on the CAS server.  It appears
I have a problem with receive connectors.  I really could use some help please.  Thank you. -Glen
Here are the results of the Get-ReceiveConnector PS script:
Identity                                              
Bindings                                      Enabled
MBX1\Default MBX1                             {0.0.0.0:25}                               
True
MBX1\Client Proxy MBX1                       {10.1.255.26:25, 0.0.0.0:465}     True
MAIL1\Default Frontend MAIL1               {0.0.0.0:25}                              
True
MAIL1\Outbound Proxy Frontend MAIL1  {0.0.0.0:717}                              True
MAIL1\Client Frontend MAIL1                 {0.0.0.0:587}                            
 True
Here are snippets of the failure results:
The values that you specified for the bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MBX1\Client Proxy MBX1". A receive connector must have a unique combination of a local IP address & port bindings
and remote IP address ranges.  Change at lease one of these settings.
The values that you specified for the bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MBX1\Default MBX1". A receive connector must have a unique combination of a local IP address & port bindings and remote
IP address ranges.  Change at lease one of these settings.

Answer 1

Here's the full output from the failure messages:
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 "MBX1\Client Proxy MBX1". 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 "MBX1\Default MBX1". 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)".