Hi BWH_Administrator,
Different event IDs could be caused by different factors, therefore, to narrow down the issue, please try checking the following aspects:
=======================
Event ID 364:
Possible causes:
- The time difference between the ADFS proxy and the ADFS server is too big (should be synchronized as close together as possible - manually or via Win32Time).
- The SSL certificate of either the ADFS proxy or the ADFS server is failing revocation checking on either side (standard PKI troubleshooting applies).
- The SSL certificate of either the ADFS proxy or the ADFS server is unable to chain up to a Trusted Root on either side (verify all CA certificates in the chain are installed in the personal store of the application pool service account).
========================
Event ID 218:
Possible cause: This could mean that the AD FS 2.0 Windows Service is not started on the federation server computer.
Resolution: Verify that the AD FS 2.0 Windows service is running on the remote federation server computer, and that the remote federation server is reachable. For more information, see Verify that AD FS is installed and running and Verify network connectivity.
========================
Event ID 230:
Possible causes:
- The internal AD FS 2.x Federation Server is overloaded with requests.
- The AD FS 2.x Proxy server is overloaded with requests.
- There is a network issue occurring between the AD FS 2.x Proxy server and the internal AD FS 2.x Federation Server.
Resolution: Please refer to http://social.technet.microsoft.com/wiki/contents/articles/19057.ad-fs-2-x-troubleshooting-proxy-server-event-id-230-congestion-avoidance-algorithm.aspx to troubleshoot the issue.
For more details, please refer to the links below:
ADFS Event ID 364 on ADFS 2.0 proxy
AD FS 2.0 + Federation Proxy + Unsecured or incorrectly secured fault errors
Troubleshooting federation server proxy problems with AD FS 2.0
AD FS 2.x: Troubleshooting Proxy Server Event ID 230 (Congestion Avoidance Algorithm)
