RE: Logon failed for user '(null)'..... error

From: Kevin McDonnell [MSFT] (kevmc_at_online.microsoft.com)
Date: 12/23/03

  • Next message: Jrome: "RE: Logon failed for user '(null)'..... error" 
    Date: Tue, 23 Dec 2003 21:34:53 GMT

    previous message: "The application works perfectly for the users on one
    network domain, but the error listed above appears when
    trying to access the DB application from a user's
    workstation on another domain. The user has a SQL Server
    account. "

    To make a Trusted connection the domains need to have a Trust between them.
     The users need to be defined as either a domain user or from a domain
    group.

    If the user has a SQL Server account, then you are not using Integrated
    Security. This is SQL Security. If you want to use SQL Security then you
    need to change your connection string. If you want to keep the connection
    string as is, then make sure the clients in the other domain can make a
    Trusted Connection to SQL. Add the users from the other domain in SQL
    Enterprise Manager.

    Then, either load the SQL client tools on one of the workstations & test
    connections from Query Analyser or try creating a sample ODBC DSN and
    request Windows Authentication.

    Read this information and it will make more sense.

    http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
    ol/sql/maintain/security/sp3sec/default.asp

    Thanks,

    Kevin McDonnell
    Microsoft Corporation

    This posting is provided AS IS with no warranties, and confers no rights.

  • Next message: Jrome: "RE: Logon failed for user '(null)'..... error"

    Relevant Pages

    • Re: Concurrent database access in SQL 2005 Mobile
      ... Please stick to having an "dummy" connection in Open State. ... SQL CE/Mobile has a background thread that flushes the changes ... they run for long hours and we have not seen memory leaks so far. ... then opens his work forms and it's in ...
      (microsoft.public.sqlserver.ce)
    • Re: Concurrent database access in SQL 2005 Mobile
      ... Please stick to having an "dummy" connection in Open State. ... So it is a kind of asynchronous commit which happens every 10 ... I am not sure of this claim as we have many applications built on SQL CE ... then opens his work forms and it's in ...
      (microsoft.public.sqlserver.ce)
    • Access 2003 adp/proxy security - A substitute for SYSTEM_USER()
      ... We need a way for SQL to know the nt username that initiated the proxy ... Many stored procedures and views use a UDF that also depends on ... SyUserLogin and use HostIDand HostName() to find the right row. ... We've played with the Connection dialog settings, ...
      (microsoft.public.sqlserver.connect)
    • Access 2003 adp/proxy security - A substitute for SYSTEM_USER()
      ... We need a way for SQL to know the nt username that initiated the proxy ... Many stored procedures and views use a UDF that also depends on ... SyUserLogin and use HostIDand HostName() to find the right row. ... We've played with the Connection dialog settings, ...
      (microsoft.public.access.security)
    • RE: Logging in in background
      ... wold take all kinds of modifictions as I'd need to be checking that each SQL ... my database and all have connection strings associated with them. ... I suspect that there is also an issue on the SQL Server side as I keep ...
      (microsoft.public.access.modulesdaovba)