Hi,

i need assistance in trying to resolve an ID 1035 event on a fresh install of Exchange 2013 CU7

Inbound authentication failed with error LogonDenied for Receive connector Default SERVERNAME. The authentication mechanism is Login. The source IP address of the client who tried to authenticate to Microsoft Exchange is [127.0.0.1].

This event is logged every 15 minutes, and appeared the first time after setting up the send connector and external addresses / virtual directories. There are currently no clients connecting to the server.

I'Ve spend hours in digging through Technet and other ressources. This seem to be a very common issue, unfortunately no solution could fix it with me. Some of te suggestions were: Add anonymous access to connector (did not work), too much receive connectors, delete some (huh? Without loosing functionality), mixed up ports in hub transport when client access role and post office role is installed on the same server (which is, but there seem to be any faults with the ports. Also no additional revceive connectors were installed, just the default ones).

Best hint ever was "Just ignore it, thats the price you've to pay when using unfinished software". However, I want my log to be clean. So I would appreciate any help in getting rid of this warning.

Best regards
Holger

Edit: I forgot to mention that, after the same configuration step, lots of health sets became unhealthy. Meanwhile I've found HealthMailbox[...]@domain.com producing Kerberos Error 0x6 KDC_ERR_C_PRINCIPAL_UNKNOWN. Maybe this is all related.

• Edited by Holger Keil 1 hour 2 minutes ago

Disabling the health manager service as written in another froums thread removes the kerberos errors as well as the receive connector errors, however removes the health check as well, so this could finally not be a solution. My best guess is, that all the mentioned "unhealthy" services are indeed not unhealthy but simply could not be probed due to the authentication error. The question is: Why did this happen suddenly after configuring mailflow and client access as described in  Exchange 2013 post installation tasks.

Before completing this steps, all HealthSets reported "Healthy" (except of Network, but this is another issue) and there were no 1035 warnings logged as well (didn't had Kerberos logging enabled at this time, but I guess those HealthManagerService-induced errors didn't happen).