I get lots of warnings 1035 MSExchangeFrontEndTransport, SmtpReceive. Receiving mail is no problem. Details:

Inbound authentication failed with error LogonDenied for Receive connector Client Frontend ITSPECSRV. The authentication mechanism is Login. The source IP address of the client who tried to authenticate to Microsoft Exchange is [::1].

Hi there,

could you perhaps tell me how the Receive connector is configured? (Permission Groups, authentication)?

thanks!

Michael

Hi Michael, Thanks for looking into this!

Authentication: TLS, Basic/After starting TLS, Integrated Windows

Permission groups: Exchange users

Anyone?

I had the same issue today with my first Exh 2013 install. Turned out that 'anonymous users' need to be allowed to connect to the receive connector or mail will get bounced.

This can be done from the 'Permission groups' section you refered to earlier in the thread.

I think this has always been the case and is a default MS security setup but it had been a long time since I'd set one up.

Regards,

Mike

Hi Mike,

As far as I know, no mail gets bounced.

I'll try allowing "anonymous users" anyway to find out if the errors go away.

Regards,

The warnings occur about every 15 minutes. They still do...

Hi Leo - have you found a solution to this? I am having the same issue on a fresh Exchange 2013 install (on Windows Server 2012) every 15 minutes.

Inbound authentication failed with error LogonDenied for Receive connector Client Frontend DC1. The authentication mechanism is Login. The source IP address of the client who tried to authenticate to Microsoft Exchange is [::1].

Unfortunately not. Things haven't changed. I only once had a mail receiving problem: the Transport service had stopped for no reason. Restarted it and things seem to be running fine except this and other warnings and errors.

Loe have you had any luck with this error, as I am experiecing the same issues on a new build

10010 warning

6002 warning

1035 warning

Unfortunately: not any. Last warnings/errors today:

ITSPECSRV	1035	Waarschuwing	MSExchangeFrontEndTransport	Application	19-3-2013 15:47:54
ITSPECSRV	10010	Waarschuwing	MSExchange Mid-Tier Storage	Application	19-3-2013 15:43:14
ITSPECSRV	10010	Waarschuwing	MSExchange Mid-Tier Storage	Application	19-3-2013 15:34:37
ITSPECSRV	1035	Waarschuwing	MSExchangeFrontEndTransport	Application	19-3-2013 15:32:53
ITSPECSRV	1050	Waarschuwing	MSExchange Extensibility	Application	19-3-2013 15:27:50
ITSPECSRV	10010	Waarschuwing	MSExchange Mid-Tier Storage	Application	19-3-2013 15:23:45
ITSPECSRV	10010	Waarschuwing	MSExchange Mid-Tier Storage	Application	19-3-2013 15:20:51
ITSPECSRV	10010	Waarschuwing	MSExchange Mid-Tier Storage	Application	19-3-2013 15:20:48
ITSPECSRV	10010	Waarschuwing	MSExchange Mid-Tier Storage	Application	19-3-2013 15:20:30
ITSPECSRV	6002	Waarschuwing	MSExchange Mid-Tier Storage	Application	19-3-2013 15:19:54
ITSPECSRV	1035	Waarschuwing	MSExchangeFrontEndTransport	Application	19-3-2013 15:17:53
ITSPECSRV	10010	Waarschuwing	MSExchange Mid-Tier Storage	Application	19-3-2013 15:16:04
ITSPECSRV	10010	Waarschuwing	MSExchange Mid-Tier Storage	Application	19-3-2013 15:15:02
ITSPECSRV	10010	Waarschuwing	MSExchange Mid-Tier Storage	Application	19-3-2013 15:13:44
ITSPECSRV	10010	Waarschuwing	MSExchange Mid-Tier Storage	Application	19-3-2013 15:12:18
ITSPECSRV	1035	Waarschuwing	MSExchangeFrontEndTransport	Application	19-3-2013 15:02:53

I'm getting these errors as well.

Going back through my logs they seem to have started after several "unexpected" shutdowns where I had a serious disk issue on the host machine (Exchange is running in a VM Guest).

I needed to do some repairs to the IIS config (WAS) to get it all working again, and ever since I get repeating entries for these errors. It seems like a lot of the Exchange health monitoring processes are now broken.

I'm not sure if these errors started because of the other problems, or just happened to start after some other change I made in the process of fixing them, but I haven't worked out how to stop them. They don't *seem* to be causing a problem, but that's hardly comforting.

I have this same issue since installing CU1 (I thought it was related, apparently not).  In our case I noticed that two security audit logs (4525) went along with it one denoting the server and the other a healthmailbox.  I worked with MS Support and we turned on logging for Kerberos (HKLM\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters, add a DWORD32 named LogLevel with a decimal value of 1 and then check the system event log... make sure to set it to 0 after).  There were tons of errors concerning the health mailboxes (0x6 KDC_ERR_C_PRINCIPAL_UNKNOWN and 0x12 KDC_ERR_CLIENT_REVOKED).  No answers yet, MS is still researching, if I get more info I'll post it.

This isn't resolved IMO but we disabled the Microsoft Exchange Health Manager service and the errors went away (as well as a bunch of 5011s I was having in the System log and had a separate ticket open on).  They said they will address it in the next patch.

These warnings seem to have gone after installing CU1.

I have same issue on CU1

i think u have too many front end connectors, deleting one may fix the errors.

hope it helps :)

I only have the default ones, so I'm quite sure that's not the problem.

i have the exact same Problem... ex 2013 cu 1 and only Default connectors.. a few times a day Exchange Drops the Connection to Outlook and i get a credential prompt. if i cancel , the Connection gets re-established in about 30 seconds but if that happens when writing an E-Mail (draft) , i cannot send that email and have to rebuild in in another E-Mail object. thats quite annoying.

has anyone got an idea?

If you are running Mailbox rolls & Client Rolls on the same server, you have most likely built a Hub Receive Connector for relay (for a photocopier say) and set the port to 25. In these dual rolls on a single Exchange Server the Frontend Receive Connectors use port 25 and the Hub Receive Connectors use port 2525.

Delete the Hub Receive connector you built and build a Frontend Receive Connector which use port 25 for the program/equipment that needs to relay.

It's now 1,5 years and 6 CUs later (CU7) and I'm having the same problem. 1035 Warning every 15 minutes and tons of 0x6 KDC_ERR_C_PRINCIPAL_UNKNOWN.

Any suggestions?

Found a solution at:

http://serverfault.com/questions/527404/users-unable-to-send-over-smtp-after-upgrade-to-exchange-2013?answertab=active#tab-top