App Volumes Active Directory error mesages

[mathewdsa]

Our App Volumes manager has many system messages going back several days about failure to connect to AD.
Users are still getting attached writable and we can search users to assign new writable volumes.
The AD account is also used by a different App Vol manager for a second site but same AD domain. That App Vol manager does not have the messages.
Both managers serve VDI Horizon users via individual vcenters.
We need to resolve the AD connection messages on the App Vol manager that has this message.

[Mickeybyte]

@mathewdsa 

Could you give an example of those error messages? 

I remember seeing messages like "invalid credentials" showing up in the log after setting up LDAPS or LDAP over TLS instead of LDAP (insecure) I think in the AD configuration in AppVolumes.

[mathewdsa]

I'm seeing things like:

• Unable to connect to Active Directory 
• No connected adapter was found
• Active Directory error:A connection attempt failed because the connected party did not properly respond after a period of time, xxx-user specified timeout. 

[Mickeybyte]

@mathewdsa 

That's not what I've seen before when using LDAPS. There must be a different cause for those errors. 

Please compare the AD configuration between both sites to see if you can find any difference. Also re-enter the password for the AD bind account. 

Guessing from the errors, also check if the AppVolumes managers have access to the AD servers (firewalls?).

[mathewdsa · Accepted solution]

We were given a KB to follow to disable NTLM:

Disable Microsoft Windows NTLM Authentication (vmware.com)

Now under observation.