Config File Security does not Display Correct Domain Name

Last reviewed: December 3, 1997
Article ID: Q170672
The information in this article applies to:
  • Microsoft SNA Server version 2.11, 2.11 SP1, 2.11 SP2, 3.0, and 3.0 SP1

SYMPTOMS

In SNA Server Admin version 2.11 SP1, Security/Owner shows 2 fields, SNA Domain and Owner. The value displayed in the SNA Domain field is actually the value for the NT Domain, rather than for the SNA SubDomain.

With SNA Server version 3.0, in SNA Server Manager under Domain Properties/ Config File Security/Take Ownership, the fields are SNA SubDomain and Owner. The value for SNA SubDomain correctly displays the SNA SubDomain. However, the Owner field displays the complete NT Domain Name/UserName only in some cases.

For example:

  • If the NT Domain Username and/or Machine account exist in the same domain as the domain that the Owner exists in, the Owner field will display only the UserName.
  • If the NT Domain Username and/or Machine account exist in a different domain than the Owner exists in, the Owner field will display both the NT Domain Name and the UserName.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SNA Server, versions 2.11, 2.11 SP1, 2.11 SP2, 3.0, and 3.0 SP1. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words:
Keywords : prodsna snaadmin snamanager kbbuglist
Version : 2.11 2.11sp1 2.11sp2 3.0 3.0sp1
Platform : winnt
Issue type : kbbug


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: December 3, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.