RE: How to create a trusted connection
From: Bill Cheng [MSFT] (billchng_at_online.microsoft.com)
Date: 07/15/03
- Next message: Usman: "user's rights"
- Previous message: ABG: "New Sysadmin cannot stop SQL instance..."
- In reply to: Bill Cheng [MSFT]: "RE: How to create a trusted connection"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 15 Jul 2003 03:32:30 GMT
Hi Jim,
You need to grant access for the Windows login by referring to the books
online topic that I had previously posted and also ensure that SQL Server
is set to use Windows authentication to be able to do trusted connection.
There are two modes of authentication in SQL Server:
Windows only mode and Mixed - in either case Windows authentication must
have been enabled on the Server.
It is possible that the authentication mode is set to Windows only in your
case and you are trying to a login using a SQL login that you have created
and that is failing for obvious reasons as the authentication mode needs to
set to MIXED - both Windows and SQL Server authentication.
You may also want to refer to the following articles to see if they apply
to you scenario:
INF: Windows Authentication is the Default Security Mode After a SQL Server
2000 Typical Installation
http://support.microsoft.com/?id=269587
FIX: Connection Failure Errors Occur After Upgrade to MSDE 2.0
http://support.microsoft.com/?id=308212
~~~~~~~~~~~~~~~~~~~~
You may refer to the following BOL topic (books online) for more
information on Authentication Mode:
Authentication Mode
Authentication Modes
Logins
How to set up Mixed Mode security (Enterprise Manager)
SQL Server Books Online from MSDN
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/startsql/ge
tstart_4fht.asp
SQL Server 2000 Books Online (Updated - Service Pack 3)- Download
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Bill Cheng
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
--------------------
| X-Tomcat-ID: 572429130
| References: <000e01c346f5$44abafa0$a301280a@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: billchng@online.microsoft.com ("Bill Cheng [MSFT]")
| Organization: Microsoft
| Date: Thu, 10 Jul 2003 16:30:25 GMT
| Subject: RE: How to create a trusted connection
| X-Tomcat-NG: microsoft.public.sqlserver.security
| Message-ID: <rQyLXCwRDHA.1636@cpmsftngxa06.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.security
| Lines: 64
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.security:14432
| NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
|
| Hi Jim,
|
| How do you login? What do you mean by "creating a Windows login"? Is your
| SQL Server 2000 MSDE 2000, or Standard Edition? Do you have Query
Analyzer?
|
| To login SQL Server 2000 using trusted connection, grant the Windows
| account access to the SQL Server, login in Windows 2000 as the Windows
| account, open Query Analyzer, and use "Connect using Windows
| authentication".
|
| Since authentication is a large topic, SQL Server Books Online has some
| documentation for it. I suggest that you check "Adding a Windows User or
| Group" in SQL Server Books Online to get the concept, as understanding it
| is quite important for troubleshooting the problem.
|
|
| This posting is provided "AS IS" with no warranties, and confers no
rights.
|
| Regards,
|
| Bill Cheng
| Microsoft Support Engineer
| --------------------
| | Content-Class: urn:content-classes:message
| | From: "JimT" <Jim_Taylor@ieee.org>
| | Sender: "JimT" <Jim_Taylor@ieee.org>
| | Subject: How to create a trusted connection
| | Date: Thu, 10 Jul 2003 08:09:32 -0700
| | Lines: 24
| | Message-ID: <000e01c346f5$44abafa0$a301280a@phx.gbl>
| | MIME-Version: 1.0
| | Content-Type: text/plain;
| | charset="iso-8859-1"
| | Content-Transfer-Encoding: 7bit
| | X-Newsreader: Microsoft CDO for Windows 2000
| | X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| | Thread-Index: AcNG9USr1MMBPVQOSN+6rAyfuOl2Sg==
| | Newsgroups: microsoft.public.sqlserver.security
| | Path: cpmsftngxa06.phx.gbl
| | Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.security:14430
| | NNTP-Posting-Host: TK2MSFTNGXA11 10.40.1.163
| | X-Tomcat-NG: microsoft.public.sqlserver.security
| |
| | I have just installed SQL Server for the first time and
| | created a test database using a script I was given. I
| | have created a Windows login and an SQL login for the
| | person who originally created the data base and sent it to
| | me.
| |
| | No matter what I do, or how I log in, the login code
| | crashes with the error message "Login failed for
| | user 'xxx'. Reason: Not associated with a trusted SQL
| | Server connection."
| |
| | What is the secret to convincing SQL Server that the
| | connection is trusted.
| |
| | I have searched the SQL Server 2000 Books On Line and
| | chased down many blind alleys. So far my conclusion is
| | that the books are useless. Of course, it's possible that
| | I don't know how to use the books, but then I would expect
| | the books to offer a little more help in that regard, too.
| |
| | Thanx for your help.
| |
| | JimT
| |
| |
|
|
- Next message: Usman: "user's rights"
- Previous message: ABG: "New Sysadmin cannot stop SQL instance..."
- In reply to: Bill Cheng [MSFT]: "RE: How to create a trusted connection"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
