HELP! Cannot connect !

While I am connecting to SQL server 2000 EE from a
different client machine using Query Analyzer it gives me
the following error message .
Unable to connect to server >
Server : MSG 18452 Level 16 state 1
[Microsoft ODBC ][SQL Server Driver][SQL server] Login
failed for user '(null)' Reason , not associated with a
trusted SQL server connection.
I can connect to two other SQL servers in the same domain
just fine with QueryAnalyzer. The machine that I cannot
connect to is also my PDC. It is running Win2KSP4, the
client is WinXPSP1. I've added and removed the machine
from the domain (at my wits end) just to make sure the
accounts are not cached. This is the only computer I'm
having these client problems with, no matter who logs in.
SQL Server I cannot connect to using Windows Login is
also my PDC (Development environment)
I can connect to two other SQL servers that are member
servers on the same domain. All servers are running
SQL2000EE/SP3a MDAC 2.7SP1 on Win2K, including domain
controller.
I can log into the SQL server in question using sa
account from the client (which is running
XPSP1/SQL2000Tools/MDAC2.7FOR XP.
If I try to add databases using Enterprise Manager from
the client, I can add the other two DB servers, however I
get the same error when trying to add the SQL server in
question.
I'm stumped as the Windows Domain account has to be
working as I can authenticate to connect to the domain as
well as the other two SQL servers. (I've tried this with
a regular user account with SQL rights as well as my
domain admin account which has SQL rights.
I can connect to the server in question from any other
client in the office using the two windows domain
accounts that do not work on the client.
I'd rather not reformat te client and start over as there
are other tools (Rational) installed whose license is a
real pain to get redone. BTW, all other clients have
identical configurations (Rational, etc) which work.
I've tried uninstalling/resinstalling the SQL tools/SP3a,
reset the computer domain account (doesn't matter as I
can connect to the other two servers), something in the
registry etc must have got trashed is all I can figure.
Tried removing TCP and readding using client network
utility. Tried setting up an alias in same tool. Same
result. Can connect just fine as sa.
Thanks for any suggsetions!The login failed for user NULL indicates a problem with authenticating on
the DC when attempting the connection. It could also indicate that the user
who is attempting to logon to the SQL Server does not have permission to
access the server itself. Verify that the user can map to a share on the
SQL Server machine. If he can then check the NT Security log on the DC
where he is validated and see if there are any errors generated when he
attempts to connect to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I tried this with my domain admin account as well. Can
map shares on that server ok. Can login to server using
sa or Windows login fine over Named Pipes (server set to
both auth). When I try to login over TCP, can only login
using sa, Windows Login won't work. This server is also
the single PDC (development net).. get this, can log into
two other SQL servers (member servers only) from same
client using Named Pipes AND TCP using sa or Windows
Login.
I've un-installed TCP, removed/readded machine from
domain, it has to be something on this client...|||You get that error when the sa account hasn't been set on the server. Expand
the sql server => management folder => right click sql server agent
properties =>. last tab is connection .You would see that the sql server
connection is set to use 'windows NT authentication', you would need to
change it to SQL authentication
hope that helps
Ayo Coker
"Phil" <anonymous@.discussions.microsoft.com> wrote in message
news:fa4a01c3f1a9$47689870$a501280a@.phx.gbl...
> I tried this with my domain admin account as well. Can
> map shares on that server ok. Can login to server using
> sa or Windows login fine over Named Pipes (server set to
> both auth). When I try to login over TCP, can only login
> using sa, Windows Login won't work. This server is also
> the single PDC (development net).. get this, can log into
> two other SQL servers (member servers only) from same
> client using Named Pipes AND TCP using sa or Windows
> Login.
> I've un-installed TCP, removed/readded machine from
> domain, it has to be something on this client...
>