Post reply

Weird user authentication problem

  • January 4, 2007 at 2:13 pm

    #368705

    Only one user is getting the following error (from eventlog):

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

    I verified that the user in the active directory (We are using Windows authentication) and this user has been given rights to access SQL Server. But when the user tries to launch QA, the above error is being thrown.

    The same user is able to access other database servers using windows authentication.

    Please help.

  • January 4, 2007 at 11:22 pm

    #681389

    Make sure use login configure for window authentication....

    Can the user connect using osql utiltiy??

    Try explicitly using TCP/IP protocol for while connecting..

    http://support.microsoft.com/default.aspx?scid=kb;en-us;827422&Product=sql2k

    http://support.microsoft.com/kb/840219

     

    MohammedU
    Microsoft SQL Server MVP

  • January 4, 2007 at 11:25 pm

    #681392

    The key is that it thinks the user account is Null. Tell the user to reboot their machine. In most cases I have encountered this resolves the issue. If not, reboot the SQL Server.

    My blog: SQL Soldier[/url]
    SQL Server Best Practices:     SQL Server Best Practices
    Twitter: @SQLSoldier
    My book: Pro SQL Server 2008 Mirroring[/url]
    Microsoft Certified Master: SQL Server, Data Platform MVP
    Database Engineer at BlueMountain Capital Management[/url]

  • January 5, 2007 at 6:27 am

    #681447

    Whenever I've seen this in the past, the user's account was locked out. (Ie. Too many pw retries, forgot their pw, etc.)

    Chris.

    Chris.

  • January 5, 2007 at 6:40 am

    #681450

    ask the user to logoff and then login and access the sql server.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

  • January 5, 2007 at 7:16 am

    #681465

    are you doing this through .net or something like that where you have a connection string?  If you are, and the database and the files are on different servers, and there's not an explicit trust between them, then it doesn't seem to pass that information even if they are on the same domain.  What I've done is simply make a database user to the tables that you need the web interface to access, and put that info in the connection string.  Use the .net authentication to filter the users who are allowed to do certain features of the site, and access certain things in the database, and simply make the pages that do the features restricted to folders with the appropiate permissions for that role.
     
    If you aren't doing some type of cross computer authentication then I'm not sure, but maybe more informatin would help.  I can't see a restart doing anything, although that does tend to fix a lot of problems that make no sense in Windows.
     
     
    Kindest Regards,

    Jon Kress
    Site I maintain at work. (Password protected)

  • January 5, 2007 at 9:33 am

    #681507

    We've tried

    1. Logoff and log back in to workstation.

    2. Restarted the machine (this worked before, but not working anymore).

    This is not through any application (.NET or VBA), he was trying to launch QA. The database and the files are on the same server.

    Here is another twist, he was able to login (windows) on from my workstation and was able to launch QA without any problem.

    Please help !!!

  • January 5, 2007 at 9:39 am

    #681509

    XP? Home Pro?

    Kindest Regards,

    Jon Kress
    Site I maintain at work. (Password protected)

  • January 5, 2007 at 9:49 am

    #681512

    XP Pro SP 2

  • January 5, 2007 at 9:56 am

    #681514

    I've seen something similar when the secure channel between teh SQL server and the domain controller is broken. Can't authenticate. Is this a new user? Or someone that hasn't logged in for awhile?

    anyone else having issues?

    I know there are some utilties to check the channel. Be sure the user is actually connecting to the DC as well. Workstations cache junk and sometimes you don't really auth to the controller. Try changin a pwd.

  • January 5, 2007 at 10:01 am

    #681516

    hmmm, well if all updates are installed, I'm temporarily stumped

    Kindest Regards,

    Jon Kress
    Site I maintain at work. (Password protected)

  • January 5, 2007 at 10:05 am

    #681518

    At our organization we have two different domains that the SQL Servers reside in and some of the clients are not in a domain at all.  You may want to check that the problem PC is in the same domain as the server.

  • January 5, 2007 at 10:11 am

    #681521

    Steve, how do I clean the cache on the workstation.

    1. Can you name some of those utilties to check the channel.

    2. How do I check the user is actually able to connect to the DC.

    3. The user changed the password and tried to launch QA, but failed again.

    Do you think if we reinstall SQL Server on the workstation will take care of the problem.

    Thank you Jon.

  • January 5, 2007 at 1:31 pm

    #681571

    Have you checked that the machine time on both server and client are the same?  I had a similar issue at one client site (not SQL Server, but using Windows Authentication) where the kerberos ticket was rejected because the clock time on the client was off by several hours.  (I guess this ticket encryption is time sensitive?  I don't know, perhaps someone else more versed in network protocols might explain).



    Mark

  • January 5, 2007 at 2:01 pm

    #681579

    does the error message come from an attempt to connect via a linked server?  the server principal name (SPN) may not be correctly identified. 

    Cheers,

    Todd

Viewing 15 posts - 1 through 15 (of 22 total)

You must be logged in to reply to this topic. Login to reply