We help IT Professionals succeed at work.

Exchange server not receiving 550.5.7.1 error- cannot receive emails but can send out no problem

Jeff Everett
Jeff Everett used Ask the Experts™
on
OK all, this is truly boggling to a few experienced people in my reach as well as myself. All of a sudden my Exchange server 2010 stopped receiving emails. I can send out just fine except from my SQL server receipt email to customers. I have done a telnet test, it shows my ports working. I have added the users to the Exchange Management Console 2010 , now I am wondering do they need 'roles' or permissions to relay the messages? OR to accept the messages? (Accepting/receiving is the issue)  Do I need to open port 587 instead of using port 25? If so do I need to remove one of the ports form the properties of the receive connector? None of my users are able to receive but all of them can send out. Also on the SQL side I cannot even send a 'test' email out from the SQL Studio in the Database Management console.  Calling all Exchange Experts!

This is the error I get when trying to add port 587 where I read can be used for receiving.

(PID 6324, Thread 43) Task Set-ReceiveConnector writing error when processing record of index 0. Error: Microsoft.Exchange.Management.SystemConfigurationTasks.ConnectorMappingConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "SERVER1\Default SERVER1". 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.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Author

Commented:
I think I have tracked this down to add to the above original post. This is a 'state 14' error I believe. I still do not know what to do Expert Exchange feedback is needed!
AmitIT Architect
Distinguished Expert 2017
Commented:
As error says, conflict. You need to specify unique values. Check IP first. Change it and see if that works.
IT Architect
Distinguished Expert 2017
Commented:
Before you make any changes, can you enable Anonymous Internet Receive Connector

Author

Commented:
I have done this and did a reboot. I will try changing the ip as you suggested if the last solution fails. Its a state 14 error and maybe complicated. I will keep you posted after the server comes back up and I get a bit of lunch!

Author

Commented:
Both were great examples of where to start. Unfortunately for my instance it didnt work. The reason for my grade of A is according to my Exchange Guru this would have more than likely fixed a good portion of the issues. The Exchange server was not configured properly from the start. It has been abandon and laid to rest for the second version of my site.