Login failed for user '(null)'

Hello world,
I'm getting the following error when trying to register an instance of SQL
in Enterprise Manager (connecting using Windows authentication):
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
EM sits on a developer's PC running XP Professional SP2, and SQL Server 2000
Standard Ed. SP4 resides on a Windows 2000 Server (SP4)
This particular PC was previously able to connecte to this manner prior to
migrating the SQL server from being a member server within an NT4 domain to
being a member server within a Windows 2003 Active Directory Domain.
Any thought's as to why Windows authentication has stopped working would be
most appreciated.Chris
Do you grant access to SQL Server,for login? What is a default database
did you assign to him?
"Chris Ford" <ChrisFord@.discussions.microsoft.com> wrote in message
news:0189E38E-31FC-4E43-A79E-FCABE2726A9A@.microsoft.com...
> Hello world,
> I'm getting the following error when trying to register an instance of SQL
> in Enterprise Manager (connecting using Windows authentication):
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> EM sits on a developer's PC running XP Professional SP2, and SQL Server
> 2000
> Standard Ed. SP4 resides on a Windows 2000 Server (SP4)
> This particular PC was previously able to connecte to this manner prior to
> migrating the SQL server from being a member server within an NT4 domain
> to
> being a member server within a Windows 2003 Active Directory Domain.
> Any thought's as to why Windows authentication has stopped working would
> be
> most appreciated.|||Uri
Thanks for replying so quickly.
Yes for the purposes of testing the connection, I've assigned the developer
(an ordinary domain user) public access to Northwind.
I've also tried making them a member of the Sysadmin Server role to no effec
t.
The same user can connect to another SQL server using Windows Authentication
(SQL 2000 Workgroup Ed SP4 running on Windows 2003 SP1).
I've just tried the same user from a different PC and he can log in from
there too (that one runs Windows 2000 Professional SP4).
"Uri Dimant" wrote:

> Chris
> Do you grant access to SQL Server,for login? What is a default database
> did you assign to him?
>|||Chris
Any errors in event viewer, sql server log file?
"Chris Ford" <ChrisFord@.discussions.microsoft.com> wrote in message
news:5DD31C06-D0ED-4DC1-9768-A072FBBBBA1B@.microsoft.com...
> Uri
> Thanks for replying so quickly.
> Yes for the purposes of testing the connection, I've assigned the
> developer
> (an ordinary domain user) public access to Northwind.
> I've also tried making them a member of the Sysadmin Server role to no
> effect.
> The same user can connect to another SQL server using Windows
> Authentication
> (SQL 2000 Workgroup Ed SP4 running on Windows 2003 SP1).
> I've just tried the same user from a different PC and he can log in from
> there too (that one runs Windows 2000 Professional SP4).
> "Uri Dimant" wrote:
>
>|||Uri
Nothing that appears to by related to the problem on either the Server SQL
and Event logs or the client event logs.
Most of the events in the security logs appear to be Privilege Use types
related to other processes.
"Uri Dimant" wrote:

> Chris
> Any errors in event viewer, sql server log file?
>|||Can anyone offer any other suggestions?|||Further tests have revealed that only clients with Windows XP Professional
are affected. Prior OS versions seem to work fine.|||Several things...
1) Depending on how your active directory is setup, you may need to be in
the domain to authenticate to it if it's only supporting kerberos rather
than just ntlm
2) Domain policies can restrict stuff. If both computers aren't in the
domain than perhaps one is more restrictive than the other.
3) If using kerberos to authenticate, you may need to enable kerberos
delegation on the sql server.
"Chris Ford" <ChrisFord@.discussions.microsoft.com> wrote in message
news:0189E38E-31FC-4E43-A79E-FCABE2726A9A@.microsoft.com...
> Hello world,
> I'm getting the following error when trying to register an instance of SQL
> in Enterprise Manager (connecting using Windows authentication):
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> EM sits on a developer's PC running XP Professional SP2, and SQL Server
> 2000
> Standard Ed. SP4 resides on a Windows 2000 Server (SP4)
> This particular PC was previously able to connecte to this manner prior to
> migrating the SQL server from being a member server within an NT4 domain
> to
> being a member server within a Windows 2003 Active Directory Domain.
> Any thought's as to why Windows authentication has stopped working would
> be
> most appreciated.