I have an issue logged with MS now, but they aren't looking at them until Nov 9. System settings of the exchange 2010 servers show they are pointing to the correct DCs - but I still get this error accompanied with long delays in rendering windows in EMC. In a nutshell, LDAP is a language to talk to directory services, and Active Directory is one.
LDAP is one of the protocols that is used to create or query objects in Active Directory. It can be used for authentication, and/or storing information about network resources. We are not able to log into Outlook Web App either with authentication failed errors - and I can't help but expect these 2 issues are related? I tried hard coding the Configuration Domain Controller at the org level, as well as using the -staticdomaincontrollers and -staticglobalcatalogservers with the "Set-ExchangeServer" powershell command - no luck. Active Directory is a proprietary directory service developed by Microsoft. DNS has no record of it, nor is it located anywhere else. The server it is citing in the error has been retired - it was gracefully dcpromo'ed down and removed from the environment. This issue is driving us nuts - there are no issues with Domain Controllers or AD in this environment.
0 kommentar(er)
