Solved

FrontEnd Transport Service Listening 2525 Exchange 2013 CU3

Posted on 2014-09-27
3
1,109 Views
Last Modified: 2014-11-24
Hello,

I have a multi-role Exchange 2013 CU3 Server running on a Windows 2012 r2 Standard VM.  I have been having issues with intermittent mail flow.  When mail stops I need to restart the server to have mail flow again.  I had put in a custom receive connector to allow internal devices, photocopiers, custom apps etc, to send mail out.  It was configured as a FrontendTransport connector.   It worked well for months, then I started having issues.  After performing a Get-ServerHealth I see that the FrontEnd Transport is unhealthy (OnPremisesInbound... and OnPremisesSmtpCli...).  After performing a Netstat -aon I see that the FrontEnd Transport PID is listening on 2525 along with the HubTransport PID.  Going over my receive connectors in both EAC and PowerShell they show that none of my FrontEnd connectors are listening on 2525.  I am fairly confident that because the two services are listening on 2525 this is causing my mail flow issues, but I can't see where to fix it.  Any help would be greatly appreciated.
0
Comment
Question by:Kutyi
  • 2
3 Comments
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
Comment Utility
First - you are on a non-supported platform.
Exchange 2013 CU3 is out of support, and was never supported on Windows 2012 R2.

Therefore you need to upgrade your server to at least Exchange 2013 SP1, preferably something higher.

The default Receive Connectors listen on port 2525. You should have two lots of connectors.
I am pretty sure they will share the same PID because they are both from the MS Exchange Transport Service.

I would start by upgrading your server to begin with - no keeping Exchange 2013 up to date is no longer an option.

Simon.
0
 
LVL 14

Author Comment

by:Kutyi
Comment Utility
I am planning the upgrade to CU5, I have a custom app that does not support CU6 yet, but wanted my server in optimal health prior to the upgrade.  I could not find anything in release notes discussing the connectors so did not draw a line between the two.  I will perform an up grade then, hopefully this weekend, or perhaps next depending on users.  I will post back when I have done the upgrade.  Hopefully then I can re-add my FrontEnd Transport connector to support my internal apps and devices.
0
 
LVL 14

Author Closing Comment

by:Kutyi
Comment Utility
It seams that Microsoft has fixed some issues with the FrontEnd Transport HUB with the newer updates.  Thanks for the help.
0

Featured Post

Want to promote your upcoming event?

Is your company attending an event or exhibiting at a trade show soon? Are you speaking at a conference? Spread the word by using a promotional banner in your email signature. This will ensure your organization’s most important contacts are in the know.

Join & Write a Comment

"Migrate" an SMTP relay receive connector to a new server using info from an old server.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
how to add IIS SMTP to handle application/Scanner relays into office 365.

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now