Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Maintenance: Recommended maintenance tasks for Windows servers|
The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is <server name>. The SSL connection request has failed. The attached data contains the server certificate.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is Schannel?
As per ME2275950, this may be recorded in certain conditions if the LDAP directory service is hosted on many nodes that are put behind a Network Load Balancing (NLB) server. The article provides details for a hotfix available.
EV100638 (MSTurnPing Bug) describes a similar scenario, with this event being generated by nodes in a NLB cluster when the MSTurnPing tool is used.
ME2282241 indicates that this problem occurs because of an error in Windows Vista and in Windows Server 2008. The LDAP client stores the node's canonical name into the alias field. This problem occurs if the node alias and the node name are different. See the article for information about a hotfix available.
When we set up our Outlook Web Access and tried to go into public folders on the Exchange system manager, we received an error about SSL certificate being invalid. The Certificate published to the public was for the server's public FQDN (different to the "real" name). When the SSL IIS was set up, the required secure channel tick box was ticked and applied to all child nodes. Unticking this box and letting this new setting filter down solved both problems.
ME324345 only applies to Windows 2000. After following the instructions in ME324345 without success on a Windows 2003 box, I found that to get rid of the error I had to first remove the certificate from the default website completely and then add it again. This cured the problem.
ME814662 provides information on this event.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated