Post reply

Connecting SQL server in Windows authentication mode

  • January 3, 2006 at 6:51 am

    #111279

    I am facing problem in connecting to a particular SQL server intance from my machine, using query analyzer. I have access to the databse and i'm able to connect to the server from other machines. Also i'm able to connect using sql server authentication.

    The problem is that when i am trying to connect to the server with windows authentication(i have logined to windows with my network id  eg DOMAIN\userid1) , the query analyzer is trying to connect with different user name other than mine(eg DOMAIN\userid2). Does any body know where the system is picking up the user id from, when connecting in windows authentication or how to resolve this issue.

    Suprisingly I am able to connect to other SQL server instances successfully from my machine itself.

    Please let me know in case you need any more inputs.

  • January 3, 2006 at 6:57 am

    #612380

    What happens if you try to run Query Analyzer from Start | Run by executing isqlw.exe ? How are you seeing that it's trying to connect as a different uesr?

    K. Brian Kelley
    @kbriankelley

  • January 3, 2006 at 7:03 am

    #612381

    It is successfully connecting to the server with the wrong user id(i had once mapped one network drive using this id , now i disconnected the same).

    And if i change the password of that user(or that account is locked) i'm getting an error message similar to this 'unable to make a trusted connection with user (null) (dont remember the exact error message).

     

  • January 3, 2006 at 8:21 am

    #612408

    Do you maintain any network connections to the SQL Server using that second set of credentials (mapped drives, etc.) I know you said you did once, but do you still have any other mappings? You can check by running a net use command from the command prompt.

    K. Brian Kelley
    @kbriankelley

  • January 3, 2006 at 9:07 pm

    #612508

    No there is no such connections. Also i'm able to connect to other SQL servers from my machine itself.

     

     

  • January 4, 2006 at 2:11 am

    #612532

    My guess is your client PC (your machine) is Win XP and it has used it's sometimes useful caching of credentials to hold the domain and user you mapped to tht machine with - there is probably some link somewhere through control panel to this cache but the only one I know is to use Start/Run and enter:

    rundll32.exe keymgr.dll, KRShowKeyMgr

    This brings upa list of servers/addresses it has cached credentials for and you can remove or edit them - find your errant server in the list and remove it and you will connect with the default user credentials again (i.e. who you log in as to XP)

    James Horsley
    Workflow Consulting Limited

  • January 4, 2006 at 2:36 am

    #612537

    Thanks a lot Horsley!. It is fixed!

    Thank you once again

    Regards

    Subair

  • January 4, 2006 at 10:40 am

    #612678

    Nice tip, James!

    K. Brian Kelley
    @kbriankelley

Viewing 8 posts - 1 through 7 (of 7 total)

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