I am trying to do an Exchange 2007 to 2013 migration. Before doing all the final repointing of DNS and proxying clients, I just want to make sure that the new Exchange 2013 is healthy. So I run a Get-HealthReport and it shows both the Online states of HubTransport and FrontendTransport as Unhealthy.
In the event logs under Microsoft>Exchange>ManagedAvailability>Monitoring I see Error events for them about the client submission probe failed x times over 15 minutes. No connection because the target machine actively refused it 127.0.0.1:587. There was also another one that said Unable to relay. For the Hub Transport it does not give as detailed information. It just says The HubAvailibilityProbe has failed 5 or more times in 15 minutes. Last failing server: ".
So it would sound like a connectivity problem, so with TELNET I tried to connect to port 25 and I get this:
telnet 127.0.0.1 25
421 4.3.2 Service not available
BUT if I put the hostname instead of 127.0.0.1, I get the 220 EMAIL.domain.com Microsoft ESMTP MAIL Service ready.
I tried temporarily disabling the windows firewall and its the same problem. I know SMTP is running because from another machine I can telnet to the mail server on port 25 and I get the SMTP banner.
So for me it seems like the Managed Availability is trying to use the IP address of 127.0.0.1 and that fails fundamentally for me when I try that in the command line, so no wonder why its marking the FrontendTransport as unhealthy. How can I resolve this? I would think a resolution would be either somehow allow 127.0.0.1 access to relay which I DID put in my Frontend Transport receive connector, but it made no difference. Or the other option is somehow configure the probe to use the hostname instead of 127.0.0.1.
As far as the HubTransport being unhealthy, I have a feeling its the same type of issue, but I am not seeing as detailed information in this path of the Event Viewer.
