Assigning Different LUs to Common Groups in SNA Server

Last reviewed: April 17, 1997
Article ID: Q150454

The information in this article applies to:
  • Microsoft SNA Server for Windows NT, versions 2.0, 2.1, 2.11, and 3.0

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 “Administration Guide,” Chapter 6:

   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 : kbnetserv kbnetwork
Version : 2.0 2.1 2.11 3.0
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 17, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.