Post reply

Weird user authentication problem

  • January 7, 2007 at 6:14 am

    #681672

    Please check for the registry privileges in that particular machine for that particular user i hope so the windows account does not have registry access that's why you get a "login failed for user(null)". Please check and let me know i have faced this while changing the connection properties of sql server agent and then after giving the necessary privileges it worked. Please do check and reply me back. Thanks in advance.

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

  • January 7, 2007 at 10:01 am

    #681677

    I have seen this only once on a network with static IPs. After all admins kai programmers gave up trying the network administrator rebuild (??? not sure of the terminology) something called an IP routing table or something like that and then the logon worked perfect.

    The client PC could not connect to the server machine for SQL server but it mapped network drives on the same server and they worked. It was really strange.

    Rebooting the server, client PC or SQLSERVER or DNS service did not work.

    If you don't get it fixed, drop a line so that I can call our administator and ask for details (on Monady that is!)

  • January 8, 2007 at 10:17 am

    #681833

    Viz, can you let me know how or what your network admin did to fix this problem.

    Thank you.

  • January 14, 2007 at 8:31 am

    #683123

    whats the type of windows authentication mechanism being used. is it kerebros or NTLM if kerberos it mite be a hop problem. a good article for the same is available in msdn blogs.

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

  • January 14, 2007 at 9:13 am

    #683126

    How do I find if it's kerbros or NTLM. Isn't kerbros related to analysis services?

  • January 14, 2007 at 11:07 am

    #683137

    http://www.google.com/search?hl=en&q=kerberos+NTLM

    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 19, 2007 at 10:20 am

    #684387

    The problem was the user's profile got corrupted.

    1. Ask the user to login on a different workstation (that has SQL QA & never logged in on that machine)

    2. Connect to the same SQL Server using NT authentication.

    If (s)he is able to, then it's a profile issue.

    After recreating the user profile, he was able to login to SQL server using NT authentication.

    Thank you all folks.

  • January 19, 2007 at 12:24 pm

    #684415

    Wow, we were soo making it more complicated than it should have been.
     
    KISS as they say *smacks forehead*
     
    Glad it's taken care of for you!
    Kindest Regards,

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

Viewing 8 posts - 16 through 22 (of 22 total)

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