All of a sudden we cannot log in using sa. The "enforce expiration"
option is not set.
How could this have happened outside of a user deliberately changing
the password? Can sa get
locked out for other reasons?
Bill E.
Hollywood, FL"Bill E." <billmiami2@.netscape.netwrote in message
news:1189503759.466560.270090@.y42g2000hsy.googlegr oups.com...
Quote:
Originally Posted by
SQL Server 2005
>
All of a sudden we cannot log in using sa. The "enforce expiration"
option is not set.
How could this have happened outside of a user deliberately changing
the password? Can sa get
locked out for other reasons?
Not that I'm aware of.
Sounds like someone changed the sa password or you've got a bad case of
fat-fingering.
Worse case, I'd start looking for domain accounts and the like that didn't
exist before. (A typical 'first thing' a hacker would do.)
Quote:
Originally Posted by
>
Bill E.
Hollywood, FL
>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Thanks Greg.
This SQL Server is behind the firewall--not available outside the
corporate network. However, when I get a chance I'll follow your
suggestion.
Bill|||"Bill E." <billmiami2@.netscape.netwrote in message
news:1189514657.397892.140570@.k79g2000hse.googlegr oups.com...
Quote:
Originally Posted by
Thanks Greg.
>
This SQL Server is behind the firewall--not available outside the
corporate network. However, when I get a chance I'll follow your
suggestion.
>
It's probably an innocent screw up then.
But you never know. (Besides, not all hackers come from outside a company
unfortunately.)
Quote:
Originally Posted by
Bill
>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||If the server authentication mode was changed to Windows
Authentication only sa would no longer work.
Roy Harvey
Beacon Falls, CT
On Tue, 11 Sep 2007 02:42:39 -0700, "Bill E."
<billmiami2@.netscape.netwrote:
Quote:
Originally Posted by
>SQL Server 2005
>
>All of a sudden we cannot log in using sa. The "enforce expiration"
>option is not set.
>How could this have happened outside of a user deliberately changing
>the password? Can sa get
>locked out for other reasons?
>
>Bill E.
>Hollywood, FL
applications.
Bill
No comments:
Post a Comment