Bug ID 756698: After upgrade, nlad may not create an schannel to a domain controller

Last Modified: Jan 20, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP APM, Install/Upgrade(all modules)

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1

Opened: Jan 27, 2019
Severity: 3-Major

Symptoms

Upgrading to v14.1.0 or later, the nlad daemon cannot create Microsoft Secure Channel (Schannel) connections to configured domain controllers after reboot. The system posts errors in the /var/log/apm logfile similar to the following: err eca[5290]: 0162000e:3: Failed to resolve DC FQDN (example.example.com), Name or service not known (-2).

Impact

NTLM authentication might fail for APM end users. No NTLM communication to back-end Domain Controller while nlad restarts.

Conditions

-- Upgrading the BIG-IP system to v14.1.0 or later. -- NTLM front-end authentication is configured.

Workaround

Run the following command to restart nlad: bigstart restart nlad eca

Fix Information

None

Behavior Change