all groups > sql server connect > december 2004 >
You're in the

sql server connect

group:

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server


Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server Bob Albert
12/21/2004 3:01:45 AM
sql server connect:
Have an APP running IIS on one box and SQL on a Win 2K3.
When running through a browser located on a completely
different box (double hop) the credentials get lost (as
designed by MS) and user is only known as Anonymous.
Everything is fine and expected so far. SQL on Win 2K
allowed such users to pass and access the db, Win 2K3
does not. I know there are alternatives ranging from
using SQL Authentication to setting Kerberos (and the
like), but these aren't options for me. I am looking for
someone who knows which W2K3 security policy, registry
setting, or, User group needs to be set/changed so that
W2K3 will give anonymous users access to SQL.

Running SQL Profiler with Security Audit Event logging
for Loggin failiures does show the failed attempt by
IIS. The following message is delivered to the browser:

Unable to open database connection. (0x80004005: Login
failed for user '(null)'. Reason: Not associated with a
trusted SQL Server connection.),
Provider=SQLOLEDB.1;Server=QMS3;Database=MessageStats;Trus
ted_Connection=Yes;Current Language=English;Locale
Identifier=1033

(0x80040114)


Any help would greatly be appreciated.

Re: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server michelle
12/23/2004 11:11:09 AM
The times that I have seen this have been caused by the local security
policy - local policies|user rights assigment|access this computer from the
network.

[quoted text, click to view]

AddThis Social Bookmark Button