Dell PowerVault 715N (Rackmount NAS Appliance) - Manual (Page 68)

have the same frame type, so that they can communicate with the rest of the network.
When you are configuring your system, it attempts to automatically detect the frame type for the client. In most cases,
this is successful. However, occasionally the automatic detection feature selects an inappropriate frame type, usually
because more than one frame type exists on the network. If this happens, you should manually set the frame type to
match the one specified on your NetWare server. Note that if more than one frame type exists, select the one that is
detected first. For example, if frame type Ethernet 802.2 and Ethernet 802.3 are bound to the same segment, then
configure frame type Ethernet 802.2. The order of detection is Ethernet 802.2, Ethernet 802.3, Ethernet II, and
then Ethernet SNAP.
Microsoft Directory Synchronization Services
Microsoft Directory Synchronization Services (MSDSS) allows you to synchronize a wide variety of data stored in the
Active Directory service with Novell Directory Service (NDS) and NetWare 3.x binderies.
MSDSS is a highly flexible service that helps Novell users:
Adopt Windows 2000 Server and the Active Directory service.
Reduce directory management through two-way synchronization.
Migrate NDS and bindery information to Windows 2000 Server.
MSDSS supports two-way synchronization with NDS and one-way synchronization with NetWare 3.x binderies to provide a
complete directory interoperability solution. MSDSS also supports password synchronization and provides a directory
migration service.
MSDSS allows NetWare users to deploy Active Directory without having to replace existing directories or bear the cost of
managing two separate directories. As a result, users have the flexibility to:
Consolidate directory management when multiple directories are required.
Manage accounts from either directory.
Use directory-enabled applications, devices, and services based on the Windows 2000 Active Directory service.
MSDSS is easy to use and makes synchronization and Active Directory setup easy through its management interface. It is
fully featured to allow users a choice of management, synchronization, and migration options.
MSDSS supports all major NetWare platforms and most Novell directories and binderies, and it includes support for
IPX/SPX and TCP/IP network protocols.
Windows 2000 MSDSS Domain Controller
To implement MSDSS, you must install the Windows 2000 Server operating system and the MSDSS software (available on
the Microsoft Services for NetWare Version 5 CD) on at least one system. In Windows 2000, when you promote a system
running Windows 2000 Server to an Active Directory server, it becomes a domain controller. You use this domain
controller to configure Active Directory, install MSDSS, and then import information from the existing NetWare
environment.
The larger the environment, the more new servers you need. If you are planning to have more than one domain, then
you need new hardware for the first domain controller in each domain.
You must also install Novell Client Access software on the MSDSS server or servers. MSDSS uses Novell Client Access to
authenticate and to access NDS. While accessing NDS, it authenticates, but does not use a license. MSDSS also uses
Novell Client Access to map one directory's contents to another, taking into account the fact that the object classes in
Novell's NDS or bindery directories are different from Active Directory object classes. Novell Client Access is also required
to use File Migration utility to migrate files.
You can install Novell Client Access in four modes: IP only, IPX only, IP and IPX combined, and IP with IPX
Compatibility Mode. Most NetWare environments still use IPX today. MSDSS works in all the modes because it uses
Novell Client Access to access the lower layers.
If you are migrating NDS, you can import the user and group information from one NDS server to the MSDSS server
because you have one user database per tree. You can then migrate the file system. Remember that each Novell server
has its own file system, which is not replicated to other servers (whereas NDS is replicated to other servers). After the
files are migrated, you can uninstall NDS from the server to provide more space for the Windows 2000 Server operating
system.