Re: C# .NET Application looses Connection to the Active Directory Serv

You also might have a look at this post. I found this pretty useful for a similar issue I was having:

http://blogs.dirteam.com/blogs/tomek/archive/2007/08/09/system-directoryservices-and-connection-pooling.aspx



--
Darren Mar-Elia
MS-MVP-Windows Server--Group Policy

*******************************
Secure and configure your Windows desktops accurately every time without having to learn or install new technology.
Find out more about Desktop Policy Manager at http://www.sdmsoftware.com/desktop_management
*******************************




"Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:%233jBc0SlIHA.1368@xxxxxxxxxxxxxxxxxxxxxxx
It could be an issue with wildcard port exhaustion. Does NETSTAT show a large number of connections sitting in "TIME WAIT" status?

Server not operational can be a difficult error to figure out because there are a variety of different types of network problems that can cause it. Getting a network trace when the failure occurs might help as well.

Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"Constantin Wolber" <ConstantinW@xxxxxxxxxxxxxxxxx> wrote in message news:4fd8915e-d02a-4554-99b4-c691a1dd4b3c@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Ok tried it out and nothing changed. Right now the first domain
reports this error again.

greets

Constantin

On 2 Apr., 14:55, Constantin Wolber <Constant...@xxxxxxxxxxxxxxxxx>
wrote:
Hi,

thx for your answer. I checked this before the IIS is running as
Network_Service. As far as I know this should work.

So you believe I should try to run the Application Pool with my user
Account?

On 2 Apr., 14:31, Ziad K. Chafi <ZiadKCh...@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

> Hi Constantin,
> I think this might be a security issue since you recently upgraded to
> Windows Server 2003, can you check the privileges of the account that > is
> running the application, it usually runs using a local account, I_USER > I
> think, you might have to configure it to use a domain user account.

> Let me know...
> --
> Ziad K. Chafi
> MCT, MCTS, MCDBA, MCSE: S, MCDST
> CompTIA A+, CompTIA N+,

> "Constantin Wolber" wrote:
> > Hi,

> > I checked google to solve this problem but didn't really find > > anything
> > that helped.

> > We have an Intranet Web Applicatioon running for about 2 years.
> > verything worked fine. Than we needed to change onto another server.
> > While changing the servers we upgraded from .Net 1 to .net 2. The > > old
> > server was a Windows 2000 Server and now we are on a Windows Server
> > 2003 Machine.

> > Our TeamSearch is searching the AD for all Users.

> > The same code doesn't work correctly anymore.

> > When starting the IIS everything works fine. After some time > > suddenly
> > some domains don't answer to querys anymore.

> > The Exception Message is:

> > The server is not operational.

> > at System.DirectoryServices.DirectoryEntry.Bind(Boolean
> > throwIfFail)
> > at System.DirectoryServices.DirectoryEntry.Bind()
> > at System.DirectoryServices.DirectoryEntry.get_AdsObject()
> > at System.DirectoryServices.DirectorySearcher.FindAll(Boolean
> > findMoreThanOne)
> > at System.DirectoryServices.DirectorySearcher.FindOne()

> > When using netstat on the machine the output indicates that the
> > connection to the AD server is in CLOSE_WAIT status.

> > To check the connections we use a small aspx page which just does > > the
> > following for each domain:

> > DirectoryEntry eingang = new
> > DirectoryEntry(ldap, s_user, s_pass);
> > DirectorySearcher suchen = new
> > DirectorySearcher("(sAMAccountname=ad_searcher)");
> > suchen.SearchRoot = eingang;
> > suchen.FindOne();
> > the account ad_searcher exists in every single Domain.

> > Thanks

> > Constanin




.

Relevant Pages

  • Re: Please help - Cant join PC to new domain
    ... I installed a DC (Windows Server 2003 R2) and set up Active Directory ... Tried creating the computer account first and then adding it to the ... Your DNS domain name, "MYDOMAIN" is a single label name. ...
    (microsoft.public.windows.server.dns)
  • Re: Re-Post - "the trust relationship between this workstation and the
    ... "the trust relationship between this workstation and the primary domain ... only problem is adding a new user account on the station. ... Client computer must use STRICTLY the INTERNAL DNS server which can ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)
  • Re: Same question, still no answer!!!
    ... Sounds then like we are all paying for a feature set only large companies ... The "proxy server" pc is actually an older box stuffed ... Expectation #1) keep the ethernet more or less as is. ... The kids account would be ...
    (microsoft.public.windowsxp.basics)
  • Re: Re-Post - "the trust relationship between this workstation and the
    ... "the trust relationship between this workstation and the primary domain ... only problem is adding a new user account on the station. ... This would be on the DNS server 172.20.100.2 ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)
  • Sending email to mydomain.com
    ... server will appear as undeliverable. ... This happens because you are using the POP3 connector... ... an NDR when an account doesn't exist). ... >different from the user account names for the exchange ...
    (microsoft.public.windows.server.sbs)