NT auth. VS SQL auth.

NT auth. VS SQL auth.

Post by Grzegorz Micha3e » Sat, 19 May 2001 18:57:08


    What do I have to do in case I can login to SQLserver DB with ODBC on
the client machine with "Windows NT authentication using network login ID"
and cannot login with "SQL server authentication using login ID and password
entered by user". Server returns:

"Connection failed
 SQLState: 28000
 SQLServerError: 18456   (no permission to login)
 Login failed for user ....."

All user options and permissions seem to be ok....

What and where do I have to set in SQL server to have an access in this kind
of login?




1. NT auth works, SQL Server auth doesn't

I can connect to my SQL Server if I use NT authentication, but when I switch
to SQL Server authentication in the System DSN I get an error that the user
isn't associated with a trusted connection.  When I go to the server,
though, the user ID has been added as a Login, with System Administrator
privileges and owner rights to the databases.  Is there something else that
must be done to make a user "trusted"?

2. UNIX technical support specialist *BELFAST, N.IRELAND*

3. NT authentication vs. SQL auth

4. check box

5. Windows Vs. SQL Auth

6. Courses

7. Windows Vs. SQL Auth.

8. Proliant 5000R @ $14,000 or 4500R @ $2,400

9. Connection to SQL server having NT auth

10. Citrix - SQL NT User Group Auth Problem

11. SQL Server 7.0 - Security - NT Auth.

12. Can't connect via TCP/IP + NT Auth after hotfix install

13. Using NT Auth when not connected to domain