Unable to add new user logins after Active Directory installed

  • Hi,

     

    I'm hoping someone can shed some insight into the cause and resolution of this problem. TIA! We started to experience a problem with adding userids (Windows Authentication), after we went to Active Directory. The IT Support group has finally, for the nth time, standardized all out logins to a "standard" format. This has entailed removing prior logins and reassigning the "new" login for SQL Server access. I am able to remove the old login with no issues. However, when "some" logins are attempted to be added, the logins fail with the following message dialog: "Error 15401: Windows NT user or group 'OurDomain\ausername' not found. Check the name again."  Some of the "new" logins are able ot be added correctly, no problems. It would seem that there is a problem with the Primary Domain Controller not replicating the userid so that this server can "see" them. Other SQL Servers in our domain can successfully add the ID's that failed.

    Windoows 2000 SP4, SQL2000 Standard Edition SP2.

    Ideas anyone?

    Thanks!

  • Under AD the concept of a PDC goes away, sort of... users can be added to any DC. There are only a few roles that have to run on an individual DC (PDC Emulator happens to be one). But basically, here's a few things that can be looked at that I've seen cause the issue...

    1. Check to see if the SQL Server's computer account is generating failures. A sysadmin would likely see this on a DC under its System Event Log. The Source would be NETLOGON. See if there are a lot of failures.
    2. Verify the SQL Server is time synchronizing correctly with the DCs.
    3. Verify the usernames are getting replicated to each DC. A sysadmin can connect to each particular DC to check out the user accounts. Is this SQL Server using a DC others wouldn't be using?

     

    K. Brian Kelley
    @kbriankelley

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply