Re: error-"not associated with a trusted ..."

From: Kalen Delaney (kalen_please_reply_on_public_newsgroups_delaney@compuserve.com)
Date: 03/27/03

  • Next message: Kevin Gurney: "public role" 
    From: "Kalen Delaney" <kalen_please_reply_on_public_newsgroups_delaney@compuserve.com>
Date: Thu, 27 Mar 2003 07:55:20 -0800

    When you CONNECT to your SQL Server, you have to choose one or the other,
    but Kim is talking about the configuration of the server itself. The server
    must be set up to ALLOW both Windows Authentication and SQL Authentication.
    The other choice is WIndows only. SQL Server 2000 cannot be configured to
    only allow SQL Server authentication.

    Use Enterprise Manager, right click your server name and choose Properties.
    In the properties dialog, select the Security Tool. There you will see the
    two choices, for SQL Server and Windows authentication, or for Windows only.
    Make sure you choose the one for both. Stop and restart your SQL Server.

    HTH 

    --
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"James King" <jking@iprimus.ca> wrote in message
news:4faa01c2f468$b4b32290$a101280a@phx.gbl...
> Yes, I stopped and started the SQL Server service. Maybe a
> reboot would be needed?
>
> Also, there is no choice in the dialog box for "both
> Windows and SQL authentication".  I can choose Windows,or
> I can choose SQL Server.  Is this a problem?
>
> Thanks,
>
> James
>
>
> >-----Original Message-----
> >It really sounds like your server is not running with
> both Windows and SQL
> >Auth. (sounds like Windows Only). Have you stopped and
> restarted SQL Server
> >after this change?
> >
> >hth,
> >kt
> >
> >**** Please reply only on the newsgroups! Include
> dml/ddl, when possible.
> >Thanks ****
> >Kimberly L. Tripp
> >President, SYSolutions, Inc. www.SQLSkills.com
> >Principal Mentor, Solid Quality Learning
> www.SolidQualityLearning.com
> >
> >
> >"James King" <jking@iprimus.ca> wrote in message
> >news:4ddd01c2f3dc$e80d5de0$3301280a@phx.gbl...
> >> Hi, I'm new to SQL Server. I have SQL Server 2000
> running
> >> on WinNT, and have set it up with SQL authentication. I
> >> can connect fine locally, but I also want to be able to
> >> connect remotely from my laptop (Win2000). On the
> laptop I
> >> can see the SQL Server in Enterprise Manager(also set up
> >> to use SQL authentication), but when I try to connect I
> >> get the error:
> >> "A connection could not be established to .... Reason:
> >> Login failed for user jking. Not  associated with a
> >> trusted SQL Server connection."
> >> What's wrong?
> >> Thanks for your help.
> >
> >
> >.
> >
  • Next message: Kevin Gurney: "public role"

    Relevant Pages

    • Re: Slow booting xp home.
      ... Changing the boot order to boot first from your hard disk might save you a half second, but you won't be able to boot from a CD until you change it back - and the time spent to do that will erase any previous time saved. ... 2- Consider what software you really want to start with Windows and also how you've configured your applications at startup ... Installing and Registering Visual Studio Express Editions Smart Device ...
      (microsoft.public.windowsxp.perform_maintain)
    • Re: BizTalk 2004 MSDTC
      ... >I have a multicomputer configuration: ... SQL Server installed on a Windows 2000 Server ... The problem I am having is that with MSDTC ...
      (microsoft.public.biztalk.general)
    • Re: Slow booting xp home.
      ... Thirty seconds to boot Windows? ... I read somewhere that Microsoft suggest 30s boot up on xp home, I have seen videos on youtube of 8s boot up on xp, I'd be delighted with 30s and happy just to get below a minute. ... Installing and Registering Visual Studio Express Editions Smart Device ...
      (microsoft.public.windowsxp.perform_maintain)
    • Re: Remote connection failed
      ... If you are going over a remote connection or are not logging ... into the domain where SQL Server is then no, Windows ... authentication won't work. ...
      (microsoft.public.sqlserver.connect)
    • Getting to the bottom of MSDE network connection problems ...
      ... but other than that it is MSDE 2000 with sp3a already applied. ... I've finally figured out the connection problems associated with this, ... and it seems the problems are due to Windows XP and not MSDE. ... the enterprise/standard versions of SQL server won't install ...
      (microsoft.public.sqlserver.msde)