Exchange 2013: 421 4.3.2 Service not available

Mashing the gears of emailThere appears to be a bug in 2013 (inc. CU1) where the transport stops receiving connections with this error. In my case I have the FE role on the mailbox server, and also have a custom (hub transport) receive connector for apps (tighter scope), so have 6 receive connectors:

  • Client proxy | Bindings :::465, | RemoteIPRanges: All
  • Default | Bindings :::2525, | RemoteIPRanges: All
  • Default Frontend  | Bindings :::25, | RemoteIPRanges: All
  • Outbound Proxy Frontend  | Bindings :::717, | RemoteIPRanges: All
  • Client Frontend  | Bindings :::587, | RemoteIPRanges: All
  • Custom (anonymous allowed)  | Bindings | RemoteIPRanges: <specific IP of app servers

There are various discussions on the forums, many with snake-tonic solutions. Currently trying out one with setting the binding on the default receive connector (for internal relay on 2525) to the specific IP address of the server.

Problem is that the problem can occur anything from a few hours to days / weeks, with no reliable repro. Will try to remember to update this post if I see a reliable fix.

This entry was posted in Aide memoire, Email, Exchange 2013. Bookmark the permalink.

4 Responses to Exchange 2013: 421 4.3.2 Service not available

  1. Ronald Boyce says:

    We are experiencing the same issues are you are. Have you come accross a fix yet? Please post, thanks

    • timcoveney says:

      Not yet I’m afraid – thought it was gone with CU2, but no; up it came again the other day. Glad I’m only working in a lab with this…

      • Ronald Boyce says:

        Were going to open a case with MSoft.. Cant beleive there are this many people with this issue and there is no cure yet!

      • timcoveney says:

        Good luck – if you remember, please let me know what the solution was – I’ve seen quite a few out there like disabling the Malware agent and using front-end transport receive connectors rather than hub transport receive connectors, but these don’t really work for me… I thought it might be a memory thing, but I just increased the RAM from 16GB to 28GB (Dell PowerEdge 1950) and same thing has happened…

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s