C# .NET Application looses Connection to the Active Directory Server

[BuvDeep]

He guys I need some urgent help from you all. We are running a Intranet Web Application at our office since past 2 years. It was working fine without any problem until last week when we required to move onto another server. While doing the change in server we needed to upgrade from Net 1 to Dot Net 2. We moved the server successfully but now our teamsearch is busy searching AD for or all users. Also the code is not working anymore.

When we start IIS, it works good for some time but suddenly after an hour it starts giving problems and domains wont answer the queries anymore. This is the message we received:

at System.DirectoryServices.DirectoryEntry.Bind(BooleanthrowIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_AdsObject()
at System.DirectoryServices.DirectorySearcher.FindAll(BooleanfindMoreThanOne)
at System.DirectoryServices.DirectorySearcher.FindOne()

[Bauer's]

To me it sounds like a security problem. As you upgraded your Windows Server recently. Anyway can you just verify the privileges of the account that is running the application? Most probably it runs on a local account. You may also need to configure it to use a domain user account.

Just check and let me know the results.

[BuvDeep]

Thank you very much for the help friend. As you suggested i checked the same and found that the IIS is running as Network_Service. So do i still need to run the Application Pool with my user Account?

Please help.

[JareD]

Well then most probably the issue is with wildcard port exhaustion. Did you checked NETSTAT ? Is it showing up a large number of connections sitting in "TIME WAIT" status? Apart from this, if you are getting Server not operational error than it is going to be difficult to figure out as there use to be different types of network problems that can cause it. So I think getting a network trace when the failure occurs might help as well.

[1kshana]

Hello BuvDeep. You might need to check the followinh article describing:

System.DirectoryServices and connection pooling

When i was struggling with very similar problem like yours, it really helped me.