Abstract: A method of discovering native or non-native authentication server domains and managing information about such domains in a computer network. The various domains are “discovered” by issuing requests from the client to one or more of the servers in the network. Each response is then characterized as being from a native or non-native server, and a list of each such server type is then compiled at the client. The administrator may modify the list, for example, by adding or removing server domains, or may apply a discovery “policy” to tailor the way in which a user may access and interact with the discovered information.

Abstract: A user is authenticated at a client machine running a native operating system. Authentication may be effected from one or more non-native server domains including, without limitation, a Server Message Block (SMB) server domain, a DCE Cell, or some other non-Windows NT server domain. Following successful authentication, a user account is dynamically established or updated at the client by retrieving from the server user information and a set of "group" privileges associated with the authenticated user. A local representation of these privileges is then dynamically created on the client, after which the privileges are linked to the user account to make the user a member of the local representation. In this manner, the group information is saved on the local machine and the authenticated user is afforded appropriate access rights to the client and the server.

Abstract: A user is authenticated at a client machine running a native operating system. Authentication may be effected from one or more non-native server domains including, without limitation, a Server Message Block (SMB) server domain, a DCE Cell, or some other non-Windows NT server domain. Following successful authentication, a user account is dynamically established or updated at the client by retrieving from the server user information and a set of "group" privileges associated with the authenticated user. A "user profile" is retrieved from the non-native server domain and used to establish at the client a user desktop and any preferences associated with the user.

Abstract: A method of authenticating a user of a Windows NT client normally configured against an account held at a Windows NT server. The method begins in response to a logon request at the client. In particular, the user is provided with an option to select a server domain from a set of one or more native Windows NT server domains and/or non-native server domains for authentication. The list of native and/or non-native server domains is compiled by an administrator (e.g., during installation) or by the user (at logon). In response to user selection of the server domain, a connection is then established between the Windows NT client and the server domain. The user is then authenticated at the server domain. Following successful authentication of the Windows NT client at the server domain, a Windows NT user account is then established and maintained at the client.

Abstract: A method of discovering native or non-native authentication server domains in a computer network. The various domains are "discovered" by issuing requests from the client to one or more of the servers in the network. Each response is then characterized as being from a native or non-native server, and a list of each such server type is then compiled at the client. If desired, the administrator may then apply a discovery "policy" to tailor the way in which a user may access and interact with the discovered information.

Abstract: A method and architecture for the administration of large cells in an Open System Foundation/Distributed Computing Environment (OSF/DCE). The architecture organizes the Cell Directory Service (CDS) name space of the OSF/DCE to allow a network administrator to easily determine network resources under their control, and work with a subset of the network resources. The OSF/DCE name space is organized as resource realms having a CDS component and a registry component. The CDS component of the resource realms has a fixed portion containing at least two roots describing sub-systems and realm resources (e.g., printer, serial devices, etc.). The CDS component also contains individual realms defined directly below the fixed portions. The registry component has a root consisting of the security, group and realm portions. Individual realms are defined as directories below the root.