Results 1 to 3 of 3
  1. #1
    Join Date
    Oct 2003
    Posts
    37

    Unanswered: Can't get windows authentication in Mixed Mode to work .... any ideas?

    Hey all,
    I've got SQL 2K running in mixed mode. I created a windows acct (mytest) in the administrator group, and then created a corresponding SQL account (mytest) using the windows authentication. In the EM it comes up as a "Windows User" type of acct. (The account is not a domain account but a workstation one).

    I've configured my app to use that account for access to the database but I get the following error message when I send the connection request to the datasource:

    Connection Failed:
    SQL State:28000
    SQL Server Error: 18456
    Login failed for user myworkstation\mytest

    I can connect just fine using the sql accounts, but it doesn't want to play nice when I need the windows authentication portion to work.
    What exactly am I doing wrong?
    Any input is greatly appreciated !
    Regards,
    Tammy

  2. #2
    Join Date
    Dec 2002
    Posts
    1,245

    Re: Can't get windows authentication in Mixed Mode to work .... any ideas?

    A couple of things come to mind...

    1. If mytest is a member of the workstation Administrators group, then you do not (necessarily) need a separate SQL account for it. The BUILTIN\Administrators account permits all members of the local Administrators group to have access (in the default config anyway).

    2. If you have denied access to the BUILTIN\Administrators group, then myWorkstation\mytest will not have access (Deny trumps permit).

    3. Just a head check: you said that myworkstation\mytest was NOT a domain account (when you set it up). You didn't by chance login under the domain?

    Just my $ .02. It's not much, I'll grant you, but it was what I could come up with.

    hmscott

  3. #3
    Join Date
    Oct 2003
    Posts
    37

    Talking Re: Can't get windows authentication in Mixed Mode to work .... any ideas?

    Mr. Scott !
    I'm such an idiot .....
    I had forgotten that I denied access to the builtin Administrator account. I turned it back on and VOILA !
    Mr. Scott - 1
    Tammy - 0
    Gracias !

    Originally posted by hmscott
    A couple of things come to mind...

    1. If mytest is a member of the workstation Administrators group, then you do not (necessarily) need a separate SQL account for it. The BUILTIN\Administrators account permits all members of the local Administrators group to have access (in the default config anyway).

    2. If you have denied access to the BUILTIN\Administrators group, then myWorkstation\mytest will not have access (Deny trumps permit).

    3. Just a head check: you said that myworkstation\mytest was NOT a domain account (when you set it up). You didn't by chance login under the domain?

    Just my $ .02. It's not much, I'll grant you, but it was what I could come up with.

    hmscott

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •