FrontEnd Transport Service Listening 2525 Exchange 2013 CU3

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.
LVL 14
KutyiAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
KutyiAuthor Commented:
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
KutyiAuthor Commented:
It seams that Microsoft has fixed some issues with the FrontEnd Transport HUB with the newer updates.  Thanks for the help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.