Error: 18456, Severity: 14, State: 11

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2008 Forums

SQL Server Administration (2008)

Error: 18456, Severity: 14, State: 11

Author

Topic

tfountain
Constraint Violating Yak Guru

491 Posts

Posted - 2012-11-07 : 16:21:06

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.

chadmat
The Chadinator

1974 Posts

Posted - 2012-11-09 : 03:13:34

Can you ensure the user is connecting via TCPIP? Kerberos won't double hop on named pipes etc..

-Chad

tfountain
Constraint Violating Yak Guru

491 Posts

Posted - 2012-11-12 : 11:57:10

Chad, I'm checking into that now with the user. Unfortunately they are slow to respond :( .

tfountain
Constraint Violating Yak Guru

491 Posts

Posted - 2012-11-14 : 09:55:09

Chad, the user is configured to use the default which should be TCP/IP. I did have the user change it to TCP/IP to see if it resolves the issue and it did not. I really suspect this is more of a domain issue though. Unfortunately that's not my forte so I'm reading up on the stuff now.

tfountain
Constraint Violating Yak Guru

491 Posts

Posted - 2012-11-14 : 09:56:49

Just an update, our domains are configured liked so:


     ForestA           ForestB
        |                 |
     DomainB           DomainC
        |
     DomainA
  (child domain)

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources