SQL Server Issue - Sharing across domains

Leesha
BronzeLounger
Posts: 1488
Joined: 05 Feb 2010, 22:25

SQL Server Issue - Sharing across domains

Post by Leesha »

Hi,

IT Created A new server named “TTT-One” was relocated from “old domain” to “new domain”. The new domain is TTTSM. When it was copied away from old domain, the “LOCAL” administrator account of the server was added to all the SQL database security permissions as well as to one security section of the entire SQL Server.

Now…the server is joined to the “new domain(TTTSM)”. SQL Studio works if you log into the server as LOCAL administrator (TTT-One\Administrator). We are able to see the correct user accounts in each database AND can add users to each database. If we TRY TO add the “new domain user accounts”….such as TTTSM\Administrator we get errors that we don't have permission to do this. If you log into the server as domain administrator (TTTSM\Administrator)…it does not work. We aren't able to get into SQL as we are told we don't have permission. We can only get in under the local account.

Does anyone know how to get past this?

Thanks,
Leesha

User avatar
HansV
Administrator
Posts: 78532
Joined: 16 Jan 2010, 00:14
Status: Microsoft MVP
Location: Wageningen, The Netherlands

Re: SQL Server Issue - Sharing across domains

Post by HansV »

I'm sorry, I cannot help you with this.
Best wishes,
Hans

User avatar
Gasman
2StarLounger
Posts: 104
Joined: 22 Feb 2022, 09:04

Re: SQL Server Issue - Sharing across domains

Post by Gasman »

This would be for IT to sort out surely?
Using Access 2007/2019.
Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime.
Please, please use code tags when posting code snippets, click the </>icon.
Debug.Print is your lifesaver.

User avatar
Michael Abrams
4StarLounger
Posts: 574
Joined: 10 Feb 2010, 17:32

Re: SQL Server Issue - Sharing across domains

Post by Michael Abrams »

Gasman wrote:
25 Apr 2024, 10:50
This would be for IT to sort out surely?
You would think :hairout:

I've been here for 20 years, and roughly 50% of the time, IT couldn't hep (meaning they didn't know or couldn't find out) and I got some really incredible solutions here.

Didn't mean to hijack here, but "IT's problem" becomes the user's problem :scratch:

Michael