cswebdev
asked on
DirectoryEntry Error "The server is not operational"
I have an interesting issue. Our authentication and security setting is done from ASP.NET via an LDAP query into AD. We use the System.DirectoryServices namespace for this. Also, we retrieve user's roles from Authorization Manger using the Azroles interface.
This morning, the servers on our web farm were suddenly unable to query AD. The message we were getting back was "the server is not operational". We had a production move yesterday, but it was more configuration oriented and no code changed in our login routine. Also, users were able to log in successfully yesterday afternoon and this morning until 11:00 a.m. CST.
Our tech guys rebooted both domain controllers and after a while, I thought I'd try logging in again, and I was able to do it just fine!!
Is it possible that AD was overwhelmed with queries from our login application and just shut itself down to additional queries? We do a look-up to retrieve the user's distinguished name and then Azman has two scripts containing LDAP queries that are fired multiple times per user login. I'm wondering if it got bombarded with too many requests.
Any insight or places for us to look for answers are appreciated. The event logs on our DC and web servers haven't really yielded much.
Regards,
Ryan
This morning, the servers on our web farm were suddenly unable to query AD. The message we were getting back was "the server is not operational". We had a production move yesterday, but it was more configuration oriented and no code changed in our login routine. Also, users were able to log in successfully yesterday afternoon and this morning until 11:00 a.m. CST.
Our tech guys rebooted both domain controllers and after a while, I thought I'd try logging in again, and I was able to do it just fine!!
Is it possible that AD was overwhelmed with queries from our login application and just shut itself down to additional queries? We do a look-up to retrieve the user's distinguished name and then Azman has two scripts containing LDAP queries that are fired multiple times per user login. I'm wondering if it got bombarded with too many requests.
Any insight or places for us to look for answers are appreciated. The event logs on our DC and web servers haven't really yielded much.
Regards,
Ryan
ASKER
Nauman -
Thank you for your reply. However, we are using the correct domain controller name when creating our DirectoryEntry object and we are using the correct namespaces. I'm leaning more toward a non-code problem as this application was functioning without issues until yesterday. It's almost as if the domain controller stopped accepting our query requests. Then, all of a sudden it started working again.
Ryan
Thank you for your reply. However, we are using the correct domain controller name when creating our DirectoryEntry object and we are using the correct namespaces. I'm leaning more toward a non-code problem as this application was functioning without issues until yesterday. It's almost as if the domain controller stopped accepting our query requests. Then, all of a sudden it started working again.
Ryan
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Why for some many questions is the accepted sloution PAQed with points refunded? Useless!
agreed I just paid for membership for answer to question which has not been freakin answered !!
Please visit the following URL on the same discussion:
http://www.eggheadcafe.com/forums/ForumPost.asp?ID=8145&INTID=6
Best, Nauman