RE: Active Directory Upgrade and SQL

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Cindy Gross (cgross_at_online.microsoft.com)
Date: 03/04/04


Date: Thu, 04 Mar 2004 20:08:07 GMT

Assuming these are connection timeouts (as opposed to query timeouts), I
would guess that your domain controller is slow to authenticate your
logins. I would suggest checking other connectivity and see if there are
delays in authenticating when you create/access shares and other such
activity.

Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.



Relevant Pages

  • Re: AD 2003 Replication Failure/Authentication Failure
    ... >Verify time is synchronized on all DCs. ... users can authenticate to the Seidler-root domain controller, ... users can authenticate to the enterprise domain controller. ...
    (microsoft.public.windows.server.active_directory)
  • Forcing authentication with a specific DC
    ... I take it your PDC ... specific domain controller, that domain controller ... controller that holds the PDC emulator role. ... I want them to authenticate at the main ...
    (microsoft.public.win2000.security)
  • Re: User authenication from remote site ?
    ... There is a domain controller at the Head Quarter ... Users at remote site finds that the response time for accessing data ... Replication of data of AD between HQ and RS ... Users at RS has to authenticate via HQ ...
    (microsoft.public.windows.server.active_directory)
  • Re: Native Mode possible problems...help!
    ... >> Todd J Heron, MCSE ... >>> know which domain controller authenticates them if they are tech ... How can I verify which domain controller they authenticate ...
    (microsoft.public.windows.server.general)
  • Re: Flat domain to start off?
    ... I was told I need to assign each domain controller as a GC server. ... I do need to move computers/users to a sub-domain, ... control the DCs that your client computers authenticate against to prevent ... But I suspect since you are using a single NT4 domain ...
    (microsoft.public.windows.server.active_directory)