Please anyone...
senario: have a windows 2000 server running SQL. This server does not hold a replica of the user database on it.
problem: client tries to make a connection via SQL's query analyzer and recieves the following message:
---------------------------
SQL Query Analyzer
---------------------------
Unable to connect to server HKSRV10:
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.
---------------------------
OK
---------------------------
What this indicates is that the client is sending its authentication details to the server HKSRV10 in this instance. At a first glance it looks like HKSRV10 does not have a user database to verify these login details. Am i correct in thinking that HKSRV10 also needs to have Active Directory installed so that this issue can be resolved or is there some type of mis configuration that is stopping the login details from being sent to the global master database server to be rubber stamped for a connection to be made.
If you have any ideas please donate.
Regards,
Nick
senario: have a windows 2000 server running SQL. This server does not hold a replica of the user database on it.
problem: client tries to make a connection via SQL's query analyzer and recieves the following message:
---------------------------
SQL Query Analyzer
---------------------------
Unable to connect to server HKSRV10:
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.
---------------------------
OK
---------------------------
What this indicates is that the client is sending its authentication details to the server HKSRV10 in this instance. At a first glance it looks like HKSRV10 does not have a user database to verify these login details. Am i correct in thinking that HKSRV10 also needs to have Active Directory installed so that this issue can be resolved or is there some type of mis configuration that is stopping the login details from being sent to the global master database server to be rubber stamped for a connection to be made.
If you have any ideas please donate.
Regards,
Nick