Login failed for user '(null)'.

I'm running SQL 2000, SP3 on a W2K server and am having an issue where
users who are trying to connect to SQL Server via Windows Authenication
are getting a 'Login failed for user '(null)'. error. They have plenty
of permissions on SQL Server so that's not the issue. I've done some
testing and the only way I can get them to connect to SQL Server is if I
add them to the local admin group on the server. Has anyone else ever
seen this?
*** Sent via Developersdex http://www.codecomments.com ***
Hi
Give the domain user permission to log into SQL Server.
Look at "user accounts, described" in BOL Index.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rachael Faber" <rfaber@.alldata.net> wrote in message
news:OZczaqUOFHA.2704@.TK2MSFTNGP15.phx.gbl...
> I'm running SQL 2000, SP3 on a W2K server and am having an issue where
> users who are trying to connect to SQL Server via Windows Authenication
> are getting a 'Login failed for user '(null)'. error. They have plenty
> of permissions on SQL Server so that's not the issue. I've done some
> testing and the only way I can get them to connect to SQL Server is if I
> add them to the local admin group on the server. Has anyone else ever
> seen this?
>
> *** Sent via Developersdex http://www.codecomments.com ***
|||They do have permissions through SQL Server. The problem is that their
domain logins still fail unless I add their login to the local admin
group on the server.
*** Sent via Developersdex http://www.codecomments.com ***
|||No problems with these users logging into the Domain and accessing Domain
resources? Make sure they're not logging into their local machines as
opposed to the Domain (sometimes users forget to change the little drop-down
box on the login screen). Are you using an app that you created or is it an
off-the-shelf prog? If it is a custom app, what's the connection string
look like?
"Rachael Faber" <rfaber@.alldata.net> wrote in message
news:eNXw5jVOFHA.3704@.TK2MSFTNGP12.phx.gbl...
> They do have permissions through SQL Server. The problem is that their
> domain logins still fail unless I add their login to the local admin
> group on the server.
>
> *** Sent via Developersdex http://www.codecomments.com ***
|||They're definitely logged into the domain - and just to be sure it
wasn't just an end-user error I had 2 other DBAs on my team try to
connect to the database through query analyzer and they got the same
error message.
The application team has tried connecting through their application and
through query analyzer but cannot connect unless I add them to the local
admin group. We can use that as a temporary work around but I'd like to
figure out what's going on.
Any suggestions?
*** Sent via Developersdex http://www.codecomments.com ***
|||Hi,
What account is SQL Server running under?
I've had issues with authentication if it's running under the local system account.
I don't know how you've set things up, but here is what worked for me.
I create a local group and add the domain users to this group.
I create a logon for the local group and give it the appropriate permissions.
HTH
Dan Artuso, MVP
"Rachael Faber" <rfaber@.alldata.net> wrote in message news:uV%23r8ieOFHA.2356@.TK2MSFTNGP14.phx.gbl...
> They're definitely logged into the domain - and just to be sure it
> wasn't just an end-user error I had 2 other DBAs on my team try to
> connect to the database through query analyzer and they got the same
> error message.
> The application team has tried connecting through their application and
> through query analyzer but cannot connect unless I add them to the local
> admin group. We can use that as a temporary work around but I'd like to
> figure out what's going on.
> Any suggestions?
>
> *** Sent via Developersdex http://www.codecomments.com ***
|||It's running under a domain account.
*** Sent via Developersdex http://www.codecomments.com ***
|||Hi Rachael,
Try to rejoin to domain some of the clients.
Regards,
Daniel
"Rachael Faber" <rfaber@.alldata.net> wrote in message
news:OZczaqUOFHA.2704@.TK2MSFTNGP15.phx.gbl...
> I'm running SQL 2000, SP3 on a W2K server and am having an issue where
> users who are trying to connect to SQL Server via Windows Authenication
> are getting a 'Login failed for user '(null)'. error. They have plenty
> of permissions on SQL Server so that's not the issue. I've done some
> testing and the only way I can get them to connect to SQL Server is if I
> add them to the local admin group on the server. Has anyone else ever
> seen this?
>
> *** Sent via Developersdex http://www.codecomments.com ***
|||Hi,
Okay, the only other thing I've seen is I've had to grant access explicitly to the domain group
in the Local Security Policy
In User Rights Assignment:
Allow access to this computer from the network
add the domain group that your users area member of. By default the local Admins group
is a part of this so perhaps that is why it works when you make your users part of that group.
HTH
Dan Artuso, MVP
"Rachael Faber" <rfaber@.alldata.net> wrote in message news:%23ZoVHurOFHA.1732@.TK2MSFTNGP14.phx.gbl...
> It's running under a domain account.
>
> *** Sent via Developersdex http://www.codecomments.com ***
|||That's exactly what the problem was - thank you!!
*** Sent via Developersdex http://www.codecomments.com ***