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

From: Jrome (jlapointe_at_isd.state.al.us)
Date: 12/23/03 

Date: Tue, 23 Dec 2003 14:23:18 -0800

Thanks Cheif!

Unfortunately, I am not the network or SQL Server
Administrator but I am passing the information on to the
LAN/SQL Administrator. Hopefully, they will know how to
set up the trust between the domains since they are all
within our same division.

My connection string is fine for using Windows
Authentication right?
Also- All users no matter what domain they are on should
be able to access the DB if the domains are trusted, right?
(and the users have SQL Server IDs)

Sorry- I am LAN ignorant and overwhelmed at present trying
to get a grip on VB.NET. (Some finger pointing going own
here but we are civil and friendly).

Ailing in Alabama
Jrome

Merry Christmas from Dixie!

>-----Original Message-----
>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.
>
>
>
>.
>

Relevant Pages

  • Re: provider: Named Pipes Provider, error: 40 - Could not open a c
    ... I have tried connecting to Sql Management Studio and it worked pretty much ... An error has occurred while establishing a connection to the server. ... under the default settings SQL Server does not allow remote connections. ... I have a sql server install / database on the web server. ...
    (microsoft.public.sqlserver.connect)
  • 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)
  • .Net framework error
    ... Unfortunately the information is very limited and usually the report just ... The application is a front end for a SQL Server 2005 Express database, ... connection string in the app config file. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: connect to named instance w/ non-default port
    ... SQL Native Client Configuration. ... An error has occurred while establishing a connection to the server. ... under the default settings SQL Server does not allow remote connections. ...
    (microsoft.public.sqlserver.connect)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)