Export (0) Print
Expand All

Services for Netware Tools and Settings

Updated: June 7, 2006

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

In this section

The “Services for NetWare Tools” section describes tools that are useful for troubleshooting Services for NetWare.

The “Services for NetWare Registry Entries” section describes the registry entries that can be configured to use the advanced features of MSDSS, such as modifying wakeup interval values and setting the maximum number of failed objects.

Services for NetWare Tools

Windows Server 2003 includes several tools that allow you to determine computer configuration settings and perform diagnostic tests to resolve communication problems in an IPX/SPX network environment used for Services for NetWare 5.03.

Dsa.msc: Active Directory Users and Computers

Category

An Active Directory Administrative Tools MMC snap-in that is automatically installed on all Windows Server 2003 domain controllers running Windows Server 2003.

Version compatibility

 

Can Be Run From Can Be Run Against

Domain controllers running:

  • Windows Server 2003, Standard Edition

  • Windows Server 2003, Enterprise Edition

  • Windows Server 2003, Datacenter Edition

Servers running:

  • Windows Server 2003, Standard Edition

  • Windows Server 2003, Enterprise Edition

  • Windows Server 2003, Datacenter Edition

  • Windows Server 2003, Web Edition

Computers running:

  • Windows XP Professional with Adminpak.msi installed

Domain controllers running:

  • Windows Server 2003, Standard Edition

  • Windows Server 2003, Enterprise Edition

  • Windows Server 2003, Datacenter Edition

  • Windows 2000 Server

  • Windows 2000 Advanced Server

  • Windows 2000 Datacenter Server

Active Directory Users and Computers provides a graphical user interface that can be used to manage users and computers in Active Directory domains.

Ipxroute

Category

Ipxroute can be used to display and modify information about the routing tables used by the IPX protocol.

Version compatibility

Ipxroute is available in Windows Server 2003, Windows 2000 Server, and Windows XP Professional.

Ipxroute enables you to troubleshoot IPX connectivity problems and provides information about the current state of the stack. Ipxroute also displays information such as current IPX status, network number, MAC address, interface name, frame type, and so on.

For example, to display information at the command-line interface for all bindings on which IPX is configured, use the ipxroute command with the config argument, as follows:

C:\>ipxroute config

To determine if there is connectivity to a specific network, use the ipxroute command with the ripout argument as follows:

C:\>ipxroute ripout <network number>

where <network number> is the 8-digit hexadecimal network number.

You can also view additional information about ipxroute options, which might assist you in troubleshooting connectivity problems. To do this, use the help switch for ipxroute, as follows:

C:\>ipxroute /?

Network Monitor

Category

Network Monitor is a utility for monitoring, recording, and analyzing network traffic.

Version compatibility

Network Monitor is part of the Microsoft Systems Management Server (SMS) product. A limited version, which can capture frames that are sent to or from the network adapter of the computer on which Network Monitor is installed, is included with Windows Server 2003 and can be installed as an optional networking component. You can use NetMon to identify network traffic patterns and to perform other tasks associated with finding network problems, such as the following:

  • Locating client-to-server connection problems.

  • Identifying computers that make a disproportionate number of service requests.

  • Capturing frames (packets) directly from the network.

  • Displaying and filtering captured frames.

  • Identifying unauthorized users on a network.

Services for NetWare Registry Entries

The following registry entries are associated with Services for NetWare.

The information here is provided as a reference for use in troubleshooting or verifying that the required settings are applied. Modifications to the registry are not validated by the registry editor or by Windows before they are applied, and as a result, incorrect values can be stored. This can result in unrecoverable errors in the system. When possible, use Group Policy or other Windows tools, such as Microsoft Management Console (MMC), to accomplish tasks rather than editing the registry directly. If you must edit the registry, use extreme caution.

Note

  • For information about additional Services for NetWare registry entries for MSDSS and FMU, see the Services for Netware 5.03 online Help.

HKEY_LOCAL_MACHINE\SYSTEM\

The following registry entries are located under HKEY_LOCAL_MACHINE\SYSTEM CurrentControlSet\Services\MSDSS\Parameters.

UseMemberAttribute

Registry path

HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Services\MSDSS\Parameters

Version

The UseMemberAttribute registry setting is available in Microsoft Services for NetWare 5.03 on Windows Server 2003.

Set this value to 1 to migrate group “member”ships using the “member” attribute of the group object. If you set the value to 0, you use the “security equal to me” attribute.

When migrating groups from NDS to Active Directory, MSDSS reads the “security equal to me” attribute by default and migrates those group members to Active Directory. Some NetWare administration tools (particularly those that operate in Bindery mode) add “member”s only to the “member” attribute. This causes a discrepancy between the group memberships displayed in NDS, eDirectory, and Active Directory after some migrations. If you experience this, set the value to 1 to allow NDS and eDirectory group members that are not marked as “security equal to me” to be migrated to Active Directory.

SyncIntervalForward or SyncIntervalReverse

Registry path

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDSS\Parameters

Version

The SyncIntervalForward and SyncIntervalReverse registry settings are available in Microsoft Services for NetWare 5.03 running on Windows Server 2003.

To modify the wakeup interval values, you can add the DWORD values SyncIntervalForward and SyncIntervalReverse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDSS\Parameters.

After these values have been added, you can indicate the wakeup interval time in seconds.

MaxFailedObjects

Registry path

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDSS\Parameters

Version

The MaxFailedObjects registry setting is available in Microsoft Services for NetWare 5.03 running on Windows Server 2003.

To modify the default value of objects that cannot be retried, you can add the DWORD value MaxFailedObjects to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDSS\Parameters.

A value of 0 in MaxFailedObjects means there is no limit for the number of failed objects.

BackupInterval

Registry path

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDSS\Parameters

Version

The BackupInterval registry setting is available in Microsoft Services for NetWare 5.03 running on Windows Server 2003.

To modify the default backup interval, create a DWORD value named BackupInterval and specify a custom interval, in seconds.

SyncEmailAddress

Registry path

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSDSS\Parameters

Version

The SyncEmailAddress registry setting is available in Microsoft Services for NetWare 5.03 running on Windows Server 2003.

You can disable the “mail” synchronization attribute by setting the DWORD value to 0 in the SyncEmailAddress registry key.

SamRename

Registry path

HKEY_LOCAL_MACHINE\SYSTEM\\CurrentControlSet\Services\MSDSS\Parameters

Version

The SamRename registry setting is available in Microsoft Services for NetWare 5.03 running on Windows Server 2003.

Active Directory, NDS, and eDirectory handle logon names differently. Active Directory provides separate attributes for logon name (samAccountName) and object naming in the directory hierarchy (that is, the relative distinguished name). NDS and eDirectory use the same attribute (that is, CN) for both purposes. The initial release of MSDSS synchronizes the directory object name (that is, the relative distinguished name maps to the CN) but does not synchronize the logon names. MSDSS in Services for NetWare 5.03 provides an option for synchronizing logon names between Active Directory, NDS, and eDirectory.

Setting the value to 1 enables MSDSS to keep both the samAccountName and relative distinguished name attributes of a user object in Active Directory synchronized with the CN attribute of the corresponding NDS or eDirectory user object.

Note

  • The session must be a two-way synchronization session to synchronize changes in NDS or eDirectory to Active Directory.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft