Start a Conversation

Unsolved

This post is more than 5 years old

1754

December 12th, 2011 13:00

Replistor receive connector on Exchange 2010

We are running EMC Replictor 6.2.4.4

I am changing email notifications to point from our old Notes server to Exchange 2010.  I created a receive connector with TLS and Externally secured authentication and Anonymous/Exchange Servers permissions.

I get an error "An error was received on the connection to the mail server - Send Error - 10053."

I can send an email via telnet on port 25. Just can't get Replistor to send the mail.  Looking for assistance in troubleshooting the application sending mail.

161 Posts

December 12th, 2011 17:00

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

4 Posts

December 13th, 2011 05:00

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.

161 Posts

December 13th, 2011 19:00

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

4 Posts

December 14th, 2011 12:00

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.

161 Posts

December 14th, 2011 17:00

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

161 Posts

December 15th, 2011 01:00

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

No Events found!

Top