Microsoft KB Archive/150454

= Assigning different LUs to common groups in SNA Server =

Article ID: 150454

Article Last Modified on 8/26/2004

-

APPLIES TO


 * Microsoft SNA Server 2.0, when used with:
 * Microsoft Windows NT 4.0
 * Microsoft SNA Server 2.1, when used with:
 * Microsoft Windows NT 4.0
 * Microsoft SNA Server 3.0, when used with:
 * Microsoft Windows NT 4.0
 * Microsoft SNA Server 3.0 Service Pack 4, when used with:
 * Microsoft Windows NT 4.0
 * Microsoft SNA Server 4.0, when used with:
 * Microsoft Windows NT 4.0
 * Microsoft SNA Server 4.0 Service Pack 1
 * Microsoft SNA Server 4.0 Service Pack 2
 * Microsoft SNA Server 4.0 Service Pack 3
 * Microsoft SNA Server 4.0 Service Pack 4
 * Microsoft Host Integration Server 2000 Standard Edition
 * Microsoft Host Integration Server 2000 Service Pack 1

-



This article was previously published under Q150454



SUMMARY
It is not recommended that you assign different LUs to user groups that have members in common because the results cannot be predicted.



MORE INFORMATION
According to the SNA Server version 3.0 "Administration Guide," Chapter 3: If a user is assigned LUs through one or more accounts, such as group accounts and the user's individual account, the LUs do not accumulate. Instead, one account determines the access for that user. The account that determines this access is the account found first in the following search order:
 * 1) User accounts (highest priority)
 * 2) Domain groups
 * 3) Local groups
 * 4) Well-known groups such as Everyone (lowest priority)

However, it does not explain clearly what will happen if two groups are at the same level (2 local groups).

SNA Server will use the LUs assigned to whichever group is returned first from Microsoft Windows NT, and there is no way to predict the order in which the groups will be returned.

Additional query words: ProdSNA

Keywords: kbinfo kbnetwork kbsnaonly KB150454

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.