Article ID: 180788
Article Last Modified on 5/23/2003
APPLIES TO
- 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 3.0 Service Pack 2, when used with:
- Microsoft Windows NT 4.0
- Microsoft SNA Server 3.0 Service Pack 3, when used with:
- Microsoft Windows NT 4.0
- Microsoft SNA Server 4.0, when used with:
- Microsoft Windows NT 4.0
This article was previously published under Q180788
SYMPTOMS
When you move a user from one Windows NT group to another, SNA Server does not recognize the change made to the user's group until the SNABase service is stopped and restarted. This can cause unexpected user connectivity problems if access to SNA Server 3270 or APPC resources are controlled through membership within Windows NT user groups.
CAUSE
SnaBase only maintains SID information for the specific User Account in its internal SID Cache within the SnaBase service. The SID Cache does not maintain SID information based on groups that users may belong to.
RESOLUTION
To resolve this problem, obtain the latest service pack for SNA Server version 3.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
184307 How to Obtain the Latest SNA Server Version 3.0 Service Pack
SNA Server 4.0
This problem was corrected in the latest SNA Server version 4.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
STATUS
Microsoft has confirmed that this is a problem in SNA Server versions 3.0,3.0 SP1, 3.0 SP2, and 4.0. This problem was first corrected in SNA Server 3.0 Service Pack 4.
MORE INFORMATION
The update corrects the problem by allowing the SID Cache to store either the User SID or the Group SID.
Keywords: kbbug kbfix KB180788
