Login failed for user '(null)'...Reasons?

A SQL Server (in another domain) I'm trying to connect to with SQL Server
authentication (UID and password) fails from an Access application. I've
tried a ODBC DSN and a DSN-less connection. The SQL Server is running in
mixed authentication mode.
I can get to the SQL Server with Enterprise Manager, can successfully test
the connection with the DSN in the ODBC Administrator, and can successfully
test the connection via a UDL test (OLEDB)...just not through an Access 2000
application.
Can anyone provide the various possible reasons for...
Connection failed:
SQLState: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'(null)'. Reason: Not associated with a trusted SQL Server connection.
...?
Why is the SQL Server receiving a null UID?
Thanks,
JoeIn order for the server to accept the connection attempt it needs to
"authenticate" that the user is some that has rights (user needs the ability
to connect to the \\servername\ipc$ share). This step happens before SQL
Server gets a change to interrogate the credentials. See Books Online
"Authentication Modes" for more detail.
Steve
"JRE" <nomail@.all> wrote in message
news:#FMgYTUAEHA.3316@.TK2MSFTNGP11.phx.gbl...
> A SQL Server (in another domain) I'm trying to connect to with SQL Server
> authentication (UID and password) fails from an Access application. I've
> tried a ODBC DSN and a DSN-less connection. The SQL Server is running in
> mixed authentication mode.
> I can get to the SQL Server with Enterprise Manager, can successfully test
> the connection with the DSN in the ODBC Administrator, and can
successfully
> test the connection via a UDL test (OLEDB)...just not through an Access
2000
> application.
> Can anyone provide the various possible reasons for...
> Connection failed:
> SQLState: '28000'
> SQL Server Error: 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed fo
r user
> '(null)'. Reason: Not associated with a trusted SQL Server connection.
> ...?
> Why is the SQL Server receiving a null UID?
> Thanks,
> Joe
>
>|||Thanks... Proper user accounts exist on both domains in question.
"Steve Thompson" <SteveThompson@.nomail.please> wrote in message
news:%233d64rVAEHA.2484@.TK2MSFTNGP12.phx.gbl...
> In order for the server to accept the connection attempt it needs to
> "authenticate" that the user is some that has rights (user needs the
ability
> to connect to the \\servername\ipc$ share). This step happens before SQL
> Server gets a change to interrogate the credentials. See Books Online
> "Authentication Modes" for more detail.
> Steve
> "JRE" <nomail@.all> wrote in message
> news:#FMgYTUAEHA.3316@.TK2MSFTNGP11.phx.gbl...
Server
test
> successfully
> 2000
>|||On SQL Server, enabled auditing for "failed logins" and see if the accounts
are being rejected by SQL Server.
Security auditing at the server level should indicate if the user account is
failing to get a server connection.
Steve
"JRE" <nomail@.all> wrote in message
news:OmopmQtAEHA.1548@.TK2MSFTNGP12.phx.gbl...
> Thanks... Proper user accounts exist on both domains in question.
> "Steve Thompson" <SteveThompson@.nomail.please> wrote in message
> news:%233d64rVAEHA.2484@.TK2MSFTNGP12.phx.gbl...
> ability
> Server
I've
in
> test
Access
>|||Joe,
See if this thread helps:
http://groups.google.com/groups?q=E...SQLServerTables Do you know
what piece of the Access application is raising the error?
SK
JRE wrote:

>A SQL Server (in another domain) I'm trying to connect to with SQL Server
>authentication (UID and password) fails from an Access application. I've
>tried a ODBC DSN and a DSN-less connection. The SQL Server is running in
>mixed authentication mode.
>I can get to the SQL Server with Enterprise Manager, can successfully test
>the connection with the DSN in the ODBC Administrator, and can successfully
>test the connection via a UDL test (OLEDB)...just not through an Access 200
0
>application.
>Can anyone provide the various possible reasons for...
>Connection failed:
>SQLState: '28000'
>SQL Server Error: 18452
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
>'(null)'. Reason: Not associated with a trusted SQL Server connection.
>...?
>Why is the SQL Server receiving a null UID?
>Thanks,
>Joe
>
>
>|||Thanks...I checked out the article. That's pretty much what I do to connect
to a SQL Server back end. The error I get is not an Access error. It's
generated by SQL Server.
"Steve Kass" <skass@.drew.edu> wrote in message
news:u$eUJJZBEHA.1544@.TK2MSFTNGP09.phx.gbl...
> Joe,
> See if this thread helps:
> http://groups.google.com/groups?q=E...SQLServerTables Do you know
> what piece of the Access application is raising the error?
> SK
> JRE wrote:
>
test
successfully
2000
>|||Thanks. I'll pass this on to the SQL Server admin.
"Steve Thompson" <SteveThompson@.nomail.please> wrote in message
news:e1yyddtAEHA.1456@.TK2MSFTNGP09.phx.gbl...
> On SQL Server, enabled auditing for "failed logins" and see if the
accounts
> are being rejected by SQL Server.
> Security auditing at the server level should indicate if the user account
is
> failing to get a server connection.
> Steve
> "JRE" <nomail@.all> wrote in message
> news:OmopmQtAEHA.1548@.TK2MSFTNGP12.phx.gbl...
SQL
> I've
running
> in
successfully
> Access
connection.
>|||Joe,
I know the error is a SQL Server error, but I wanted to know at what
point in your Access application that error is raised - is it a specific
line of VB code, is it when a specific form is opened, etc.? Since you
get the error when you run the Access application, there must be a way
to debug the Access application to see exactly at what point the error
occurs, and what Access is doing at that moment.
SK
JRE wrote:

>Thanks...I checked out the article. That's pretty much what I do to connect
>to a SQL Server back end. The error I get is not an Access error. It's
>generated by SQL Server.
>"Steve Kass" <skass@.drew.edu> wrote in message
>news:u$eUJJZBEHA.1544@.TK2MSFTNGP09.phx.gbl...
>
>test
>
>successfully
>
>2000
>
>
>