Hi All
I have a 4 node DAG/multi role Exchange 2013 CU21 environment. I have been troubleshooting some performance issues with Outlook 2017 clients, mainly relating to slow performance and Outlook client disconnects.
I was delving into the Microsoft – Exchange Active Monitoring – ProbeResult logs and found 1 of my Exchange servers had a bunch of Outlook/RPC errors which to cut a long story short was due to an expired certificate that was bound to the backend default
website. I have fixed this now and seems to have cleared up a load of errors.
I notice I am still getting quite a few instances of the following:
Probe result (Name=OnPremisesInboundProxy_3)
No connection could be made because the target machine actively refused it 127.0.0.1:25
System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:25 at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SimpleSmtpClient.Connect(String
server, Int32 port, Boolean disconnectIfConnected) ………
I appear to be getting this for both FrontEnd and Hubtransport on all nodes
My Default Hubtransport receive connector does not have 127.0.0.1 added to the Remote Networks. It currently has ::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff and 0.0.0.0-255.255.255.255.
My Default Frontend receive connector is disabled entirely due to custom receive connectors being setup for External mail and internal relay.
Do I need to add 127.0.0.1 to these receive connectors? (and re-enable the default receive connector?)
OR
Is this referring to other Exchange servers trying to use the receive connectors? Each Exchange server has event log errs with result: OnPremisesInboundProxy ,OnPremisesInboundProxy_2 ,OnPremisesInboundProxy_3 and OnPremisesInboundProxy_4 errors.
Thanks!