2nd Login failed for user '(null)' ...

This is driving me NUTS!
Sometime on Modday, or the first part of the day Tuesday, I lost my ability
to connect to the servers from my workstation and have been getting the
message: "Login failed for user '(null)' ...".
I think (but am not sure) that this started with my changing the login
account in Windows Services for all the SQL Server entries from my domain
account to the Local account.
I have since completly uninstalled all SQL Servers and tools and then
reinstalled just the SQL Server 2000 client tools. Also, my local profile
was completly removed and I started with a fresh local account.
Now the really bizzare stuff. I (of course) get the error when logged into
my machine and I also get the error when logged into another machine.
However, when our Windows sysadmin logs into my machine, he can connect just
fine.
I am so totally lost, it isn't funny.OK, my version of the problem has been figured out.
The remote servers I'm dealing with are not part of the domain and we had a
new password policy (on the new QA cluster) that required two additional
characters be added. The Windows sysadmin had me change my domain password
to match - hence a password mismatch and the error.
Once I changed my password back to the old one, I was able to connect again.
Sigh ...
"Jay" <nospam@.nospam.org> wrote in message
news:unwuEGYIIHA.5360@.TK2MSFTNGP03.phx.gbl...
> This is driving me NUTS!
> Sometime on Modday, or the first part of the day Tuesday, I lost my
> ability to connect to the servers from my workstation and have been
> getting the message: "Login failed for user '(null)' ...".
> I think (but am not sure) that this started with my changing the login
> account in Windows Services for all the SQL Server entries from my domain
> account to the Local account.
> I have since completly uninstalled all SQL Servers and tools and then
> reinstalled just the SQL Server 2000 client tools. Also, my local profile
> was completly removed and I started with a fresh local account.
> Now the really bizzare stuff. I (of course) get the error when logged into
> my machine and I also get the error when logged into another machine.
> However, when our Windows sysadmin logs into my machine, he can connect
> just fine.
> I am so totally lost, it isn't funny.
>