Login failed for user (null). Reason: Not associated with a trusted SQL Server connection.

Anyone,

I have a user "john" whose machine is part of the "job" domain. He is
trying to establish an odbc connection to an MS SQL 2000 server on the
"school" domain. He uses Windows authentication to establish the odbc
connection however it gives the error "Login failed for user '(null)'.
Reason: Not associated with a trusted SQL Server connection."

I am guessing that the odbc connection is trying to pass the
credentials of job\john to the sql server. And since the sql server
is on the school domain it expects the credentials of school\john. Is
there anyway to specify the username and password so that this will
work even though the servers are on different domains without having
to trust the domains? Thanks in advance for
any help on this!!

TonyTo log into SQL Server, the user needs a SQL Server login. If your SQL
Server is set up to use NT Authentication or mixed mode authentication on
the Schools domain, then give John a login on the Schools domain and have
him login using those credentials.

"TBone" <tony.despain@.gmail.com> wrote in message
news:64b1ef71.0411261033.1044c9e9@.posting.google.c om...
> Anyone,
> I have a user "john" whose machine is part of the "job" domain. He is
> trying to establish an odbc connection to an MS SQL 2000 server on the
> "school" domain. He uses Windows authentication to establish the odbc
> connection however it gives the error "Login failed for user '(null)'.
> Reason: Not associated with a trusted SQL Server connection."
> I am guessing that the odbc connection is trying to pass the
> credentials of job\john to the sql server. And since the sql server
> is on the school domain it expects the credentials of school\john. Is
> there anyway to specify the username and password so that this will
> work even though the servers are on different domains without having
> to trust the domains? Thanks in advance for
> any help on this!!
> Tony|||Hi

The school domain needs to trust the job domain to allow this to occur. You
could use SQL Server authentication instead if you don't want this trust to
occur.

John

"TBone" <tony.despain@.gmail.com> wrote in message
news:64b1ef71.0411261033.1044c9e9@.posting.google.c om...
> Anyone,
> I have a user "john" whose machine is part of the "job" domain. He is
> trying to establish an odbc connection to an MS SQL 2000 server on the
> "school" domain. He uses Windows authentication to establish the odbc
> connection however it gives the error "Login failed for user '(null)'.
> Reason: Not associated with a trusted SQL Server connection."
> I am guessing that the odbc connection is trying to pass the
> credentials of job\john to the sql server. And since the sql server
> is on the school domain it expects the credentials of school\john. Is
> there anyway to specify the username and password so that this will
> work even though the servers are on different domains without having
> to trust the domains? Thanks in advance for
> any help on this!!
> Tony