Microsoft Exchange Server has detected that Basic Authentication is being attempted between this server and server ‘%1’. This authentication mechanism is not secure and it is not supported between front-ends and back-ends. If this condition persists, please verify that server ‘%1’ is properly configured to use Integrated Windows Authentication for each virtual directory used by Exchange. After applying any changes it may be necessary to restart Internet Information Services on both the front-end and back-end servers.

Details
Product:	Exchange
Event ID:	1001
Source:	EXPROX
Version:	6.5.6940.0
Component:	Microsoft Exchange Proxy
Message:	Microsoft Exchange Server has detected that Basic Authentication is being attempted between this server and server ‘%1’. This authentication mechanism is not secure and it is not supported between front-ends and back-ends. If this condition persists, please verify that server ‘%1’ is properly configured to use Integrated Windows Authentication for each virtual directory used by Exchange. After applying any changes it may be necessary to restart Internet Information Services on both the front-end and back-end servers.

Explanation
This event may appear when both of the following conditions are true: Exchange 2003 servers are configured in a front-end/back-end configuration. The back-end Exchange 2003 server is configured to use only Basic authentication. The text of this message implies that both the front-end server and the back-end server must be configured to use Integrated Windows authentication. This is incorrect. Only the back-end Exchange 2003 server must be configured to use Integrated Windows authentication. The description of the event should read as follows: Microsoft Exchange Server has detected that Basic authentication is being attempted between this server and server %1. This authentication mechanism is not secure and it is not supported between front-end and back-end servers. If this condition persists, verify that server %1 is correctly configured to use Integrated Windows Authentication for each virtual directory used by Exchange. You may have to restart Internet Information Services on both the front-end and back-end servers after any changes are applied. For details, see the following articles in the Microsoft Knowledge Base: 832397 An incorrect event description for event ID 1001 appears on an Exchange Server 2003 front-end server 326985 HOW TO: Troubleshoot Kerberos-Related Issues in IIS

User Action
Verify that the back-end server listed in the event description is configured to use Integrated Windows authentication, and that all front-end servers are configured to use Basic Authentication. If any authentication method changes are made to the front-end or back-end servers, restart the IIS Admin service on the front-end and back-end servers.

Event ID 697 — Federation Service Authentication Web Pages
Event ID 124 — Windows NT Token-Based Application Configuration
Ports required for single sign-on to domain web server
The currently configured authentication provider failed to load and initialize successfully. %1
Microsoft Exchange Server has detected that NTLM-based authentication is presently being used between this server and server ‘%1′. NTLM is still a secure authentication mechanism and protects users’ credentials. However, this indicates that there may be a configuration issue preventing the use of Kerberos authentication. If this condition persists, please verify that server ‘%1’ is properly configured to use Kerberos authentication. After applying any changes it may be necessary to restart Internet Information Services on both the front-end and back-end servers.

Related:

Leave a Reply Cancel reply

Links