Quantcast
Channel: Exchange Server 2013 - Mail Flow and Secure Messaging forum
Viewing all articles
Browse latest Browse all 4249

FIXED - Exchange 2013 - Can I Recreate Default Frontend Receive Connector SAFELY?

$
0
0

Hi

I'm need of some urgent assistance please.

I had a fully functional Exchange 2013 server and decided to create a receive connector for a photocopier/scanner to included its static IP  port number 25.

I accidentally chose Hub Transport role and not FrontEndTransport role which appears to have messed up port 25 connectivity on mail coming in from the internet. When I stopped and restarted the Transport Service within services.msc I then got this error.

Source: MSExchangeTransport
Event ID: 1036
Task Category: SmtpReceive
Level: Error

Description: Inbound direct trust authentication failed for certificate %1. The source IP address of the server that tried to authenticate to Microsoft Exchange is [%2]. Make sure EdgeSync is running properly.

I proceeded to delete the offending Receive connector for the scanner/photocopier and restart the server,  the transport service started ok this time but still I cant receive mail from the outside world.

My question: Can I delete the automatically created default Frontend "servername" connector which contains the proper settings then recreate it again with the same settings and NOT harm/delete all the users emails or the mailstore or anything bad for that matter?

I have the details on how to create the connector but just wanted to check that's its ok to remove it and re-add it again now that everything was setup and running fine. I'm hoping the recreated Connector will fix what I broke.

Appears what I have done has broken my connectivity to telnet to port 25 to the exchange server from the outside world although oddly I can telnet to the server from a command prompt on the exchange server (telnet "servername" 25) and getpresented with the exchange server responding. The tickbox for anonymous is ticked already. Port 25 already is forwarded from the firewall to the exchange server and was working fine till I made the error.

Any help is greatly appreciated. Thankyou.





Viewing all articles
Browse latest Browse all 4249

Trending Articles