My guess is that all the domain accounts that used to work no longer due because now there's a new domain, all the accounts (and groups) have new SIDs.

Log in using the SA login and readd the domain accounts and groups to the appropriate SQL Server groups.

-Mike

>Dealing with a Windows 2000 dual-processor p4 DELL Server on which SQL2K was happily running until last Friday when a major crash occurred - both the mdf and ldf files corrupt and unrecoverable after a blue-screen-of-death server failure. No problem here: Easily recovered the database from a back-up set and all was restored to fully working operations.
>
>However, needed to also 're-address' this server: It had been installed and working under an old NT4 domain system; now have an Active Directory set-up and this server needed to be re-assigned into a domain within Active Directory. That move - using the "My PC" properties "Network Identification" tab appeared to go smoothly. However, upon bringing up Enterprise Manager once more on this server to check the status of the various SQL database components, now got the message that EM could not connect to this database any more. Meanwhile, several other W2K/SQL2Kserver databases, previously registered in this copy of EM on this server and which other serfers were already assigned to this same doamin in Active Directory as the subject server, were showing up in EM with no problem.
>
>After first deleting the subject server's node in EM and then attempting re-registering this database, first - it's name does not show up amongst the "Available Servers" listing (even though the server is clearly visible and accessible from the "Map a Network Drive" and "Network Neighborhood" functions) and second, if the server name is entered directly for registration then the result is "Cannot open user default database. Login Failed". What has been discovered is that user sa can log in but the database sysadmin login is rejected as "Error 15401: Windows NT User or group not found" but nothing has changed about this login/user who has always beeen registered in this same domain under Active Directory. The registration can be accomplished using the sa user authentication but none of the pre-existing W2K users pass the windows authentication barrier anymore even though none of these user definitions have changed in any way
>
>So the only change made has been to re-assign this server's network ID to a new domain under Active Directory from it original domain under NT4.
>
>Any ideas as to why this rejection and invisibility might be happening?
>
>Incidentally, this server is clearly visible in NetIQ's Diagnostice Manager software located on a workstation also registered in this same Active Directory domain.
>
>Thnx in aniticpation of some pearls of wisdom. /psb