sql authentication 1

[philea]

wonderring if someone out there could shed some light on a problem we are having.

We have a new application that has been developed based on sql server 2000. The SQL server is in a different domain to the application server, the two domains are not trusted.

when we try to connect to the sql server when running the application, we get a 'null' value returned which implies nt authentication is not right.

Is there a way we can override the need for windows authentication? Or would this require a step back to the developers?

 

[JamesLean]

AFAIK, you can't use Windows authentication across domains if a trust does not exist.

If you cannot set up a trust then you will need to use SQL Authentication rather than Windows (you will need to change your server to mixed mode if it is not already).

--James

 

[philea]

James,

Thanks for your reply.

The sql server is already in mixed mode? However it appears that the application is requiring nt authentication although the developers assure us that this is not the case.

Is it perhaps something in the odbc connection string??

 

[JamesLean]

Are you getting the error "Login failed for user (null). Reason: not associated with a trusted connection"?

If so, the application IS trying to connect using Windows authentication and yes, this could well be down to what connection string is being used.

--James

 

[philea]

James,

Thanks, yes that is te exact message we are getting. Thanks for your help.

Chris.

 

[SQLBill]

You need to check two things:

1. What authentication is the SQL Server instance set to use? Options are Windows Authentication Only or Mixed Mode (Windows and SQL Server Authentication allowed).

-you need it to be in Mixed Mode

2. SQL Server Logins. You need to confirm that the login you are using exists in SQL Server and is set for SQL Server Authentication.

-SQLBill

Posting advice: FAQ481-4875