This Rule generates alerts when An LDAP server did not respond
An LDAP server did not respond.
The name of the server may be incorrect.
The name of server may not be resolvable by DNS to the correct IP address.
The server may not be physically reachable.
A required service may not running on the server.
If a secure connection is required, an appropriate Secure Sockets Layer (SSL) server certificate may not be installed on the LDAP server, or the root certificate for the certification authority (CA) that issued the SSL server certificate on the LDAP server may not be installed on the TMG Server computer.
The credentials used to connect to the LDAP server to verify the status and change the password of an account may be rejected by the server.
In TMG Server Management, click General, click Define LDAP and RADIUS Servers, and on the LDAP Servers tab, use the Edit button to modify the name and other properties of the LDAP server as required.
Use the nslookup command to verify that server name is resolvable by DNS to the correct IP address.
Use the ping and telnet commands to verify that the server can be reached.
Verify that the required services are running on the LDAP server.
Verify that an SSL server certificate is installed on the LDAP server and that the root certificate for the certification authority (CA) that issued the SSL server certificate on the LDAP server is installed on the TMG Server computer.
Verify that the credentials used to connect to the LDAP server to verify the status and change the password of an account are correct.
Target | Microsoft.Forefront.TMG.Publishing.ServerComponent |
Category | EventCollection |
Enabled | True |
Alert Generate | False |
Remotable | True |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Forefront.TMG.Rule.AlertGenerate.DS | Default |
WA | WriteAction | Microsoft.Forefront.TMG.Rule.AlertGenerate.WA | Default |
<Rule ID="Microsoft.Forefront.TMG.An_LDAP_server_did_not_respond.Rule" Enabled="true" Target="Microsoft.Forefront.TMG.Publishing.ServerComponent" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="DS" TypeID="Microsoft.Forefront.TMG.Rule.AlertGenerate.DS">
<ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Application</LogName>
<EventsPattern>^(21286)$</EventsPattern>
<EventType>2</EventType>
<SourcePattern>Microsoft Forefront TMG Web Proxy</SourcePattern>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="WA" TypeID="Microsoft.Forefront.TMG.Rule.AlertGenerate.WA">
<AlertMessageId>$MPElement[Name="Microsoft.Forefront.TMG.An_LDAP_server_did_not_respond.AlertMessage"]$</AlertMessageId>
<DomainName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/DomainDnsName$</DomainName>
<Priority>1</Priority>
<Severity>2</Severity>
</WriteAction>
</WriteActions>
</Rule>