Re: client logins

No problem...glad your up and running now. Thanks for
posting back.

-Sue

On Tue, 11 Apr 2006 09:49:01 -0700, rseedle
<rseedle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Sue:
I found a menu item Tools -> SQL Server Properties (Configuration) ->
Security that seems to change the configuration from Windows Authentication
Only to both. I have retested and found that I could login with a SQL Server
login. And your select:

select serverproperty('IsIntegratedSecurityOnly')

returned a zero so I should be able to work with both now. Thanks.

Randy

"Sue Hoegemeier" wrote:

From the error, it looks like you need to use Windows
authentication. Just because you can create a SQL login
doesn't mean the server accepts a SQL login. The SQL Server
can be configured to use Windows Authentication only.
Since you can login somehow (when you added the user), you
can check by executing:
select serverproperty('IsIntegratedSecurityOnly')
If it returns 1, your SQL Server allows Windows
authentication only and in that case you can't use SQL
logins.

-Sue

On Fri, 7 Apr 2006 14:43:02 -0700, rseedle
<rseedle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Sue:
I looked up Windows Authentication and found the procedure to create a user
using a windows authentication. I tried using the SQL Server authentication
instead. It created the user but trying to use it in the Visual Studios
server explorer, add new connection still produces the error:

Login failed for user 'new_testID'. Reason: Not associated with a trusted
SQL Server connection.

Randy

"Sue Hoegemeier" wrote:

If Windows logins work and SQL logins do not then the server
may be set to Windows Authentication only. You also need to
make sure that you also add the login as a user to whatever
database the app is using and the database user needs the
appropriate permissions. But it could be a lot of different
things. Without any specific error message, it's all just a
guess.

-Sue
SQL Server MVP

On Tue, 4 Apr 2006 19:34:01 -0700, rseedle
<rseedle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

How come when I make a SQL Server login that login can't be used to login
from my C# application (OLEDBConnection.Open()) or the properties menu
wizard.

Randy





.

Relevant Pages

  • Re: Unexpected Login Screen When Accessing SQL Data Via .NET Intra
    ... >> data and the SQL Server is on the same server. ... >> My problem is that one user has started getting a login popup ... >> right in via Windows Authentication like everyone else and like they ...
    (microsoft.public.sqlserver.connect)
  • Re: Unexpected Login Screen When Accessing SQL Data Via .NET Intranet
    ... >> data and the SQL Server is on the same server. ... >> My problem is that one user has started getting a login popup ... >> right in via Windows Authentication like everyone else and like they ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL server 2005 login issure 2
    ... My programming knowlege is pretty rusty, but if you installed SQL Server ... if you installed with Windows Authentication and then ... ALTER LOGIN sa ENABLE; ... > If by any change you have read my original post titled "SQL Server 2005 ...
    (microsoft.public.sqlserver.connect)
  • Re: Credentials not being passed with remote access
    ... allowed windows authentication to work, ... I had assumed johnx was a domain user rather than a local Windows account. ... johnx was set up as a local login on sql server. ...
    (microsoft.public.sqlserver.security)
  • Re: Connection Manager + Remote SQL Clients
    ... This error is typical of a SQL Server configuration where you are using ... Windows Authentication to connect to your backend database whereas your ... Vista machines. ...
    (microsoft.public.windows.server.sbs)
Loading