SQL Server 7.0 in NT 4.0 domain w/Trust Relationship to AD Domain

[whitedea]

All,

We have been using a VB application to access a SQL Server 7.0 (latest SP) database in an NT 4.0 Domain successfully for some time. We recently established a 2-way trust relationship to an AD domain and migrated users from the 4.0 domain to the AD domain.

A group was created in SQL giving the AD users the proper authority to the SQL database.

When the users log into the AD domain and run the VB application, the icons and two of the reports are greyed out. It appears that the users have fewer rights than in the NT 4.0 domain.

However, when I log into the AD environment and run the application, the reports run fine and all icons appear as they should (not greyed out). I have administrative rights in the AD environment but no explicit rights in the SQL database.

As a test, I have tried giving the users administrative rights in the AD environment and to the SQL database but the icons are still greyed out and 2 of the reports don't run.

Currently, I am not prepared to move this server into the AD environment nor move the database to another server. Unfortunately we no longer have any VB support at our facility.

Would anyone have any suggestions as to what might be causing this phenomenon?

Any help you can give would be much appreciated. Thank you.

ew

 

[SQLBill]

I can't answer all your questions, but....

You do have explicit rights in SQL Server. You are an administrator for the OS, therefore you fall under BUILTIN/ADMINISTRATORS in SQL Server. Check it out and you will see that login on SQL Server.

This looks more like permissions aren't set up properly on the AD. Check there first. I don't think it's a SQL Server issue since it's VB reports that aren't available.

-SQLBill

 

[whitedea]

SQLBill,

Thanks for the response.

One point of confusion -- I added the user account from the AD domain to the ADMINISTRATORS group in the nt 4.0 domain where the SQL server resides, but the application still responded as if the user did not have rights. In theory, shouldn't this have given the user the appropriate rights?

Could there be a problem with the nt 4.0 domain security that the SQL server is a member of -- orphaned rights?. Are you aware of any 2000 policies that could affect SQL authority in this way?

Thank you very much for the help.

ew