Solved

FrontEnd Transport Service Listening 2525 Exchange 2013 CU3

Posted on 2014-09-27
3
1,328 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 40347725
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
ID: 40347752
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
ID: 40463286
It seams that Microsoft has fixed some issues with the FrontEnd Transport HUB with the newer updates.  Thanks for the help.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
In this video we show how to create a Shared Mailbox 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 Recipients >> Sha…
This video discusses moving either the default database or any database to a new volume.

724 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