We recently had a Project to deploy an Active Directory Manager ASP.NET application.
Everything works in SIT environment, but when deployed to Client (secure) UAT environment, Everything fails.
What we learned.
1. Use TCPView or 'NetStat-o' on the AD server to tell which ports are called by the Web app, and get the Infra engineers to open.
2. .NET method of creating account, works only once which requires app-pool recycle. (could be because of windows server 2003, and ,NET) version. When dealing with AD using .NET, i found there the errors return may not lead you to a solution
3. We reverted to calling AD using LDAP method and found that port 389 and 636 are needed to be open
4. Also service account given need to have 'Account Operator' rights inorder for us to set-password.
No comments:
Post a Comment