Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Error: 18456, Severity: 14, State: 11 Expand / Collapse
Author
Message
Posted Wednesday, November 7, 2012 2:10 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, April 23, 2014 6:45 AM
Points: 104, Visits: 389
I have one user that is receiving this error on 5 instances out of the 8 they have access to. Let me outline our scenario:

  • There are 3 trusted domains involved in our network. I'll refer to them as DomainA, DomainB, and DomainC

  • All users are granted access and permissions through a domain group that resides on DomainA. I'll refer to this user as DomainA\DevGroup

  • The account for the user in question resides on DomainB. I'll refer to this account as DomainB\DevUserA

  • The 3 instances the user can access reside on either DomainA (the domain the group resides) or DomainB (the domain the user account resides)

  • The 5 instances the user cannot access reside on DomainC


Now here is an oddity, there are about 15 other developers in this same group that can access all 8 servers just fine. We've ran our security with this setup for 8-10 years so nothing with that has changed on that front. This is a new employee in a different geographic location but serves the same role as the other 15 developers.

When I execute xp_logininfo to see what groups this user belongs to I get the results below. Note these results are consistent across all 8 servers:
exec xp_logininfo @acctname='DomainB\DevUserA', @option='all';

Results:
account name		type	privilege	mapped login name	permission path
DomainB\DevUserA user user DomainB\DevUserA DomainA\DevGroup

Now if I run xp_logininfo to get the members of all the groups I get mixed results (but their consistent per domain if that makes sense):
exec xp_logininfo @acctname='DomainA\DevGroup', @option='members';

Results:

  • When ran on any instance in DomainA the results yield all of the other 15 users

  • When ran on any instance in DomainB the results yield only this 1 user

  • When ran on any instance in DomainC the results yield all of the other 15 users


Any thoughts on this one? At first glance this appears to me there is some sort of issue with DomainC authenicating accounts on DomainB, perhaps due to some sort of double-hop issue going through DomainA.

Thanks in advance and sorry for the long winded post. I just wanted to make sure I provided all the facts and troubleshooting I've done so far.
Post #1382171
Posted Thursday, November 8, 2012 7:15 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, April 23, 2014 6:45 AM
Points: 104, Visits: 389
Is this perhaps a tough one? lol - any thoughts anyone?
Post #1382476
Posted Wednesday, November 14, 2012 7:53 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, April 23, 2014 6:45 AM
Points: 104, Visits: 389
Just an update, our domains are configured liked so:

ForestA ForestB
| |
DomainB DomainC
|
DomainA
(child domain)
Post #1384641
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse