Changing User Rights Isn't Recognized Until Snabase is Restarted

• Microsoft SNA Server, versions 3.0, 3.0SP1, 3.0SP2, 4.0

SYMPTOMS

When moving 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 is controlled through membership within Windows NT user groups.

CAUSE

The problem is caused because 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.

STATUS

Microsoft has confirmed this to be a problem in SNA Server versions 3.0, 3.0 SP1, 3.0 SP2, and 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Product Support Services for more information.

MORE INFORMATION

The update corrects the problem by allowing the SID Cache to store either the User SID or the Group SID.

Keywords          : kbbug3.00 kbbug3.00.sp1 prodsna snaadmin snabaseservice kbbug3.00.sp2 kbbug4.00 kbbuglist
Version           : WINDOWS:3.0,3.0SP1,3.0SP2,4.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix