Not much experience. I will do research and give feedback then.

I also ran a wireshark capture from the server running Replistor, but do not see any attempts to contact the Exchange server. All the while Replistor is generating more 10053 Send errors.

We searched error 10053 as the following error message from Windows(net helpmsg 10053).

One resolution is adding IP for the Source Exchange server to Connection Control. When SMTP Virtual Sever is set up for Connection Control. Connection Control will grant or deny access to this server using IP addresses or Internet domain names.

If you had proper permission. More detail link to http://solutions.emc.com/emcsolutionview.asp?id=esg103056.

Lu

I am running Exchange 2010. In Exchange 2010 "Receive Connectors" take the place of Connection Control which was used in Exchange 2003.

I did create a Receive Connector for the IP addresses of the servers running Replistor. I can send an email via telnet on port 25 from the servers, so I know that the connectors work. Just can't get the Replistor application to send the mail.

Does it require special authentication or use a port other than 25?

I also ran a wireshark capture from the server running Replistor, but do not see any attempts to contact the Exchange server. So that is strange as well.

Because Replistor go to EOL. The Exchange 2010 configuration is not update. But I already send the symptons to expert DL. I will update it if got feedback.

The other workaround for RepliStor 5.3 is restarting the RepliStor services including:

RepliStor Control Services

RepliStor Server

http://solutions.emc.com/emcsolutionview.asp?id=esg69435

Lu

Another suggestion from Engineer's team is upgrade to 6.4.2.9...available on powerlink. Then check if they will have SMTP issue.