RE: odbc connection multi domain no trust

From: Rand Boyd [MSFT] (rboyd_at_onlinemicrosoft.com)
Date: 11/17/04 

Date: Wed, 17 Nov 2004 17:49:20 GMT

If there is no domain trust then you will either need to use SQL
authentication or create NT accounts on the SQL Server machines that mirror
the accounts that the users logon to their client machines with. The
accounts will have to have the same name and password. Using this method
you can use NT authentication to SQL Server.

Rand
This posting is provided "as is" with no warranties and confers no rights.

Relevant Pages

  • Re: User ASPNET in SQL Server 2000
    ... When you hit a web application that has anonymous access, ... While I love integrated security in SQL Server, it is often a pain in web ... maintenance of accounts with access. ... >>> authentication", and has the same users as in Win 2000 ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Impersonation ASPNET SQL Server
    ... I think you need to impersonate those user accounts in asp.net ... !Subject: Re: Impersonation ASPNET SQL Server ... Authentication, and Secure Communication is just one ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Hlep with Simple questions about Authentication
    ... Valid SQL Server login accounts and passwords are not related to ... must supply the SQL Server login and password when you connect to SQL Server. ... >> B has windows logon info as UserB and PasswordB. ... >> The Sql Server is set to Windows and Sql Serevr Mixed Authentication Mode, ...
    (microsoft.public.sqlserver.security)
  • Re: SQL2K Restrication by IP address
    ... authentication you can limit Win accounts to log on from specific computers ... If your computers have static IP ... Dejan Sarka, SQL Server MVP ...
    (microsoft.public.sqlserver.security)
  • Re: SQL2K Restrication by IP address
    ... authentication you can limit Win accounts to log on from specific computers ... If your computers have static IP ... Dejan Sarka, SQL Server MVP ...
    (microsoft.public.sqlserver.security)
Loading