Understanding DFSR debug logging (Part 18: LDAP queries failing due to network (uses debug severity 5))

2009-04-08

In this scenario we will see a DFSR server attempt to contact its DC through LDAP to read the current replication topology. LDAP lookups are being blocked by ‘firewall/network/DC down’ so there are no responses.

(ldapblocked - Dfsr00008 - 2008.log)

These are two Windows Server 2008 servers called 2008x86SRV10 and 2008x64FSDC01 in the contoso.com ___domain. The log is from 2008x86SRV10 where the file is created. The other server is a ___domain controller. Review scenario “Domain Controller Bind and Configuration Polling on Windows Server 2008”.

<Upstream> 20080908 11:19:23.236 3940 CFAD 2159 [ERROR] Config::AdQuery::Search Failed to ldap_search_ext_s(). Error:Server Down base:CN=2008X86FSRV10,CN=Computers,DC=contoso,DC=com ß ___domain controller is not responding to an LDAP search request for the sending computer’s own DN

<Upstream> 20080908 11:19:23.236 3940 CFAD 8456 Config::AdConfig::IsConnected Lost connection to AD. Error:

+ [Error:58(0x3a) Config::AdQuery::StartSearch ad.cpp:2261 3940 W The specified server cannot perform the requested operation.] ß it’s important to note that DC connectivity errors will not all be LDAP-only. This error 58 is a WINERROR.H translated to “The specified server cannot perform the requested operation” with err.exe

+ [Error:58(0x3a) Config::AdQuery::StartSearch ad.cpp:2204 3940 W The specified server cannot perform the requested operation.]

+ [Error:58(0x3a) Config::AdQuery::Search ad.cpp:2169 3940 W The specified server cannot perform the requested operation.]

+ [Error:81(0x51) Config::AdQuery::Search ad.cpp:2169 3940 U Server Down] ß the other extended error is actually an LDAP error that will translate with err.exe to LDAP_SERVER_DOWN in WINLDAP.H

<Upstream> 20080908 11:19:42.174 3940 CFAD 317 Config::AdConnection::Connect Binding to dcAddr:\10.10.0.101 dcDnsName:\2008x64FDC01.contoso.com ß this is the DC where the LDAP bind is being attempted against. It returns both IP and DNS name.

<Upstream> 20080908 11:19:42.174 3940 CFAD 149 Config::AdConnection::BindToAd Trying to connect. hostName:2008x64FDC01.contoso.com

<Upstream> 20080908 11:20:03.175 3940 CFAD 3021 [ERROR] Config::AdSession::Connect Failed to ldap_connect(). timeout:30 Error:Server Down

<Upstream> 20080908 11:20:03.175 3940 CFAD 179 [ERROR] Config::AdConnection::BindToAd Failed to bind to AD. Error:[Error:58(0x3a) Config::AdSession::Connect ad.cpp:3027 3940 W The specified server cannot perform the requested operation.]

<Upstream> 20080908 11:20:03.175 3940 CFAD 149 Config::AdConnection::BindToAd Trying to connect. hostName:10.10.0.101

<Upstream> 20080908 11:20:24.192 3940 CFAD 3021 [ERROR] Config::AdSession::Connect Failed to ldap_connect(). timeout:30 Error:Server Down

<Upstream> 20080908 11:20:24.192 3940 CFAD 179 [ERROR] Config::AdConnection::BindToAd Failed to bind to AD. Error:[Error:58(0x3a) Config::AdSession::Connect ad.cpp:3027 3940 W The specified server cannot perform the requested operation.]

<Upstream> 20080908 11:20:24.192 3940 SCFG 1888 [WARN] ServiceConfig::DsPollIsDue Failed to enable lightweight polling. Error:

+ [Error:160(0xa0) Config::AdConfig::ConnectToLocalDc ad.cpp:8326 3940 W One or more arguments are not correct.] ß misleading error, the previous LDAP failure caused another operation to return this error

+ [Error:160(0xa0) Config::AdConfig::Connect ad.cpp:8077 3940 W One or more arguments are not correct.]

+ [Error:160(0xa0) Config::AdConnection::Connect adconnection.cpp:365 3940 W One or more arguments are not correct.]

+ [Error:160(0xa0) Config::AdConnection::BindToAd adconnection.cpp:184 3940 W One or more arguments are not correct.]

- Ned Pyle

Share via

Understanding DFSR debug logging (Part 18: LDAP queries failing due to network (uses debug severity 5))

Additional resources