Login failed after reseting password

I was away from the office and there was a need to check in a few
sourcesafed documents. My domain user account had its password changed.
When I got back, I changed it back to the same password I have always
used. However, I now am experienced login issues with every server on
the domain using windows auth. Does setting the password create a new
profile? Can I not login to SQL Server becuase the SID has changed? Is
there anyway to restore my domain account so it has access to the SQL
Servers using windows auth. We are running Windows XP Pro and SQL
Server 2000 sp4. This error is essentially putting me out of
commission. Any suggestions?Hi
The SID remains the same.
If the domain is working correctly, the updated password should propagate
within a few minutes. Try logging off, rebooting and then see if you can
authenticate. You may want to try logging if from a different machine to
verify it is not machine specific.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<chase.colburn@.gmail.com> wrote in message
news:1133971287.204872.168840@.g49g2000cwa.googlegroups.com...
>I was away from the office and there was a need to check in a few
> sourcesafed documents. My domain user account had its password changed.
> When I got back, I changed it back to the same password I have always
> used. However, I now am experienced login issues with every server on
> the domain using windows auth. Does setting the password create a new
> profile? Can I not login to SQL Server becuase the SID has changed? Is
> there anyway to restore my domain account so it has access to the SQL
> Servers using windows auth. We are running Windows XP Pro and SQL
> Server 2000 sp4. This error is essentially putting me out of
> commission. Any suggestions?
>|||Thank you for the suggestion. This error persisted after about a day
and a half of troubleshooting, logging in as different users,
rebooting, ect. I just finally went ahead and bite the bullet and
reinstalled SQL Server. It was a little messy getting everything back
to normal but I seem to be authenticating fine now. I am still curious
as to why I had this problem and whether or not a reinstall could have
been prevented. If anyone has any insight, please feel to post.