Re: Newbie questions about 'trusted connections'

From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 10/04/04 

Date: Mon, 04 Oct 2004 12:15:27 -0600

No not really a bug. If you were using local and localhost then you
were connecting to the default instance. It sounds like you have a
default instance that is set to Windows Authentication only and a
named instance that you are using to practice 228 questions.
The drop downs don't necessarily show every available server - they
display the servers you have connected to. Once you type in a server
and connect to it, it is saved to the registry and then it displays in
the drop down. You have only connected to the default instance with
Query Analyzer that's why it's the only one that showed.

-Sue
 
On Mon, 4 Oct 2004 08:05:03 -0700, "B. Chernick"
<BChernick@discussions.microsoft.com> wrote:

>Hold everything! I found the problem but I'm still a little confused.
>
>My server settings are fine. The problem was the point in the exercise
>where you're told to go to the Query Analyzer and do a Connect.
>
>When my 'Connect to SQL Server' window pops up, it displayed two options in
>the dropdown - (local) and localhost. Neither would work. Hitting the ...
>button (the elipsis?) produced a blank list. Then I realized I could type in
>the full name of my server and that worked. (And apparently now that I've
>done that, the name is also available in the dropdown.)
>
>Please feel free to elaborate on what just happened. Is this a user
>interface bug?
>
>"Sue Hoegemeier" wrote:
>
>> A trusted connection uses Windows Authentication. So the
>> user is authenticated based on their network login. When
>> using Windows authentication, you don't pass in a user name
>> and password. You just tell the connection to use Windows
>> Authentication or a trusted connection and you are validated
>> against the network. With a SQL login, you specify a user
>> name and password and then you are validated against the
>> login information for the SQL login by SQL Server.
>> If you are creating SQL logins (vs Windows logins) and you
>> are trying to login using one of these logins, your server
>> needs to be configured for Mixed Mode security to allow both
>> Windows logins as well as SQL logins.
>>
>> -Sue
>>
>> On Sun, 3 Oct 2004 11:29:01 -0700, "B. Chernick"
>> <BChernick@discussions.microsoft.com> wrote:
>>
>> >I'm trying to do chapter 10 in the 70-228 book and I'm totally confused. I'm
>> >on Lesson 3, Chapter 10, Creating a login, and I keep getting msg 18452 (Not
>> >associated with a trusted SQL Server connection) at step 19. I've looked at
>> >every reference I have and this is just not making sense to me. First of
>> >all, could someone please explain to me in their own words what a trusted
>> >connection is and how do I create it?
>> >
>> >(I should mention that I've installed SQL Server 2000 Developer over a
>> >pre-existing MSDE2000 installation. This is all on one laptop, no network
>> >currently connected. The original MSDE server is in Windows Authentication
>> >mode. The new server, on which I'm trying to do the exercise, is in mixed
>> >mode. I did stop and restart the server before trying to login as 'Joe'.)
>>
>>