November 17, 2011 at 1:25 am
anthony.green (11/17/2011)
this is a good reason why service accounts should be used with none expiring passwords to run SQL server services
Agree for SQL Server Service Accounts. But the issue was related to regular logins.
November 17, 2011 at 1:27 am
In this instance this wouldn't of helped as they detail there are multiple SQL servers at play here, not just the one having the issue with the login. It seems that there where a number of SQL servers running under the users account, as this was locking the account out at AD level when the account tried to authenticate with SQL, AD said no as the account is locked.
We can guess few things based on Experience... 🙂
November 17, 2011 at 1:31 am
Dev (11/17/2011)
anthony.green (11/17/2011)
this is a good reason why service accounts should be used with none expiring passwords to run SQL server servicesAgree for SQL Server Service Accounts. But the issue was related to regular logins.
bpportman 52825 (11/16/2011)
there were a couple of SQL servers where using his ID...SQL reporting and DBs running scripts with his ID...changed his password over vpn on the weekend, something happened where it broke and it didn’t propagate everywhere and it didn’t update everywhere
As the users account was logging in with the old password to other resources and failing AD was locking the account. When the authentication was happening the users account was locked so the authentication couldnt happen
bpportman 52825 (11/16/2011)
So I went in and removed his credentials from those SQL boxes and problem was solved
The account no longer being locked out at AD level, account can now authenticate
December 3, 2015 at 3:29 am
We had same issue with few users, where their network DNS entries were obsolete due to which those clients were unable to connect via SQL Server via windows authentication. After fixing local users DNS IP it started connecting SQL with windows authentication...
May be this will help someone ....
Shamshad Ali
December 3, 2015 at 3:31 am
We had same issue with few users, where their network DNS entries were obsolete due to which those clients were unable to connect via SQL Server via windows authentication. After fixing local users DNS IP it started connecting SQL with windows authentication...
May be this will help someone ....
Shamshad Ali
December 3, 2015 at 3:31 am
We had same issue with few users, where their network DNS entries were obsolete due to which those clients were unable to connect via SQL Server via windows authentication. After fixing local users DNS IP it started connecting SQL with windows authentication...
May be this will help someone ....
Shamshad Ali
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply