We had a power outage last night and when the server came back up our domain users could not access our SQL Server 2000 instance name: MASSQL.
We can access using SQL Authentication.
- We tried making sure the user that runs the service has SSPI read and Write
- We tried creating a new user
- We tried running the service using NETWORK SERVICE account
- We tried running as Local System Account
- We tried creating a new Domain Admin account and run service as the new Domain Admin account
I also ran the following command against the problem SQL Server instance:
setspn -L xsql2
Registered ServicePrincipalNames for CN=MASSQL,CN=Computers,DC=ABC,DC=com: HOST/MASSQL HOST/MASSQL.ABC.COM
I ran the following command against a non-problem SQL instance:
setspn -L xensql1
Registered ServicePrincipalNames for CN=XENSQL1,CN=Computers,DC=ABC,DC=com: WSMAN/XENSQL1 WSMAN/XENSQL1.ABC.com RestrictedKrbHost/XENSQL1 HOST/XENSQL1 RestrictedKrbHost/XENSQL1.ABC.COM HOST/XENSQL1.ABC.COM
It seems the results for the non-problem instance have more data. I do not know if this has to do with the fact one is 2000 and the other is 2012.
What likely happened? How do I allow domain users login again?