Re: Login failed for user '(null)'
- From: "news.microsoft.com" <beh@xxxxxxxx>
- Date: Fri, 1 Dec 2006 10:56:40 -0500
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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0189E38E-31FC-4E43-A79E-FCABE2726A9A@xxxxxxxxxxxxxxxx
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.
.
- Prev by Date: Re: Recover delete the row from a table?
- Next by Date: Re: "Drop User" statement does not seem to work
- Previous by thread: Re: Changing the "dbo" schema owner...breakage?
- Next by thread: Re: "Drop User" statement does not seem to work
- Index(es):
Relevant Pages
|
