I am getting that annoying error "Login failed for user
'(null)'. Reason: Not associated with a trusted SQL", but
this appears to be different from the posts I have seen so
far.
Everything was OK until yesterday morning. We have Novell
and Active Directory. The login box is Novell on my desktop
system, but I login with an Active Directory userid.
When trying to connect using Enterprise Manager or Query
Analyzer, I get the message above - if I am on my desktop
system. If I login directly on the system running SQL Server
2000 using the AD account, then I can connect in Enterprise
Manager or Query Analyzer without any problems.
This is occurring on 2 different SQL Server systems. I can
connect remotely using 'sa'. Also, the servers are set to use
both Windows and SQL logins.
I would really like to hear any suggestions on how to resolve
this.
tia,
Bill
For Enterprise manager,
Ensure you have the server registration set up to use a trusted connection,
(instead of the registration using standard).
Also make sure the client you are having a problem with, has the same
network protocols that the server is listening on..
Hope this helps.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<bill_sheets@.hotmail.com> wrote in message
news:1112106862.273066.309790@.z14g2000cwz.googlegr oups.com...
>I am getting that annoying error "Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL", but
> this appears to be different from the posts I have seen so
> far.
> Everything was OK until yesterday morning. We have Novell
> and Active Directory. The login box is Novell on my desktop
> system, but I login with an Active Directory userid.
> When trying to connect using Enterprise Manager or Query
> Analyzer, I get the message above - if I am on my desktop
> system. If I login directly on the system running SQL Server
> 2000 using the AD account, then I can connect in Enterprise
> Manager or Query Analyzer without any problems.
> This is occurring on 2 different SQL Server systems. I can
> connect remotely using 'sa'. Also, the servers are set to use
> both Windows and SQL logins.
> I would really like to hear any suggestions on how to resolve
> this.
> tia,
> Bill
>
No comments:
Post a Comment