How can we help you today? How can we help you today?
lehrsj24
The only issue is with Windows authentication. I have two domains, let's say A and B. I have a SQLMonitor server on domain A. I have another one on domain B. The service account used for both of these domains is a single service account from domain A. It works fine in both domain A and domain B as this single service account has rights to the SQL servers in domain A and B. It has all the rights it needs to run and gather the data from SQL Monitor. There are no user rights issues for this. The problem is that if I set up Windows Authentication then in domain A, when setting it up, I specify a windows account that is going to check AD to determine if other windows users have rights when they log in. In domain A the only account it will allow is a windows account from domain A. And in domain B the only windows account it will use is an account from domain B. This too isn't a problem as I can use a different account for each of the servers. The problem is on the SQL Monitor server on Domain A, I can't add users from Domain B. It says it can't find them. And on the SQL monitor server on domain B it won't allow me to add users from domain A. It can't find them. It appears that it can only authenticate a user in a single domain - even though domain A and domain B have a full trust relationship. From the way this is working I it appears to me that windows authentication can only validate users in a single domain. / comments
The only issue is with Windows authentication. I have two domains, let's say A and B. I have a SQLMonitor server on domain A. I have another one on domain B. The service account used for both...
0 votes