Some SNACFG Options Fail using a German version of Windows NTLast reviewed: February 17, 1998Article ID: Q181099 |
The information in this article applies to:
SYMPTOMSThere are multiple problems using the SNACFG command line utility when the SNA Server is running on a German version of Windows NT. They include the following:
to the "Everyone" group on the US version of Windows NT).3. SNACFG USER cannot add local groups.
CAUSEString comparisons of user names needed to be localized. Instead of using stricmp(), set the system locale to OS native and use stricoll() which properly compares upper and lower case non-US characters. The local groups problem results because SnaCfg mishandles the fact that LookupAccountSid() returns ERROR_NONE_MAPPED for local group names. The error causes no SID to be found for the group, but SnaCfg adds it anyway, leaving the userSidBlock in the config record full of zeros and the type set to User, not Group. A solution is to strip off the domain name and retry LookupAccountSid. If it works this time, and the returned SID is SidTypeAlias, then the returned RefDomain will be "BUILTIN" (or its localized equivalent). In this case, replace the RefDomain with the domain name from the command line and continue. If the second LookupAccountSid doesn't work either, then fail as before. Then, if there is a valid SID for the user or group, it is used with LookupAccountSid to get the proper case of the user name string.
STATUSMicrosoft has confirmed this to be a problem in SNA Server versions 2.11, 2.11 SP1, 2.11 SP2, 3.0, 3.0SP1, 3.0SP2, 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.
|
Additional query words: snacfg
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |