Login failed for user '(null)'


I have a SQL 2000 Server running on Windows 2003. The server is a secure internal build, and I must confess I don't have full visibility of all the security elements that have been performed at the OS level, but for the SQL server, I do have.

I have added my account as a Sysadmin login to the server (e.g. DOMAIN1\USER1).

Now when I run Query Analyser from a client logged on as DOMAIN1\USER1, I receive the error:

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.

It's as if my domain credentials are not being passed across to the server.

Thanks in advance.
LVL 7
lozzamooreAsked:
Who is Participating?
 
PAQ_ManConnect With a Mentor Commented:
PAQed with points refunded (500)

PAQ_Man
Community Support Moderator
0
 
jackiechen858Commented:
Check the SQL Server enterprise manager->your database server-> Security->logins,
Add Domain1\User1
0
 
Ramesh SrinivasTechnical ConsultantCommented:
More than likely that your user does not have access to the sql server. You should test that this is the case by creating a connection to your sql server from another server. E.,g., use webpage, vb.net app or file dsn etc.
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
jackiechen858Commented:
oh, You already did it.
0
 
lozzamooreAuthor Commented:
Saleek,

I'm testing access from another workstation using SQL Query Analyser.

The login has been added in SQL Server. Does the user need additional access?

Thanks,
0
 
Ramesh SrinivasTechnical ConsultantCommented:
Can you gain access by logging in (at the client end) using the built-in sql server admin account?
0
 
lozzamooreAuthor Commented:

I can log into the client using the SQL Server Service account no problem.

However-I just tried logging into the Win2003 Server using the Service account, and I get the following:

The system cannot log you on due to the following error:
The RPC server is unavailable.

Please try again or.....

Does this mean anything to you?
Could a service that is required not be running?

Thanks,
0
 
Ramesh SrinivasTechnical ConsultantCommented:
Hmmm. Did you recently create the service account? I'm just wondering if you did, then whether the change has been propogated over the network.  
0
 
Ramesh SrinivasTechnical ConsultantCommented:
Some possible cause I found on the internet:

1. The RPC service may not be started.
2. You are unable to resolve a DNS or NetBIOS name.
3. An RPC channel cannot be established.

0
 
lozzamooreAuthor Commented:

1. I've checked the RPC Service on the server, and it is started ok.

2. As the environment is AD, Win2003 Server, and XP Client, I'm assuming NetBIOS use should be minimal.

So-I have checked:
resolving client DNS name from server. OK
resolving DC name from server. OK

3. Not sure how I would go about checking this?

Thanks,


0
 
lozzamooreAuthor Commented:

UPDATE:

We got our OS guys here to remove the win2003 "security template" that they had applied.

This has removed the issue.

I don't know much about the security template features, but from what I have heard, these are largely an automated way of applying Local Policies and Registry Settings.

Anyone have any experience of which setting could have caused this issue?

BTW: The RPC error message when I try and logon to the server still persists (?)
0
 
lozzamooreAuthor Commented:
OK,

Please post if you wish me to arrange to have the question deleted.

Incidentally-for all subscribed: I recently found out, we did get a resolution for this issue, and were able to get connections working with the security template applied also.

The account running SQL services must have the "Impersonate a client after authentication" right.  This doesn't seem to be necessary if LOCAL SYSTEM is running them, but is for a domain account.

Thanks,
0
All Courses

From novice to tech pro — start learning today.