Specifications

Joining a Windows Workgroup, Domain, or Active Directory
80 Snap Server Administrator Guide
Joining a Windows Workgroup, Domain, or Active
Directory
Once joined to a Windows NT, Windows 2000 or Active Directory domain, the Snap
Server imports, and then maintains a current list of the users and groups on the
domain.
Notes on Windows Authentication
• You cannot modify Windows domain user or group accounts locally —
You must
use the domain controller to make modifications. Changes you make on the
domain controller appear automatically on the Snap Server.
• Group Quotas are not available for Windows Domain Groups —
All other Snap
Server features, such as user quotas, share access, and ACLs on files and
directories are available to Windows domain users and groups
• Kerberos authentication —
The Snap Server will use Kerberos for authentication
in ADS domains.
• Support for Microsoft name resolution servers —
The Snap Server supports both
of the Microsoft name resolution services: Windows Internet Naming Service and
Dynamic Domain Name Server. However, when you use a dynamic domain
server or a domain name server with an ADS server, make sure that the forward
and reverse name lookup is correctly set up.
Interoperability with Active Directory Authentication
The Snap Server supports the Microsoft Windows 2000 family of servers that run in
native Active Directory Services (ADS) mode or in mixed NT/ADS mode. Snap
Servers can join Active Directory domains as member servers. References to the
Snap Server's shares can be added to the LDAP database by creating a new shared
folder object under an Organizational Unit.