connect error with Windows Security

My Windows2000\SQL2000 server uses Windows Only security from a NT 4 domain.
My Win2000 client logs in to AD, not the NT4 domain. I am getting sql conne
ct errors 123 and 53 when I try to create a DSN and add my NT4 domain creden
tials. Does anyone know how
to create a DSN using credentials other than the one I am logged in as?
Thanks.Could you post the exact error messages you get?
If you are creating a DSN to use Windows authentication, you
don't specify a user name and password. You just select NT
authentication for the login info. The login must exist on
the server and if you selected a database for the DSN, the
user must exist in the database.
-Sue
On Mon, 24 May 2004 13:36:07 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:

>My Windows2000\SQL2000 server uses Windows Only security from a NT 4 domain. My Win
2000 client logs in to AD, not the NT4 domain. I am getting sql connect errors 123 a
nd 53 when I try to create a DSN and add my NT4 domain credentials. Does anyone know
ho
w to create a DSN using credentials other than the one I am logged in as?
>Thanks.|||I am trying to create a user DSN and specify server name on the first screen
. On the security screen, it defaults to my AD login credentials, so I click
sql security, enter my NT4 domain credentials, then click Windows security.
The error I get is " SQLSt
ate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated w
ith a trusted SQL Server connection"|||The error means you are attempting to login to SQL Server
using windows authentication and the login was not able to
be validated. On the SQL Server end, make sure that the
login exists on the server.If the login exists, try dropping
and recreating and see if that makes a difference for that
login. But if the login is fine then it's likely a Windows
authentication issue. You can check the event logs for
network related issues, problems contacting a domain
controller, that type of thing. You can also try to force
the client to connect through named pipes by creating a
named pipe alias using the Client Network Utility.
-Sue
On Tue, 25 May 2004 07:06:03 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:

>I am trying to create a user DSN and specify server name on the first screen. On th
e security screen, it defaults to my AD login credentials, so I click sql security,
enter my NT4 domain credentials, then click Windows security. The error I get is " S
QLS
tate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated with a trusted S
QL Server connection"
>
>