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
application is using SQL Server Authentication (with those username and
password stuff). I'd first check your SQL Server Security configuration
before applying the hotfix and see if it is in Mixed Mode (SQL Server and
Windows Authentication). If it Windows only, change it to Mixed Mode then
restart the SQL Server service for the security configuration to take effect

"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:e9oaE9hLIHA.5980@xxxxxxxxxxxxxxxxxxxxxxx
For the benefit of the people in the group I would appreciate if you could
post back the result after you apply the hotfix.

--
Claus
"Steve Mahon" <SteveMahon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4E1935CB-DE82-49D9-BA3B-6F9AE9862BAE@xxxxxxxxxxxxxxxx
I'm confident it is as issue between Vista and SBS 2003. I've tried the
exact
same process on another Vista machine, on an XP-Pro, and an XP-Tablet
machine. SQL Management Studio Express and the application connected no
problems on both XP machines and failed with the same Trust Error on both
Vista machines. The Sever has been updated with the fixes for Vista
clients.
Here is the message text from SQL Studio Express:

I did some more research and confirmed that this is a Vista Issue. There
is
a hotfix #942003 that must be requested from Microsoft support. See
http://support.microsoft.com/kb/942003.

"Claus" wrote:

If you use Access front ends you need an ODBC driver for SQL installed.
When
you configure the ODBC driver you can use an authentication that is not
related to the user that logs on.

Running Vista against an SBS box you might also want to take a look at
this
link:
http://support.microsoft.com/kb/926505

--
Claus
"Steve Mahon" <SteveMahon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2B3B2192-B676-4FFB-A74E-42385685B79C@xxxxxxxxxxxxxxxx
We have SBS2003R2 Prem, SQL2005, ISA2004. We have several MSAccess
frontend
applications. On a remote, non sbs domain member, Vista Ultimate
machine
connected via connection manager I can browse the lan and copy a one
of
the
Access frontends to vista machine.

When I run the app and open a page with data, I get the following SQL
Server
Login error:
Connection failed: SQLState: '28000' SQL Server Error: 18452
[Microsft][ODBC
SQL Server Driver][SQL Server]Login failed for user". The user is not
associated with a trusted SQL Server connection.

I get a similar error trying to connect with SQL MGMT Studio Express.
The
server is configured for Windows Authentication, but I thought the
connection
manager takes care of the authentication. Perhaps it is a Vista issue.
I
haven't tried yet with an XP client.

Any help is appreciated.







.

Relevant Pages

  • 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: asp.net sql trusted connections between machines
    ... > connect to a remote SQL Server instance w/ Read-Write permissions. ... > connection string in the web.config. ... > Windows Authentication setting for access via IIS doesn't seem pass the ... is this impersonation behavior with IIS and Windows Authentication ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Very basic login question
    ... In order to use Windows Authentication the two computers have to be members of the same domain or trusted domains. ... you should have a login at the SQL Server on the XP Pro workstation. ...
    (microsoft.public.sqlserver.security)
  • Re: How to install and configure SQL Server 2005 on Net work and s
    ... database to backend and then link all table from front Access database to ... we never allowed user can login to sql server to do any thing, ... Each user they required Windows Authentication when they open they won ... install the sql server. ...
    (microsoft.public.sqlserver.security)
  • Re: client logins
    ... Security that seems to change the configuration from Windows Authentication ... I have retested and found that I could login with a SQL Server ...
    (microsoft.public.sqlserver.clients)