ODBC connection using NT authentication

I want to create an ODBC connection with windows NT authentication on two servers the domain are different and their operating
systems r also different.
(one is Windows 2K other is NT).
how can i have to go about if i have to do this.sorry i forgot to mention the version
im using SQL SERVER 7|||This should be doable as long as there is a trust relationship established between the NT domain and the W2K domain. Depending on your requirements, this might have to be a two-way trust.

Regards,

hmscott|||My $0.02 ...

I think you could do a 'pass-through' if you cant get the domains to trust eachother. Create a user on the sql server and create the same user with the same password on the other server and you should be able to connect via windows authentication. Is it a good practice? I would say No. But a work aroud if you can't have the domains trust each other.

Originally posted by hmscott
This should be doable as long as there is a trust relationship established between the NT domain and the W2K domain. Depending on your requirements, this might have to be a two-way trust.

Regards,

hmscott|||Hi,

Thanks for ur reply. My client is not beliveing tht we need trust relationship, can u please provide any link
or url where it is mentioned.
Waiting for ur reply

TIA

Originally posted by hmscott
This should be doable as long as there is a trust relationship established between the NT domain and the W2K domain. Depending on your requirements, this might have to be a two-way trust.

Regards,

hmscott|||It is very unlikely that you will get two servers in different domains (NT&W2k) working without setting up a trust between the two domains. Windows authentication uses a SID (security identifier) each computer and each user has a unique SID and the authentication should use the SID not the username. It is true to say that NT4 could be fooled depending on what service pack you used, but W2k with Active Directory will require a trust.

I recently upgraded a whole network of users from NT4 to W2k with AD in a different domain. I researched this and it will only work with a trust relationship as HMScott says. In our original plan we were going to use replication and migrate the users one by one, in the end we moved every9one ov

The way we get around such problems is to use a Role, we have one SQL username in the Role and have our application use that username. Granting ODBC connections may be quick and easy but it leaves you a bit exposed to other issues of Security & Support.

Imagine if this was not the case, any old hacker could access you databases.sql