Copyright: Services for NetWare Networks
Citation: Services for NetWare Networks


Welcome
Welcome	1 of 3

Welcome

This manual provides information on the Gateway Service for NetWare® and the Migration Tool for NetWare. These features of Microsoft® Windows NT™ Server provide connectivity with NetWare and provide a migration path from NetWare to Windows NT Server.

Microsoft Windows NT Server integrates well with existing networks, including Novell® NetWare networks. To provide maximum connectivity in today's heterogeneous network environment, Windows NT Server and Windows NT Workstation support the native protocol for NetWare networks, IPX/SPX, and provide client software for connectivity to NetWare servers.

Windows NT provides IPX/SPX through the NetWare Link IPX/SPX Compatible Transport (NWLink). NWLink supports connectivity between computers running Windows NT and computers running NetWare.

Windows NT Workstation and Windows NT Server include client software to support connections to servers running NetWare. With the Client Service for NetWare in Windows NT Workstation and the Gateway Service for NetWare in Windows NT Server, users can access file and print resources on servers running NetWare 2.x through 4.x (through bindery emulation).

In addition to acting as client software for NetWare, the Gateway Service provides access to NetWare servers for Microsoft network client computers that are not running NetWare client software. Computers without NetWare client software can connect to NetWare resources as if they were shared on a Windows NT Server computer. Administrators can control which users can establish a gateway and the resources that are shared over the gateway.

Windows NT Server also provides administrators with a tool to help migrate the information on existing NetWare servers to Windows NT Server computers. The Migration Tool for NetWare in Windows NT Server transfers user and group accounts, and files and directories from NetWare 2.x and 3.x servers to Windows NT Server.


How to Use This Manual
Welcome	2 of 3

How to Use This Manual

This manual is organized in two parts. Part I explains how to install, configure, use, and troubleshoot Gateway Service for NetWare. Part II provides information on the Migration Tool for NetWare, including planning information and how to use the Migration Tool. The manual assumes that you are familiar with the Microsoft Windows NT Server operating system. If you are not familiar with Windows NT Server, see your Microsoft Windows NT documentation set for any information you need.

This manual contains the following chapters:

Part I  Gateway Service for NetWare in Windows NT Server

Chapter 1, "Setting Up the Gateway Service and NWLink"

Explains what the Gateway Service for NetWare does and how to install and configure the Gateway Service, install the NWLink IPX/SPX Compatible Transport Protocol without the Gateway Service, run the Gateway Service without the Windows NT Workstation service, and monitor its performance once it is running.

Chapter 2, "File and Print Gateways"

Explains how to configure a computer running Windows NT Server as a file or printer gateway so its client workstations can access NetWare file and print resources.

Chapter 3, "Connecting to a NetWare Print Queue"

Explains how to connect directly to print resources on the NetWare network.

Chapter 4, "Connecting to a NetWare Volume or Directory"

Explains how to connect to file resources on the NetWare network.

Chapter 5, "Running NetWare Utilities and NetWare-Aware Applications"

Lists supported NetWare utilities and NetWare-aware applications and outlines the requirements for running them on a Windows NT computer. Also describes NetWare utilities whose functions are handled by Windows NT utilities.

Chapter 6, "Troubleshooting the Gateway Service"

Explains how to diagnose problems in starting and running the Gateway Service, establishing connections to NetWare file and print resources, and setting up a file or print gateway.

Part II  Migration Tool for NetWare in Windows NT Server

Chapter 7, "NetWare to Windows NT Migration"

Introduces the Migration Tool and provides information on planning a migration, including the differences between NetWare and Windows NT networking.

Chapter 8, "Using the Migration Tool for NetWare"

Explains the basics of using the Migration Tool.

Chapter 9, "Transferring Users and Groups"

Explains how to transfer user and group accounts from NetWare to Windows NT.

Chapter 10, "Transferring Files and Directories"

Explains how to transfer files and directories from NetWare to Windows NT.

Chapter 11, "Completing the Migration"

Explains how to replace login scripts with user profiles and logon scripts, and the capabilities of printing on a Windows NT network.


Documentation Conventions
Welcome	3 of 3

Documentation Conventions

This manual uses several type styles and special characters, described in the following list:

Convention	Use

Bold	Represents commands, command options, and file entries. Type bold words exactly as they appear (for example, net use).

Italic	Introduces new terms and represents variables. For example, the variable computername indicates that you type the name of a workstation or a server.

ALL CAPITALS	Represents filenames and paths. (You can, however, type such entries in uppercase or lowercase letters, or a combination of the two.)

SMALL CAPITALS	Represents keyboard names (for example, CTRL, ENTER, and F2).

[brackets]	Encloses optional items in syntax statements. For example, [password] indicates that you can choose to type a password with the command. Type only the information within the brackets, not the brackets themselves.

Indicates a procedure.

...(ellipsis)	Indicates a command element may be repeated.


Setting Up the Gateway Service and NWLink
Chapter 1	1 of 8

Setting Up the Gateway Service and NWLink

If part of your computer resources are on a Novell NetWare network, your Windows NT network will need to communicate and share resources with the NetWare network. With the Gateway Service for NetWare, you can access NetWare file and print resources from your Windows NT Server computer. You can also enable a gateway to share NetWare file and print resources with Microsoft networking clients that have no NetWare client software.

This chapter explains what the Gateway Service for NetWare is. It also describes procedures for installing and configuring the Gateway Service, for configuring the NWLink IPX/SPX Compatible Protocol (NWLink), and for monitoring performance once the Gateway Service and NWLink are running. This chapter covers the following topics:

What is the Gateway Service?

Preparing to install the Gateway Service

Installing the Gateway Service

Configuring the NWLink IPX/SPX Compatible Transport Protocol

Specifying a preferred NetWare server

Managing IPX/SPX routing on a token ring network

Monitoring NetWare performance


What Is the Gateway Service?
Setting Up the Gateway Service and NWLink	2 of 8

What Is the Gateway Service?

To share resources between a Windows NT computer and the NetWare network, the two must use the same communication protocol. Windows NT includes an implementation of the internetworking packet exchange (IPX) and sequenced packet exchange (SPX) transport protocols used by the NetWare network. But a Windows NT computer must also be able to send NetWare core protocol (NCP) packets to request and receive file and print services. The Gateway Service for NetWare in Windows NT Server translates the server message block (SMB) packets used for Microsoft networking requests into the NCPs used by NetWare.

With the Gateway Service, your Windows NT Server computer can access files, directories, and printers on Novell NetWare servers. You can also run NetWare utilities and NetWare-aware applications from your Windows NT computer. In addition, you can configure a gateway so that Microsoft networking clients - computers running Microsoft networking software, including Windows NT, Windows for Workgroups, or LAN Manager 2.x - do not need NetWare client software to access files and printers on NetWare servers.

With NWLink NetBIOS, a Microsoft-enhanced implementation of Novell NetBIOS, you can send and receive Novell NetBIOS packets between a NetWare server running Novell NetBIOS and a Windows NT computer, or between two Windows NT computers. Performance is significantly better if all computers are Windows NT computers, because of efficiencies in communication between computers that can use the enhancements.

The Microsoft implementations of the IPX, SPX, and Novell NetBIOS protocols can seamlessly coexist with other protocols on the same network adapter card. For example, a single network card on a Windows NT computer can receive IPX/SPX, TCP/IP, Microsoft NetBEUI, and AppleTalk® packets.


Preparing to Install the Gateway Service
Setting Up the Gateway Service and NWLink	3 of 8

Preparing to Install the Gateway Service

Important

Before you install the Gateway Service, you must remove any existing NetWare redirectors, such as NetWare Services for Windows NT from Novell, and then restart your computer.

To remove existing NetWare redirector installations

1.	In Control Panel, choose the Network option.

2.	In the Network Settings dialog box, select the existing NetWare redirector software in the Installed Network Software box.

3.	Choose the Remove button.

4.	When Windows NT asks you to confirm your choice, choose the Yes button.

5.	In the Network Settings dialog box, choose the OK button.

6.	Restart your computer for the changes to take effect.

You are now ready to install the Gateway Service on your Windows NT Server computer.


Installing the Gateway Service
Setting Up the Gateway Service and NWLink	4 of 8

Installing the Gateway Service

You must be logged on as a member of the Administrators group for the local computer to install and configure the Gateway Service for your Windows NT computer.

When you install the Gateway Service on your Windows NT Server computer, the NWLink transport protocol is also installed if it is not already on your computer.

To install the Gateway Service

1.	From Control Panel, choose the Network option.

2.	When the Network Settings dialog box appears, choose the Add Software button.

3.	In the Add Network Software dialog box, select Gateway Service for NetWare, and then choose the Continue button.

4.	In the Windows NT Setup dialog box, enter the path where the Gateway Service files are located, and then choose the Continue button.

5.	In the Network Settings dialog box, choose the OK button.

6.	If the NWLink IPX/SPX Protocol Configuration dialog box appears, specify the network adapter card you want to use to communicate with the NetWare network. By default, NWLink automatically detects the frame type for the network adapter card you specify.

The default settings in this dialog box do not normally need to be changed. If you need to, you can always change the settings later, as described in "Configuring the NWLink IPX/SPX Compatible Transport Protocol," later in this chapter.

7.	To restart Windows NT so the changes take effect, choose the Yes button in the message that appears.

An icon labeled GSNW is added to Control Panel when the Gateway Service for NetWare is installed. The icon looks like the Network icon, except that one of the cable connectors is red.

By default, the NetWare network is added to the first place in the network search order. For more information on the network search order, see "Setting Network Provider Search Order" in Chapter 5, "Control Panel," of the Windows NT Server System Guide.


Configuring the NWLink IPX/SPX Compatible Transport Protocol
Setting Up the Gateway Service and NWLink	5 of 8

Configuring the NWLink IPX/SPX Compatible Transport Protocol

After the NWLink software is installed on your computer, you can specify the network adapter card it will use and the frame type of your network. The default settings are optimized for most environments, but you can modify protocol parameters after installation if, for example, you want to bind the protocol to a different network adapter card.

To configure the IPX protocol

1.	In Control Panel, choose the Network option.

2.	In the Installed Network Software box, select NWLink IPX/SPX Compatible Transport, and then choose the Configure button.

3.	In the Adapter box of the NWLink IPX/SPX Protocol Configuration dialog box, select the name of the adapter card to which you want to bind the transport.

4.	Select Auto Frame Type Detection (the default), or Manual Frame Type Detection if you want to manually specify the frame type or types for IPX/SPX packets on your network.

5.	If you choose Manual Frame Type Detection, the box on the left lists the frame types NWLink is using, and the box on the right lists the frame types that are available but not in use. To remove a frame type that is now in use, select it from the box on the left, and then choose the Remove button. To add a frame type, select it from the box on the right, and then choose the Add button.

6.	Choose OK to close the NWLink Configuration dialog box, and then choose OK to close the Network Settings dialog box.

7.	Windows NT prompts you to restart the computer so that the changes take effect. Choose the Yes button to restart the computer.

When you set the Frame Type to "Auto Detected," NWLink checks the frames being passed to the network adapter card the protocol is bound to. If it detects any frames of type 802.2 or no frames at all, it sets the frame type to 802.2. Otherwise, it sets the frame type to whatever is being passed on the network. For NetWare 4.01 networks, the frame type is usually 802.3. For token ring networks, it is 802.5.

If your computer is on a token ring network, you can use the ipxroute command line utility to further configure your computer. For more information, see "Managing IPX/SPX Routing on a Token Ring Network," later in this chapter.

Additional tunable parameters are stored in the Registry. In most situations, you should not have to modify the defaults in the Registry. NWLink parameters are described in Appendix A, "NWLink Registry Values."


Specifying a Preferred NetWare Server
Setting Up the Gateway Service and NWLink	6 of 8

Specifying a Preferred NetWare Server

The first time you log on after the Gateway Service is installed, you should specify the NetWare server you want your Windows NT computer to connect to by default when you log on. This NetWare server, which is referred to as the preferred server, validates your user credentials when you log on to the NetWare network and is queried for information you request about resources available on the NetWare network.

Although you do not have to specify a preferred server, it is a good idea, especially if you need to avoid logging on to NetWare servers that are limited to a small number of user connections.

To specify a preferred server when the Gateway Service is first installed

In the Select Preferred Server for NetWare dialog box, select the name of a server on the NetWare network or select <None> from the list provided, and then choose the OK button.

–Or–

Type a server name directly in the Server box, and then choose the OK button.

If you chose <None>, the Gateway Service attempts to connect to the nearest available server each time you log on.

You can change your preferred server any time you are logged on. For information on changing the preferred server once the Gateway Service is installed, see Chapter 4, "Connecting to a NetWare Volume or Directory."

Note

The preferred server setting affects only the account under which you are logged on when you make the setting. When other users log on, they are also prompted for a preferred server. If you later change your preferred server, other users are unaffected.


Managing IPX/SPX Routing on a Token Ring Network
Setting Up the Gateway Service and NWLink	7 of 8

Managing IPX/SPX Routing on a Token Ring Network

If your Windows NT computer is using the IPX/SPX protocol on a token ring network, each computer on the network has a source routing table that contains the address of each node on the network. When a computer receives an IPX/SPX broadcast packet or an IPX/SPX packet whose node address is not in its source routing table, by default the computer forwards the packet as a Single Route Broadcast frame.

You can modify or clear the source routing table, and you can change the default behavior of broadcast packets and packets with an unknown address, with the command line utility ipxroute. This utility provides the same functionality and has the same syntax as the route utility supplied by Novell for MS-DOS – based NetWare clients.

The parameters for ipxroute are equivalent to those for the route utility supplied by Novell. The ipxroute syntax is as follows:

ipxroute board=n [clear] [def] [gbr] [mbr] [remove=xxxxx]

board=n

Specifies the network adapter card whose parameters you want to change.

clear

Clears the source routing table.

def

Forwards packets as All Routes Broadcast frames if their media access control (MAC) address is not in the source routing table.

gbr

Forwards general broadcast packets, those addressed to the broadcast address (FFFFFFFFFFFF), as All Routes Broadcast frames.

mbr

Forwards multicast broadcast packets, those addressed to a multicast address (C000xxxxxxxx), as All Routes Broadcast frames.

remove=xxxxx

Removes the specified node address from the source routing table.

Note

The ipxroute utility changes these parameters only for the current Windows NT session. When you log off, the settings are lost. To permanently change NWLink parameters, you must set them in the Registry. For further information, see the online Help topic "Tuning Network Adapter Parameters."

The ipxroute utility is installed with the NWLink IPX/SPX Compatible Transport Protocol only if the protocol is bound to a token ring network card.


Monitoring NetWare Performance
Setting Up the Gateway Service and NWLink	8 of 8

Monitoring NetWare Performance

You can monitor the performance of the Gateway Service and the NWLink NetBIOS using Performance Monitor. For a detailed explanation of Performance Monitor, see "Performance Monitor" in the Windows NT Server System Guide.

To monitor the Gateway Service or NWLink NetBIOS with Performance Monitor

1.	In the Administrative Tools group, choose Performance Monitor.

2.	From the Edit menu, choose Add To Chart.

3.	In the Computer list in the Add To Chart dialog box, select the computer you want to monitor.

4.	In the Object list, select the process you want to monitor, Gateway Service for NetWare or NWLink NetBIOS.

5.	In the Counter list, select the counters you want to monitor for the selected process, and then choose the Add button.

For information about a counter, select the counter and then choose the Explain button.

6.	When you have added all the counters you want to a particular chart, choose the Done button.


File and Print Gateways
Chapter 2	1 of 6

File and Print Gateways

Microsoft networks and NetWare networks use different communication protocols for passing requests from clients to servers. Microsoft networking clients use server message block (SMB) protocol to perform remote requests to Microsoft networking servers, while NetWare clients use NetWare core protocol (NCP) to communicate with NetWare networking servers.

For clients of the Microsoft network that need access to NetWare resources but cannot use multiple protocols, you can configure a Windows NT Server computer as a file or print gateway. A gateway is also useful for Microsoft networking clients that are using Microsoft Remote Access Service, or on networks on which you want to limit IPX/SPX traffic or on which you are migrating to the Transport Control Protocol/Internet Protocol (TCP/IP). A gateway on a Windows NT Server computer can connect to NetWare resources and share them with clients of the Microsoft network.

This chapter covers the following topics:

How a gateway works

Enabling a gateway

Activating a file gateway

Setting permissions for a gateway share

Activating a print gateway


How a Gateway Works
File and Print Gateways	2 of 6

How a Gateway Works

The Gateway Service for NetWare on a Windows NT Server computer acts as a translator between the server message block (SMB) protocol used by the Windows NT network and the NetWare core protocol (NCP) used by the NetWare network. With a file gateway, for example, clients of a Windows NT Server computer can access files on NetWare servers without having to load additional NetWare connectivity components. The following figure shows an example of a file gateway configuration.

File Gateway Example

All file access over the gateway is done by sharing drives that are redirected to NetWare volumes or directories. The file gateway uses a NetWare account on the Windows NT Server computer to create a validated connection to the NetWare server. This connection appears on the Windows NT Server computer as a redirected drive. When you share the redirected drive, it becomes like any other shared resource on the Windows NT Server computer.

For example, you can connect the Windows NT Server computer to a NetWare directory called \\NW4\SYS\DATA, which becomes drive Z on the Windows NT Server computer. If the name of the Windows NT computer is THOR and the Z drive is given the share name DATA_USERS, a Microsoft networking client can access the NetWare directory by connecting to \\THOR\DATA_USERS. The Microsoft networking client is unaware that this shared resource is part of the NetWare network.

Once the gateway connection is established, it is not disconnected unless the computer is turned off or the Windows NT administrator disconnects the shared resource or disables the gateway. Logging off the Windows NT Server computer does not, by itself, disconnect the gateway.

Note

A gateway enabled on a Windows NT Server computer seamlessly integrates the Microsoft network with file and print resources on the NetWare network. Because requests from Microsoft networking clients are being processed through the Windows NT Server, access over the gateway is slower than direct access from the client to the NetWare network. For Microsoft networking clients that require frequent access to NetWare resources, Windows NT with the Client Service for NetWare or Windows for Workgroups with the client software supplied by Novell is a better solution. On a Windows for Workgroups computer, loading the necessary network protocols in high memory preserves valuable conventional memory for application software.


Activating a Gateway
File and Print Gateways	3 of 6

Activating a Gateway

Before you can enable a gateway on a Windows NT Server computer:

You must have a user account on the NetWare network with the necessary rights for the resources you want to access.

The NetWare server must have a group named NTGATEWAY with the necessary rights for the resources you want to access.

The NetWare user account must be a member of the NTGATEWAY group.

By controlling membership in the NTGATEWAY group, the NetWare administrator can control which Windows NT Server computers can be gateways to the NetWare server, and what kind of access to what files each user account has.

The NetWare administrator has total control over whether the gateway allows access to files and print queues on the NetWare server. With a gateway, the network administrator can control access to NetWare network resources either over the gateway or directly on the NetWare network:

On the Windows NT Server computer acting as a gateway, the administrator can restrict access by limiting which networking users or groups have access to gateway shares. Using multiple share restrictions through a gateway, the Windows NT administrator can control which networking users and groups can access files through the gateway.

On the NetWare file server, the NetWare administrator must create a special gateway group, NTGATEWAY. Using NTGATEWAY, the administrator can set trustee rights on the directories and files to which users and groups are allowed access through the gateway. There is no auditing of gateway access.

To make a NetWare server available to a gateway account

1.	Use the NetWare syscon utility to create the NTGATEWAY group account on the NetWare file server.

2.	Use syscon to create a NetWare user account with the name and password you will use to log on from the Windows NT Server computer.

3.	Add the gateway account to the NTGATEWAY group.

4.	Establish trustee rights for the NTGATEWAY group.

For detailed information on the syscon utility and NetWare user accounts and trustee rights, see your NetWare documentation.

To activate the file gateway on the Windows NT Server computer, you must specify the NetWare volume or directory. Volumes, directories, and print queues are represented in Windows NT by their uniform naming convention (UNC) names. However, NetWare syntax is also supported.

UNC names begin with two backslashes (\\) followed by the remote (in this case, NetWare) server name, and then the names of the volume or directory points on the server separated by single backslashes.

For example, if the file server named NW4 contains the THOR volume on which there is a directory WINAPPS\WORD, the UNC name for the directory is \\NW4\THOR\WINAPPS\WORD.

To enable a gateway

1.	In Control Panel on the Windows NT Server computer that is to be the gateway, choose the Gateway Service for NetWare (GSNW) option.

2.	In the Gateway Service for NetWare dialog box, choose the Gateway button.

3.	In the Configure Gateway dialog box, select the Enable Gateway check box.

4.	In the Gateway Account box, type the name of your gateway account on the NetWare file server. Type the password for the gateway account in both the Password and Confirm Password boxes.


Activating a File Gateway
File and Print Gateways	4 of 6

Activating a File Gateway

To activate a file gateway, you must have previously enabled a gateway on your Windows NT Server computer, as described in the previous section.

To activate a file gateway

1.	In Control Panel on the Windows NT Server computer that is to be the gateway, choose the Gateway Service for NetWare (GSNW) option.

2.	In the Gateway Service for NetWare dialog box, choose the Gateway button.

3.	In the Configure Gateway dialog box, choose the Add button to create a NetWare share for Microsoft networking clients.

4.	In the New Share dialog box, type the information about the redirected share, and then choose OK.

Windows NT Server creates a connection to the NetWare resource you specify in the Network Path box, assigns it the redirected disk drive you specify in the Use drive box, and creates a share on the Microsoft network using the share name you specify in the Share Name box.

If the connection fails with an "Access Denied" message from the NetWare server, be sure that you entered your account name and password correctly in the Configure Gateway dialog box. If you did, you may not have a valid account on the NetWare server, or your account may not be a member of the NTGATEWAY group. It is also possible that your account or the NTGATEWAY group has insufficient trustee rights to access the specified NetWare volume or directory.

Note

You cannot use the net use command to create a gateway, because redirections made using either this command or File Manager are properties of the user who was logged on at the time of creation. If the user logs off, the connection is terminated. The gateway connection is disconnected only if the computer is turned off or if an administrator disables the gateway.


Setting Permissions for a Gateway Share
File and Print Gateways	5 of 6

Setting Permissions for a Gateway Share

If you want to control user access, you can set permissions for the share when you create it, or later if your needs change. You can set permissions on a NetWare resource shared through a gateway using either File Manager or the Gateway Service. For information on setting permissions with File Manager, see "File Manager" in the Windows NT Server System Guide.

To set permissions for a gateway share using the Gateway Service

1.	In Control Panel, choose the Gateway Service for NetWare (GSNW) option.

2.	In the Gateway Service for NetWare dialog box, choose the Gateway button.

3.	From the list of gateway shares provided in the Configure Gateway dialog box, select the share whose permissions you want to set, and then choose the Permissions button.

If the Permissions button is dimmed, the gateway may be disabled. If the Enable Gateway check box is cleared, enable the gateway as described earlier in this chapter.

In the Access Through Share Permissions dialog box, you can add groups and users, change the permissions for the listed groups and users, and remove a group or user from the permissions list.

4.	To add a user to the list of authorized share users, choose the Add button in the Access Through Share Permissions dialog box.

The Add Users And Groups dialog box displays the groups on the computer or in the domain shown in the List Names From box. You can display users, find the users in a group, or find the domain to which a group or user belongs.

Local groups are shown for the computer or domain whose name is followed by an asterisk (*). You can select another domain from the List Names From box. Domains are listed only if your computer is a member of a domain on a Windows NT network. The domains shown have a trust relationship with your computer's domain.

5.	To display the names of users on the selected computer or domain, choose the Show Users button.

6.	To view the members of a group, select the group and choose the Members button.

The Local Group Membership dialog box appears, listing the group's members. For Windows NT Server domains, global groups that are members of a local group appear in the list.

To see a global group's users, select the group name from the list and choose the Members button in the Local Group Membership dialog box. To add the group to the list in the Add Users And Groups dialog box, choose the Add button in the Local Group Membership dialog box.

7.	To add a group or user, you must know the domain to which the group's or user's account belongs. For Windows NT Server domains, choose the Search button to find the domain of a group or user. When the Find Account dialog box appears, type the name of the group or user in the Find User Or Group box, and specify the domains you want to search. Then choose the Search button. To include the groups or users in the Add Users And Groups dialog box, select them in the Search Results box and choose the Add button.

8.	To add groups or users to the list, select them in the Names box and choose the Add button, or double-click the name of the group or user. Or you can type the names of groups and users in the Add Names box. Separate names with a semicolon.

If the account of the group or user is not located on the computer or domain shown by the List Names From box, you must specify the location. Type the computer or domain name followed by the group or user name, and separate the names with a backslash, for example, sales\anniep. You can type the name without waiting for Windows NT to list groups in the Names box.

9.	If you are adding users or groups to a permissions list, select from the Type Of Access box the permission for the groups or users shown in the Add Names box.

10.	Choose the OK button.

11.	In the Configure Gateway dialog box, choose the OK button.

12.	In the Gateway Service for NetWare dialog box, choose the OK button.

For information about setting permissions with File Manager, see "Setting Permissions Through Shared Directories" in Chapter 4 of the Windows NT Server System Guide.


Activating a Print Gateway
File and Print Gateways	6 of 6

Activating a Print Gateway

A print gateway functions much like the file gateway described earlier in this chapter: once you have enabled the Gateway Service on a Windows NT Server computer, the NetWare printer appears on the Windows NT network like any other shared printer. Print jobs sent to the print gateway are redirected to the corresponding NetWare print queue. You configure a NetWare print gateway through Print Manager.

To configure a print gateway, a gateway must be enabled. All access to NetWare printers is in the context of the user account used to enable the gateway. For more information, see "Activating a Gateway," earlier in this chapter.

To configure a NetWare print gateway

1.	From the Windows NT Server computer that is to serve as a gateway, connect to a NetWare print queue using Print Manager, as described in Chapter 3, "Connecting to a NetWare Print Queue."

2.	In Print Manager, select the printer icon or window for the print queue.

3.	From the Printer menu, choose Properties, or choose the Properties button on the toolbar.

4.	In the Printer Properties dialog box, select the Share This Printer On The Network check box.

Print Manager creates a share name in the Share Name box for the printer, using MS-DOS naming conventions. This allows MS-DOS – based computers to connect to the printer. If you edit the share name and the Windows NT network has clients that are running MS-DOS, be sure to follow MS-DOS naming conventions.

5.	In the Location box, type a description of the printer's location to let network users know where their documents will be printed.

6.	Choose the OK button.

Once the queue is shared, networking clients can access the print queue.

Microsoft networking clients can connect to the shared NetWare print queue as they would to any Windows NT printer. For example, if the print queue is shared on a Windows NT Server computer named WIN_NT under the share name HP4SI, users can specify \\win_nt\hp4si in the Connect To Printer dialog box. Users can also browse for the printer. The printer is listed by its uniform naming convention (UNC) name in the Shared Printers box. For information on the uniform naming convention, see "Activating a Gateway," earlier in this chapter.


Connecting to a NetWare Print Queue
Chapter 3	1 of 4

Connecting to a NetWare Print Queue

With the Gateway Service for NetWare, you can establish a connection to a NetWare print queue through Print Manager or from the command prompt.

This chapter covers the following topics:

Connecting to a NetWare printer through Print Manager

Connecting to a NetWare printer at the command prompt

Setting printing options


Connecting to a NetWare Printer Through Print Manager
Connecting to a NetWare Print Queue	2 of 4

Connecting to a NetWare Printer Through Print Manager

You can connect to NetWare print queues using Print Manager in the same way you connect to shared printers on the Microsoft network. The list of NetWare servers and print queues is displayed automatically in the Shared Printers box. Double-click a server name to display or hide its print queues.

To connect to a NetWare print queue using Print Manager

1.	From the Printer menu, choose Connect To Printer, or choose the Connect Printer button on the toolbar.

2.	In the Connect To Printer dialog box, select a printer from the Shared Printers box, or type the name of a computer and print queue in the Printer box.

The Shared Printers box shows servers and print queues. Double-click a server name to display or hide its print queues. When you select a print queue in the Shared Printers box, Print Manager fills in the Printer box.

When you type the name of a print queue directly in the Shared Printers box, precede the computer name with two backslashes (\\), and separate the computer name from the print queue's name with a single backslash (\). For example, to specify a printer named HP4SI on a server named NW4, you would type \\nw4\hp4si.

3.	Choose the OK button.

4.	If a printer driver is not available locally for a NetWare print queue, Print Manager prompts you to install a printer driver. Choose the OK button to continue.

5.	In the Select Driver dialog box, select the appropriate driver for the printer in the Driver box.

6.	In the Windows NT Setup dialog box, type the directory and path where Windows NT printer drivers are stored, and then choose the Continue button.

Windows NT installs the driver and displays a printer window for the connected print queue.

Be sure to set the correct printer options once the appropriate driver has been loaded. You can now print to the NetWare print queue just as you would to a Windows NT printer.


Connecting to a NetWare Printer at the Command Prompt
Connecting to a NetWare Print Queue	3 of 4

Connecting to a NetWare Printer at the Command Prompt

If you are running an application that writes directly to a predefined port, you can use the net use command as you would use the NetWare capture utility to associate the NetWare print queue with the port. For example, to redirect output from LPT1 to the NetWare print queue called MEMOS on the server named NW4, type:

net use lpt1 \\nw4\memos

This statement is equivalent to the NetWare capture command, where the syntax would be capture Q=memos S=nw4 L=1.

After you have redirected output using the net use command, you can use the copy command to send files that don't require formatting to the printer. For example:

copy myfile.txt lpt1

You can also copy the file directly to the print queue. For example:

copy myfile.txt \\nw4\memos


Setting Printing Options
Connecting to a NetWare Print Queue	4 of 4

Setting Printing Options

Printing options are already set for the user logged on to Windows NT, and these same options can be set for NetWare print queues. The printing defaults are to suppress form feed, to print a banner (blank page) between documents, and to notify you when your document is finished printing. You can change these options by changing the configuration of the Gateway Service.

Note

Settings in the Gateway Service affect all NetWare print queues you are using from your Windows NT Server computer. The options are equivalent to settings available through the NetWare capture utility.

To set printing options

1.	In Control Panel, choose the Gateway Service for NetWare (GSNW) option.

2.	In the Print Options box of the Gateway Service for NetWare dialog box:

To instruct the printer not to eject a page after printing a document, clear the Add Form Feed check box.

To stop notification when your document has been printed, clear the Notify When Printed check box

To stop printing a banner page before your document prints, clear the Print Banner check box.

3.	Choose the OK button when the printing options are as you want them.


Connecting to a NetWare Volume or Directory
Chapter 4	1 of 9

Connecting to a NetWare Volume or Directory

When the Gateway Service for NetWare is installed on your Windows NT computer, you can connect to volumes and directories on NetWare file servers using File Manager or the net command at the command prompt. You can print to NetWare print queues by connecting to the print queue in Print Manager or by using the copy command at the command prompt.

This chapter covers the following topics:

Validating a NetWare account

Selecting a preferred server

Connecting to a NetWare file resource through File Manager

Connecting to a NetWare file resource at the command prompt

Managing network connections

Managing NetWare file attributes


Validating a NetWare Account
Connecting to a NetWare Volume or Directory	2 of 9

Validating a NetWare Account

You must have an account on the NetWare server before you can use its files, applications, or print queues. The NetWare server account contains your credentials, which are your username and password.

By default, Windows NT supplies the username and password you use when you log on to Windows NT as the credentials it sends to the NetWare server. Because you are prompted to supply your username and password on the NetWare server only if they are different from those on the Windows NT computer, you may want to keep your username and password the same on both the Windows NT and NetWare networks. Maintaining the same username and password also makes it easier for network administrators to coordinate user accounts.

To change your password on a NetWare server

1.	At the command prompt, use the net use command to connect to the NetWare server's SYS volume.

–Or–

From the Disk menu in File Manager, choose the Connect Network Drive command, and connect to the NetWare server's SYS volume.

2.	At the command prompt, change to the drive for the NetWare server, and then make the PUBLIC directory the current directory. For example, type n:, and then type cd \public.

3.	At the command prompt, type the setpass command. If the server on which you want to change your password is different from the one on the current drive, type setpass and the server name.

For example, to change your password on the server named NWSERVER, type:

setpass nwserver

4.	When you are prompted, type your old password, then the new password, and then retype the new password to confirm it.

5.	If you are connected to other NetWare servers that also use your old password, they are listed, and you are asked if you want to change your password on these servers as well.

Type y and press ENTER to change the additional passwords.

–Or–

Type n and press ENTER to leave the passwords as they are.

If you want to change your password on more than one server, connect to all affected servers before running the setpass command.

The setpass command is a NetWare utility supported by Windows NT. For a complete list of supported NetWare utilities, see "Supported NetWare Utilities" in Chapter 5, "Running NetWare Utilities and NetWare-Aware Applications."


Selecting a Preferred Server
Connecting to a NetWare Volume or Directory	3 of 9

Selecting a Preferred Server

When the Gateway Service is installed, you can specify a preferred NetWare server, the one to which the Gateway Service connects your Windows NT computer by default when you log on, or you can specify no preferred server. If your needs or the network's configuration change later, you can change your preferred NetWare server at any time.

To specify a preferred NetWare server

1.	From Control Panel, choose the Gateway Service for NetWare (GSNW) option.

2.	When the Gateway Service For NetWare dialog box appears, in the Select Preferred Server box select a server from the list provided, or type the name of a NetWare server directly into the box, and then choose the OK button.

3.	If your password on the NetWare server is different from that on the Windows NT computer, enter your NetWare password at the prompt, and then choose the OK button.

The next time you log on, the Gateway Service connects to the NetWare server you specify as the preferred one.

Note

The preferred server setting affects only the account under which you are logged on when you make the setting. When other users log on, they are also prompted for a preferred server. If you later change your preferred server, other users are unaffected.


Connecting to a NetWare File Resource Through File Manager
Connecting to a NetWare Volume or Directory	4 of 9

Connecting to a NetWare File Resource Through File Manager

With File Manager, you can browse and connect to resources on both the Microsoft and NetWare networks. Once you are connected to a NetWare volume, you can drag and drop directories and files to move and copy them between your Windows NT computer and NetWare servers.

The list of servers on the NetWare network is displayed automatically in the Shared Directories box. The servers, volumes, and directories are displayed in a tree structure. Both volumes and directories are represented by the shared directory icon. Choose an item to expand the list; for example, choose a directory to display its subdirectories.

The NetWare server validates your credentials before it displays directories in a NetWare volume you select. If the NetWare server cannot validate your credentials, Windows NT displays the Enter Network Credentials dialog box.

On the NetWare network, you can type the server name in the Path box and choose the OK button if you know the name of a server and need to see the names of its volumes. Preface the server name with two backslashes (\\). Windows NT adds the name of the server's first volume directory to the Path box and displays all the server's volumes in the Shared Directories box.

You can type a network path in the Path box. On the NetWare network, you can type the name using either uniform naming convention (UNC) or NetWare syntax. For information about UNC syntax, see "Activating a Gateway" in Chapter 2, "File and Print Gateways."

To connect to a NetWare drive using File Manager

1.	From the Disk menu, choose Connect Network Drive, or choose the Connect Drive button on the toolbar.

2.	File Manager displays the first free drive letter in the Drive box. You can accept the displayed drive letter for the connection or choose another in the Drive box.

3.	In the Path box, select or type a network path.

If you have connected to the volume or directory before, select the path from the list displayed by the Path box. The Path box displays the previous ten paths.

Or, you can use the Shared Directories box to select a network path.

4.	You are connected by default under the username and password you used to log on. If you want to connect under a different username, type it in the Connect As box.

5.	Choose the OK button. If a password is required, Windows NT displays the Enter Network Password dialog box where you can type the password.


Connecting to a NetWare File Resource at the Command Prompt
Connecting to a NetWare Volume or Directory	5 of 9

Connecting to a NetWare File Resource at the Command Prompt

You can use the net view command to display file servers and volumes on the NetWare network. With the network parameter, you can specify the particular network you want to view.

To display a list of NetWare file servers

At the command prompt, type:

net view /network:nw

To display volumes on a specific NetWare file server

At the command prompt, type:

net view \\nwserver_name /network:nw

where nwserver_name is the name of the NetWare file server. Be sure to precede the server name with two backslashes (\\).

If the net view command is used without the /network:nw switch, the servers and shares on the Microsoft network are displayed by default.

You can use the net use command from the command prompt to connect to NetWare file servers and print queues. To connect, you can use the same command syntax you use to connect to shares on a Microsoft network.

The net command for connecting to NetWare file servers is equivalent to the map NetWare command on MS-DOS – based NetWare workstations.

To connect to a NetWare volume

At the command prompt, type the net use command, specifying the shared directory with either its UNC or NetWare name:

net use drive: \\computer\directory | \\computer:volume\directory

For example, to connect to the directory \DATA\MYDATA on the THOR volume on a server named NW4 using the G drive, type:

net use g: \\nw4\thor\data\mydata

Tip

To use the next available drive letter when connecting to the volume, replace the drive letter with an asterisk (*).

The error message "The password is invalid for \\server_name\volume_ name[\directory_name...]" means that the username and password you supplied when you logged on to Windows NT were not validated by your preferred server. To connect under a valid username and password, use the following net use command with the switch and syntax shown:

net use drive: \\computername\sharename /user:username password

–Or–

net use drive: \\computer:volume\directory /user:username password

For example, to connect as anniep with the password marshmallow to the directory \DATA\MYDATA within the THOR volume on a server called NW4 using the G drive, type:

net use g: \\nw4\thor\data\mydata /user:anniep marshmallow

If you prefer to be prompted for a password, replace the password with an asterisk (*). When you type your password at the prompt, it is not displayed on the screen.


Managing Network Connections
Connecting to a NetWare Volume or Directory	6 of 9

Managing Network Connections

When the Gateway Service is running, you can manage connections to the NetWare network just as you manage connections on the Microsoft network. You can view and manage active connections and define persistent connections with the net use command.


Viewing Current Network Connections
Connecting to a NetWare Volume or Directory	7 of 9

Managing Network Connections

Viewing Current Network Connections

When you type the net use command without any parameters, you can list the current network connections.

Status	Local	Remote		Network
-	E:	\\NW4\SYS		NetWare
OK	F:	\\WIN_NT\DROOT		Microsoft Windows
-	H:	\\NETWARE40\THOR\APPS		NetWare


Reestablishing Network Connections
Connecting to a NetWare Volume or Directory	8 of 9

Managing Network Connections

Reestablishing Network Connections

You must indicate when you create connections that they are to be reestablished if you want a user's profile to establish network connections.

To make connections persistent, check the Restore At Logon box when making connections from File Manager. Or if you are creating the connection from the command line, be sure to use the /persistent switch with the net use command. For example, type net use /persistent:yes.

Administrator-defined logon scripts can also be used in addition to the net use command with the /persistent switch. For more information about logon scripts, see "User Manager" in the Windows NT Server System Guide.


Managing NetWare File Attributes
Connecting to a NetWare Volume or Directory	9 of 9

Managing NetWare File Attributes

NetWare file attributes are not exactly the same as those on Windows NT. The following file rights mappings are applied when a NetWare file is opened by Gateway Services.

Windows NT file attributes		NetWare file attributes
R (Read Only)		Ro, Di (Delete Inhibit), Ri (Rename Inhibit)
A (Archive)		A
S (System)		Sy
H (Hidden)		H
Gateway Services does not support mapping to the following NetWare file attributes: RW (Read Write), S (Shareable), T (Transactional), P (Purge), Ra (Read Audit), Wa (Write Audit), and Ci (Copy Inhibit).

When you copy a file from an Microsoft networking client to the NetWare file server via Gateway Services, the Ro, A, Sy, and H file attributes are preserved.

You can use the NetWare utilities, such as filer and rights, from a Windows NT Server computer with an activated gateway to set attributes that are not supported by the Windows NT-to-NetWare file rights mapping. For more information about other supported utilities, see Chapter 5, "Running NetWare Utilities and NetWare-Aware Applications."


Running NetWare Utilities and NetWare-Aware Applications
Chapter 5	1 of 7

Running NetWare Utilities and NetWare-Aware Applications

Windows NT has a collection of 32-bit graphical network and user management tools, including User Manager, Server Manager, and User Profile Editor. You can share Windows NT resources using File Manager, Print Manager, or the command line. NetWare, by contrast, includes a set of 16-bit command-line utilities for managing and sharing resources.

With Windows NT Server and the Gateway Service for NetWare, you can run many of the NetWare utilities from the command prompt. Other functions of the NetWare utilities are provided through the Windows NT management tools. In addition, Windows NT supports many NetWare-aware applications.

This chapter lists the supported NetWare utilities and explains the Windows NT utilities that you can use to manage the NetWare network. It also lists supported NetWare-aware applications and describes the files you must have in order to run them.


Supported NetWare Utilities
	Running NetWare Utilities and NetWare-Aware Applications	2 of 7
Supported NetWare Utilities

Windows NT supports many of the NetWare utilities, so you can manage the NetWare network from a Windows NT computer. Some NetWare utilities are not supported, but you can perform their functions with Windows NT utilities. Some additional files supplied either with Windows NT or with NetWare may be required by some utilities. For detailed information, see "Requirements for Running NetWare-Aware Applications," later in this chapter.

Windows NT supports the following MS-DOS–based NetWare utilities:

chkvol	help	rconsole	settts
colorpal	listdir	remove	slist
dspace	map	revoke	syscon
flag	ncopy	rights	tlist
flagdir	ndir	security	userlist
fconsole	pconsole	send	volinfo
filer	psc	session	whoami
grant	pstat	setpass
Note

If you run a utility (such as rconsole on 3.1x NetWare servers) outside of the SYS:PUBLIC directory, the utility may ask for the SYS$MSG.DAT file. The SYS$MSG.DAT file is located in the SYS:PUBLIC directory. You can avoid this message by adding SYS:PUBLIC to your path.


NetWare Utility Behavior Supplied by Windows NT Commands
	Running NetWare Utilities and NetWare-Aware Applications	3 of 7
Supported NetWare Utilities

NetWare Utility Behavior Supplied by Windows NT Commands

The Windows NT net use command or File Manager can be used to perform the same functions as the NetWare attach, login, and logout utilities. The Windows NT net view command can be used to perform the same function as the NetWare slist utility. For more information about the net use and net view commands and File Manager, see "Connecting to a NetWare File Resource at the Command Prompt" in Chapter 4, "Connecting to a NetWare Volume or Directory."

The net use command also supplies similar functionality to the capture command for printing when MS-DOS–based and Windows-based applications require printing to a specific port. In addition, Print Manager can be used to connect to NetWare print queues. For more information about printing, see "Connecting to a NetWare Printer Through Print Manager" in Chapter 3, "Connecting to a NetWare Print Queue."


NetWare-Aware Applications
	Running NetWare Utilities and NetWare-Aware Applications	4 of 7
NetWare-Aware Applications

NetWare-aware applications behave on Windows NT as if they were on a NetWare resource. Not all NetWare-aware applications are supported by Windows NT, and of those that are supported, many require special files supplied either with NetWare or with Windows NT.


Supported NetWare-Aware Applications
	Running NetWare Utilities and NetWare-Aware Applications	5 of 7
NetWare-Aware Applications

Supported NetWare-Aware Applications

The NetWare-aware applications shown in the following table are supported. The applications were tested on Intel®, MIPS®, and Digital Alpha AXP™ platforms. Following the table are descriptions of the services and files required for these applications to be supported.

MS-DOS – Based NetWare-Aware Applications

Application		Version	Prerequisites
Attachmate Extra! for MS-DOS to the NetWare SAA™ Gateway		3.1	Batch files
Attachmate Extra! for MS-DOS to the Attachmate 3270 Gateway		3.1	Batch files
Attachmate Extra! for Windows to the NetWare SAA Gateway		3.5	TSR
Attachmate Extra! for Windows to the Attachmate 3270 Gateway		3.5	TSR
DCA™ IRMA™ LAN for MS-DOS to Novell's SAA		2.1.0	None
Btrieve® requester (BREQUEST.EXE)		6.10a	TSR
Gupta SQLBase® for NetWare systems		5.1.3	Btrieve support NWIPXSPX.DLL, NETWARE.DRV, and NWNETAPI.DLL Must be connected to a NetWare server prior to loading Runs only on an Intel platform
Lotus Notes®, SPX connectivity option		3.0	Must be connected to a NetWare server prior to loading TBMI2 on MIPS and Alpha AXP NWIPXSPX.DLL, NETWARE.DRV, and NWNETAPI.DLL
NetWare 3270 LAN Workstation for Windows		1.2	Runs only on an Intel platform


Requirements for Running NetWare-Aware Applications
	Running NetWare Utilities and NetWare-Aware Applications	6 of 7
NetWare-Aware Applications

Requirements for Running NetWare-Aware Applications

The following files and services may be required in order for MS-DOS – based NetWare utilities and NetWare-aware applications to be supported.

NWIPXSPX.DLL

Many applications that are written for 16-bit Windows and are NetWare-aware require NWIPXSPX.DLL from Novell. If you have previously used the application under Microsoft Windows 3.x and are using the same computer for Windows NT, NWIPXSPX.DLL exists on your system. If you start the application and the application cannot find this file, check your path by typing path at the command prompt. Verify that a copy of the NWIPXSPX.DLL can be found. If not, obtain a copy of NWIPXSPX.DLL from Novell, and copy it to the \systemroot\SYSTEM32 directory.

If you are running these applications on either the MIPS or Digital Alpha AXP platforms, you will need to obtain NWIPXSPX.DLL from Novell. Copy NWIPXSPX.DLL to the \systemroot\SYSTEM32 directory.

If you need to copy NWIPXSPX.DLL to your Windows NT Server computer or modify your path statement, you must log off and then log back on to Windows NT for the changes to take effect.

Special Requirements for MIPS and Alpha AXP Platforms

If the NetWare-aware application requires NWIPXSPX.DLL, you must have a copy of TBMI2.COM in \systemroot\SYSTEM32 to run the application on the MIPS and Digital Alpha AXP platforms.

In AUTOEXEC.NT, insert the following line immediately after the line that refers to vwipxspx:

lh winnt\system32\tbmi2.com

Save the change to AUTOEXEC.NT, and then log off and log back on to your Windows NT Server computer.

NETWARE.DRV, NWNETAPI.DLL, and NWCALLS.DLL

NetWare-aware applications that use the NetWare application programming interface (API) to send and receive NetWare core protocol (NCP) packets might require NETWARE.DRV and either NWNETAPI.DLL or, for more recent versions of NetWare, NWCALLS.DLL.

NETWARE.DRV is installed in the \systemroot\SYSTEM32 directory when you install the Gateway Service. If you have previously used a NetWare-aware application on the same computer using an MS-DOS–based version of Windows, NWNETAPI.DLL or NWCALLS.DLL is probably already installed on your computer. If your application cannot find NWNETAPI.DLL or NWCALLS.DLL, make sure the appropriate file is installed on your computer and is in your computer's search path. If you are running the application on the Digital Alpha AXP or MIPS platform or you can't locate one of these .DLL files on your computer, contact Novell to obtain a copy of the appropriate file, and then install it in your \systemroot\SYSTEM32 directory. If you cannot load your NetWare-aware application with the version of NETWARE.DRV installed with the Gateway Service, replace NETWARE.DRV with the corresponding file supplied by Novell, dated 10/27/92 with a file size of 126,144 bytes.

If you copied any of these files to your Windows NT Server computer or modified your path statement during the current Windows NT work session, you must log off and then log back on for the changes to take effect.


Special Considerations for Individual NetWare-Aware Applications
	Running NetWare Utilities and NetWare-Aware Applications	7 of 7
NetWare-Aware Applications

Special Considerations for Individual NetWare-Aware Applications

If you do not have a preferred server and you have not connected to any NetWare server, you must first create a connection to a NetWare server. For more information about connecting to NetWare servers, see Chapter 4, "Connecting to a NetWare Volume or Directory."

Btrieve

If you are running MS-DOS – based or 16-bit Windows-based applications that require the Btrieve requester, BREQUEST.EXE, you must modify the AUTOEXEC.NT file located in \systemroot\SYSTEM32 so the applications can find the Btrieve requester. Find the location of BREQUEST.EXE on your computer and append location information in the AUTOEXEC.NT file.

For example, if BREQUEST.EXE is located in the C:\BTRIEVE directory, add this line to AUTOEXEC.NT:

lh c:\btrieve\brequest.exe

Then log off and log back on to Windows NT for the change to take effect.

Attachmate Extra! Extended for MS-DOS

If Extra! batch files are run from a console window, make the first line of the batch files command /c so that the Extra! hot keys work after Extra! has initialized.

Attachmate Extra! for Windows IPX/SPX Connectivity

Attachmate Extra! for Windows requires IPXINTFC, a terminate-and-stay-resident (TSR) utility. This TSR must be loaded by AUTOEXEC.NT prior to the DOSX TSR being loaded.

For example, suppose Attachmate Extra! for Windows has been installed in the C:\EXTRAWIN subdirectory. In AUTOEXEC.NT, make sure the following three lines are in the order shown:

lh c:\extrawin\ipxintfc
REM Install DPMI support
lh winnt\system32\dosx

Log off and log back on to Windows NT for the changes to take effect.


Troubleshooting the Gateway Service
Chapter 6	1 of 18

Troubleshooting the Gateway Service

This chapter describes ways of troubleshooting various problems that can arise while installing, starting, and running the Gateway Service for NetWare. The chapter discusses problems in these areas:

Startup problems

Access problems

Application and print problems

Other network problems


Startup Problems
Troubleshooting the Gateway Service	2 of 18

Startup Problems

Many common startup problems are caused by improper installation of the network adapter card or of the Gateway Service itself. The first things to check are that the network card is installed and configured correctly and that any existing installations of NetWare redirectors, such as Novell's NetWare Services for Windows NT, have been removed.

To correct the configuration of your network card or to remove a NetWare redirector, use the Network option in Control Panel. For more information, see Chapter 1, "Setting Up the Gateway Service and NWLink."

This section discusses some common problems that might occur while installing or starting the Gateway Service.


Gateway Service Doesn’t Start
Troubleshooting the Gateway Service	3 of 18

Startup Problems

Gateway Service Doesn't Start

If the Gateway Service does not start, one of the services or protocols it depends on may not be available. You can first try to start it manually. If that fails, you can troubleshoot the problem using the system event log.

To verify that the Gateway Service has started

1.	In Control Panel, choose the Services option.

2.	If the status of Gateway Service for NetWare is not Started, select it and choose the Start button. If the service is already started, check the System Log in Event Viewer.

To check the System Log

1.	In the Administrative Tools group of Program Manager, choose Event Viewer.

2.	In the Source column of the Event Viewer System Log dialog box, look for events from Service Control Manager or NWLinksys.

3.	Double-click the appropriate log entry for more details about the event.

4.	In the Event Details dialog box, look for one of the messages described in the table following this procedure.

5.	In the Event Details dialog box, choose the Close button.

6.	From the Log menu, choose Exit.

Messages Found in the Event Details Dialog Box

Source	Message		Recommended action
Service Control Manager	Gateway Service for NetWare terminated with the following error: The system cannot find the specified file.		The Gateway Service was not installed properly. Use the Network option in Control Panel to remove and reinstall the Gateway Service. For information on installing the Gateway Service, see Chapter 1.
Service Control Manager	The NWLink service depends on the NWLinksys services which failed to start because of the following error: The system cannot find the file specified.		The NWLink IPX/SPX Compatible Transport Protocol was not installed properly. Use the Network option in Control Panel to reinstall NWLink. For more information about installing transports, see Chapter 3 of the Windows NT Server Installation Guide.
NWLinksys	Error binding to adapter card cardname.		Your adapter card may be malfunctioning, or its settings may be incorrect. If your adapter card is not malfunctioning and the NWLink protocol is bound to the correct card, use the Network option in Control Panel to verify the adapter card settings. For information on configuring the NWLink protocol, see Chapter 2.


Gateway Service Starts, But Servers Can’t Be Found
Troubleshooting the Gateway Service	4 of 18

Startup Problems

Gateway Service Starts, But Servers Can't Be Found

You may not be able to see NetWare servers because the network frame type is set incorrectly. View the network adapter load line in the NetWare server's AUTOEXEC.NCF file to verify that you are using the correct frame type for the server. For example, suppose a server's network adapter load line is:

load 3C503 FRAME=ETHERNET_802.3 NAME=ETH

In this case, the server is bound to a 3Com® 503 ethernet adapter that will accept the raw 802.3 frame format.

You can use the Network option in Control Panel to see the frame type you have set for your adapter card. If the frame type is "Auto Detected" and NWLink detects any frames of type 802.2 or no frames at all, it sets the frame type to 802.2. If the network adapter card receives frames of type 802.2 but your NetWare network uses some other frame type, you will have to set it manually. For detailed information on configuring NWLink, see Chapter 1, "Setting Up the Gateway Service and NWLink."


Gateway Service Starts, But NetWare 4.x Servers Can’t Be Seen
Troubleshooting the Gateway Service	5 of 18

Startup Problems

Gateway Service Starts, But NetWare 4.x Servers Can't Be Seen

The Gateway Service supports NetWare 4.x bindery emulation. Be sure that the bindery context you set for your NetWare server directory includes the Windows NT users you want to have access to the servers. You can view and set your bindery context on NetWare 4.x servers either by loading the SERVMAN NetWare Loadable Module (NLM) and then viewing and setting the SET BINDERY CONTEXT parameter. Or you can type set at the command prompt to view the Miscellaneous SET parameters. For more information, see your NetWare 4.x server documentation.


Gateway Service Prompts for a Password at Each Logon
Troubleshooting the Gateway Service	6 of 18

Startup Problems

Gateway Service Prompts for a Password at Each Logon

The Gateway Service prompts you for a password for your preferred server after you log on to Windows NT because the user name and password for your NetWare preferred server differs from your Windows NT password. If you don't want to be prompted for your preferred server password, make your NetWare preferred server and Windows NT passwords the same. You can change your password using the procedure described in "Validating a NetWare Account" in Chapter 4, "Connecting to a NetWare Volume or Directory."


NetWare Login Scripts Are Not Running
Troubleshooting the Gateway Service	7 of 18

Startup Problems

NetWare Login Scripts Are Not Running

The Gateway Service does not support the NetWare scripting language. However, Windows NT does have its own logon scripts. For information on Windows NT logon scripts, see Chapter 13, "User Manager," in the Windows NT Server System Guide.


Access Denied to a NetWare File Server
Troubleshooting the Gateway Service	8 of 18

Access Denied to a NetWare File Server

By default, the Gateway Service uses the credentials used for preferred server authentication to access other NetWare servers. In order to see files on NetWare servers for which you have access, synchronize your credentials on all the NetWare servers. You can synchronize your credentials using the procedure described in "Validating a NetWare Account" in Chapter 4, "Connecting to a NetWare Volume or Directory."

If you do not want to use the same credentials for each NetWare server, type your username for the NetWare server in the Connect As box in the Connect Network Drive dialog box in File Manager. You will be prompted for your password for the server.

If you are using the command prompt and do not want to synchronize your NetWare credentials on all servers, at the command prompt type:

net use drive: \\nwserver_name\volume_name /user:username password

If access is denied when you are trying to configure a Windows NT Server computer as a file or print gateway, the NetWare user account you have used to enable the gateway may not be a member of the NTGATEWAY group, or your account or the NTGATEWAY group may not have sufficient trustee rights. For information on setting up the NTGATEWAY group and assigning trustee rights on the NetWare server, see your NetWare documentation.


Application and Print Problems
Troubleshooting the Gateway Service	9 of 18

Application and Print Problems

This section describes applications and print problems that could affect your ability to run the Gateway service.


NetWare Print Queues Are Not Shown in Print Manager
Troubleshooting the Gateway Service	10 of 18

Application and Print Problems

NetWare Print Queues Are Not Shown in Print Manager

In Print Manager, when you select the NetWare server where your print queues are located, no queues are shown because your credentials on the NetWare print server do not match those on your preferred server. The Gateway Service uses your preferred server credentials to access the print queue server.

If you do not see any print queues, verify that you can see NetWare servers in File Manager. If not, verify that the Gateway Service is started, as described in "Gateway Service Doesn't Start," earlier in this chapter.

If the Gateway Service is started and you cannot see the print queues on NetWare servers to which you have access, you do not have an authenticated connection to the server. To avoid this problem, you should synchronize your credentials on all the NetWare servers as described in "Validating a NetWare Account" in Chapter 4, "Connecting to a NetWare Volume or Directory."

If you do not want to synchronize your NetWare file server credentials with your preferred server credentials, at the command prompt type:

net use port: \\nwserver_name\queue_name /user:username password

For more information about printing, see "Connecting to a NetWare Print Queue Through Print Manager" in Chapter 3, "Connecting to a NetWare Print Queue."


NetWare-Aware Applications Are Not Working Correctly
Troubleshooting the Gateway Service	11 of 18

Application and Print Problems

NetWare-Aware Applications Are Not Working Correctly

To make sure the application is supported in this release, see the list of supported NetWare-aware applications in Chapter 5, "Running NetWare Utilities and NetWare-Aware Applications." Also verify that any required files mentioned in Chapter 5 are installed on your Windows NT computer in a directory that is in the computer's search path.

Supported applications include some MS-DOS – based and 16-bit Windows-based NetWare-aware applications. Some of the utilities that ship with NetWare 2.2, 3.11, or 3.12 are also supported.


NetWare Map Utility Fails with a Memory Allocation Error
Troubleshooting the Gateway Service	12 of 18

Application and Print Problems

NetWare Map Utility Fails with a Memory Allocation Error

The default environment for 16-bit programs is too small to accommodate the mapping table created by the NetWare map utility. You need to designate COMMAND.COM as the permanent command interpreter for the Command Prompt window and reset the default environment size allocated to the window. An environment of 4096 bytes is large enough to accommodate the NetWare utility, the mapping table, and the command interpreter.

To make these changes to the environment, enter this line in CONFIG.NT:

shell=%systemroot%\system32\command.com /e:4096

This line causes COMMAND.COM to be the command interpreter for the window as long as it remains open or until you issue another shell command, and it permanently allocates 4096 bytes to 16-bit programs you run in the window.


Other Network Problems
Troubleshooting the Gateway Service	13 of 18

Other Network Problems

This section briefly describes other network problems that could affect your ability to install or run the Gateway Service. For more network troubleshooting information, see the troubleshooting chapter in the Windows NT Server System Guide. See also the NETWORK.WRI file in your \systemroot directory.

If network problems persist, use Event Viewer from the Administrative Tools group to review the system log information generated during startup. Details in the system log will reveal possible interrupt conflicts or other driver problems.


Duplicate Computer Names
Troubleshooting the Gateway Service	14 of 18

Other Network Problems

Duplicate Computer Names

Each computer on a network must have a unique name. If you specify a computer name that is the same as another computer on the network or the same as a workgroup or a domain, the network will not start when you run Windows NT.


Services or Subsystems Do Not Start
Troubleshooting the Gateway Service	15 of 18

Other Network Problems

Services or Subsystems Do Not Start

If services or subsystems do not start properly, use the Services or Devices icons in Control Panel to check their status. You can try to start services using the Services option and start a device with the Devices option. Also, check the system log in Event Viewer for entries related to the problem.


Interoperability with Windows for Workgroups
Troubleshooting the Gateway Service	16 of 18

Other Network Problems

Interoperability with Windows for Workgroups

When setting up your network, check the following items to ensure smooth interoperability between Windows NT and Windows for Workgroups.

If you log on to a Windows for Workgroups computer whose workgroup name is the same as the name of a Windows NT Server domain, and if the user name and password are not valid for the domain, browsing will not be available. If you want to browse the domain, log on with a user name and password that are valid in the domain.

Guest accounts should remain enabled on domain controllers. Instead of removing guest accounts to restrict access to certain services, simply remove any unwanted guest account rights in User Manager.

Avoid duplicate user names on different domains. If a user name is duplicated across different domains, logging on will produce different results on the Microsoft network and the Windows for Workgroups workstation.


Using the Last Known Good Configuration
Troubleshooting the Gateway Service	17 of 18

Other Network Problems

Using the Last Known Good Configuration

If you encounter difficulty starting Windows NT, you may choose to start Windows NT using the Last Known Good Configuration.

1.	Start your computer and select Windows NT Server from the boot loader menu (if it does not start automatically).

2.	As soon as the screen clears and the words "OS Loader" appear on the screen, hold down the space bar.

Windows NT displays the Configuration Recovery menu, which asks you to choose either Current Startup Configuration or Last Known Good.

3.	To restore the last working system configuration, choose Use Last Known Good Configuration.

Configuration changes are lost if they were made since your system was last started successfully.


Using the Emergency Repair Disk
Troubleshooting the Gateway Service	18 of 18

Other Network Problems

Using the Emergency Repair Disk

If your system files are corrupt and you are unable to recover the previous startup configuration (Last Known Good), you can use the Emergency Repair disk to restore your system to its initial setup state. To repair a Windows NT installation, you must use the Emergency Repair disk specifically created for that installation during Windows NT Setup.

If your system becomes corrupt but you do not have the Emergency Repair disk created during installation, you must reinstall Windows NT from the original installation disks.

To restore Windows NT with an Emergency Repair disk on an x86-based computer

1.	Start Setup using the original Setup floppy disks or CD-ROM. (For example, insert Setup Disk #1 of the original Windows NT installation disks in drive A and start the computer.)

2.	In the first text-based Setup screen, type r to indicate that you want to repair your Windows NT files.

3.	Follow the instructions on the screen, inserting the Emergency Repair disk in drive A and providing any other Windows NT Setup disks as requested.

4.	When the final message appears, remove the Emergency Repair disk from drive A, and then press CTRL+ALT+DEL to restart your computer.

To restore Windows NT with an Emergency Repair disk on a RISC-based computer

1.	Start the Windows NT Setup program as instructed in your manufacturer-supplied documentation. (How you start Windows NT Setup depends on the type of RISC-based computer you are installing on.)

2.	In the first text-based Setup screen, type r to indicate that you want to repair your Windows NT files.

3.	Follow the instructions on the screen, inserting the Repair disk in drive A if Repair asks for it.

4.	When the final message appears, remove the Repair disk, and then press ENTER to restart your computer.

For more information about using your Repair disk, see Chapter 12 in the Windows NT Server System Guide.


NetWare to Windows NT Migration
Chapter 7	1 of 10

NetWare to Windows NT Migration

This chapter introduces the Migration Tool for NetWare in Microsoft Windows NT Server and provides information that you should understand before migrating servers from NetWare to Windows NT Server.

Topics include:

An introduction to the Migration Tool.

Information on planning a migration.

A comparison of NetWare and Windows NT networking models

A comparison of NetWare and Windows NT User Accounts

A comparison of NetWare and Windows NT administrative accounts

A comparison of NetWare and Windows NT directory and file security

Flowcharts to guide your use of the Migration Tool


The Windows NT Server Migration Tool for NetWare
NetWare to Windows NT Migration 	2 of 10

The Windows NT Server Migration Tool for NetWare

The Windows NT Server Migration Tool for NetWare can help you migrate NetWare 2.x and 3.x servers to computers running Windows NT Server. The Migration Tool transfers user and group accounts, and directories and files from NetWare servers to computers running Windows NT Server. Migrations are performed across the network with the Migration Tool running on Windows NT Server.

The Migration Tool allows you to:

Preserve appropriate user account information

Control how user and group names are transferred

Set passwords for transferred accounts

Control how account restrictions and administrative rights are transferred

Select the directories and files to transfer

Select a destination for transferred directories and files

Preserve effective rights on directories and files


Software Requirements
NetWare to Windows NT Migration 	3 of 10

The Windows NT Server Migration Tool for NetWare

Software Requirements

The Migration Tool runs on Windows NT Server. You can run the Migration Tool on the computer to which you are migrating or another computer running Windows NT Server. When you install Windows NT Server, you should also:

Install the Windows NT file system (NTFS) on computers to which you are transferring directories and files from a NetWare server. To preserve file and directory security, files and directories must be transferred to an NTFS volume.

Install the NetWare Link IPX/SPX Compatible Transport on the computer used to run the Migration Tool and computers taking part in the migration. The NWLink transport is an implementation of the IPX and SPX protocols used in Novell networks.

Install the Gateway Service for NetWare on the computer used to run the Migration Tool and computers taking part in the migration. The Gateway Service provides access to files and printers on NetWare servers, and allows computers on the Microsoft network to reach NetWare resources through a computer running Windows NT Server and the Gateway Service.


Planning a Migration
NetWare to Windows NT Migration 	4 of 10

Planning a Migration

Before performing a migration, you should become familiar with the differences between Windows NT Server and NetWare, and plan the migration. For more information on the two network operating systems, including information on the network models, user and administrative accounts, account restrictions, and file and directory security, see the sections later in this chapter.

When you are planning a migration, you should consider the following issues:

How your current workstations can access computers running Windows NT Server.

How users and groups should be migrated.

How directories and files should be migrated.

How to configure the user environment.

If you are planning to add Windows NT Server to provide file and print services, and existing workstations on your network are running NetWare client software, you must decide how to provide connectivity to Windows NT Server. In order to take advantage of all the features of Windows NT Server, you can upgrade workstations to Microsoft client software such as Windows NT, Windows™ for Workgroups 3.11, or the Workgroup Add-On for MS-DOS®. Upgrading workstations is often the best solution because Microsoft client software preserves a workstation's connectivity to NetWare servers while also supporting all the features available through Windows NT Server.

If you are planning to migrate many NetWare servers to Windows NT Server in several departments, you should consider how to best organize the network using one or more domains. The domain organization offered by Windows NT Server provides users complete access to the network with a single logon. It also eases the chore of account management because all accounts can be located centrally and, when domains are linked, each user needs only one account. A well-planned domain strategy can save administrative time and cost while increasing network ease of use for users. For more information on Windows NT domains, see "Comparing Network Models," later in this chapter and the Windows NT Server Concepts and Planning Guide.

To decide how computers running Windows NT Server should be organized, start by taking an inventory of your current network resources and how they are used. You should take into account both servers and client workstations. It may help to create a simple chart for this purpose that shows both the existing organization and the organization to which you are moving.

For example, you may find that a department relies on several servers that users in other departments rarely access and that all of the workstations in that department are running Windows 3.1. In this case, you may decide that the best course is to upgrade all workstations to Windows for Workgroups 3.11 and then migrate the servers to computers running Windows NT Server organized as a single domain.

In a more complex case, you may find that there are servers used by three departments where it is not practical to upgrade all workstations in all departments to Microsoft clients at once, and that servers in two of the departments should be consolidated into a single domain. In this case, you may decide to upgrade the first department to Microsoft clients, and provide users in the second department access to Windows NT Server using interoperability software and then migrate servers to a single domain composed of servers running Windows NT Server. Users in the third department can use existing NetWare servers until you are ready to migrate them to another domain.

Once you have determined which NetWare servers to migrate, you should also plan the order in which to migrate them. On NetWare networks, users have an account on each server they use. On Windows NT Server networks, administration is centralized so users need to have only one account. When you transfer accounts from multiple NetWare servers to a Windows NT domain, you will be consolidating user and group accounts. In most cases, it is easiest to migrate the server that contains the greatest number of user and group accounts. Then, as you migrate additional servers, you can use the Migration Tool to control how duplicate user and group accounts are handled.

Similarly, if volumes on NetWare servers have the same name and you are transferring the volumes to a single Windows NT Server computer, you should plan how you want the volumes organized on the Windows NT Server computer. By default, the Migration Tool merges all volumes that have the same name as a single shared directory, but you can also transfer each volume to a different share, or transfer each volume to a different subdirectory of the share.

You can use the Migration Tool to help you with these kinds of decisions by running a trial migration. When you run a trial, the Migration Tool creates a set of log files so that you can see how users and groups, and volumes will be transferred. By reviewing the log files, you can adjust migration options so that the migration runs just as you want.

To complete a migration, you should also plan how to use Windows NT logon scripts and user profiles to replace your current NetWare login scripts, and how to take advantage of the print services offered by Windows NT. For more information on these topics, see Chapter 11 "Completing the Migration."


Comparing Network Models
NetWare to Windows NT Migration 	5 of 10

Comparing Network Models

On NetWare 3.x or 2.x networks, each server contains its own entirely separate set of user accounts, and accounts must be administered by making changes on each server in the network. On Windows NT Server networks, servers can share account information when they are organized into one or more domains. A domain is a collection of servers that share a common user account database and security policy. In a domain, one server, the domain controller, stores all accounts and replicates changes to the backup domain controllers in the domain.

Domain organization allows a group of computers to behave as though they were a single server. Users can reach all the domain's resources with a single username and password. Account administration on a domain is easier because changes need to be made only on the domain controller. You can think of a domain as an expansion of the NetWare bindery to a larger organizational unit.

When you transfer user and group accounts from a NetWare server to a computer running Windows NT Server, the Migration Tool automatically creates the accounts on the domain controller of the server's domain. At the end of the migration process, accounts are replicated automatically to the Windows NT backup domain controllers in the domain.

For larger networks, you can link domains by establishing trust relationships between them. Once linked by trust, accounts in one domain can be used in another. For centralized administration, you can create a master domain, a single domain where all user accounts and global group accounts are stored. You can then use trust relationships to link each of the domains on the network to the master domain. When users log on and are authenticated by the master domain, resources throughout the network are available to them, yet all account information remains centralized for easy administration.

So that you can transfer user and group accounts from a NetWare server to a Windows NT Server master domain, the Migration Tool allows you to specify the domain to which accounts are transferred.

For more information on network security and domains in Windows NT networking, see the Windows NT Server Concepts and Planning Guide.


Comparing User Accounts
NetWare to Windows NT Migration 	6 of 10

Comparing User Accounts

User accounts on NetWare and Windows NT contain the same basic information: a username, a password, and the user's full name. Accounts also perform the same function: they establish a user's identity on the network. Both NetWare and Windows NT support groups so that you can administer network security easily. Both network operating systems support a range of restrictions that allow you to control user accounts.

On NetWare, most default account restrictions are set using the Supervisor Options and then can be changed for individual user accounts. On Windows NT, some account restrictions are set for individual user accounts, while others are enforced for all accounts in the domain. Restrictions that apply to all accounts in the domain are set as account policies in Windows NT. When the Migration Tool transfers restrictions that are supported for each user on Windows NT, it takes them from the transferred NetWare user account. When the Migration Tool transfers restrictions that are supported as Windows NT policies, it takes them from the default restrictions set using the NetWare Supervisor Options.

When you transfer accounts using the Migration Tool, you can control whether the following Supervisor default account restrictions are transferred or whether the current Windows NT account policy settings are used:

Require Password

Minimum Password Length

Require Password Change

Password Reuse

Intruder Lockout

By default, the Supervisor defaults are transferred. For more information, see Chapter 9, "Transferring Users and Groups."

The following table summarizes NetWare account restrictions and their Windows NT equivalents. It also shows whether a restriction is transferred from an individual NetWare account to an individual Windows NT account, or whether the restriction is transferred from the Supervisor default restrictions to a Windows NT policy setting.

Transferring Account Restrictions

NetWare Account Restriction		Windows NT Equivalent	How Transferred
Expiration Date		Expiration Date	By individual user account
Account Disabled		Account Disabled	By individual user account
Limit Concurrent Connections		None	Not transferred
Require Password		Permit Blank Password	As policy for all accounts
Minimum Password Length		Minimum Password Length	As policy for all accounts
Force Periodic Password Changes		Password Never Expires	By individual user account
Days Between Forced Changes		Maximum Password Age	As policy for all accounts
Grace Logins		None	Not transferred
Allow User to Change Password		User Cannot Change Password	By individual user account
Require Unique Passwords		Password Uniqueness	As policy for all accounts
Station Restrictions		None	Not transferred
Time Restrictions		Logon Hours	By individual user account
Intruder Detection/Lockout		Account Lockout	As policy for all accounts
User Disk Volume Restrictions		None	Not transferred
The following sections describe NetWare account restrictions, their Windows NT equivalents, and how restrictions are transferred.

Account Restrictions

Expiration date

On both NetWare and Windows NT networks, you can set a date when the account expires. Accounts expire at the end of day for the date you have set. The Migration Tool sets this restriction for each account transferred to Windows NT based on the setting for the NetWare user account.

Account Disabled

You can disable individual user accounts on both NetWare and Windows NT networks. The Migration Tool sets this restriction for each account transferred to Windows NT based on the setting for the NetWare user account.

Limit Concurrent Connections

NetWare supports limiting the number of concurrent network connections a user may have. Because Windows NT does not support this restriction, the Migration Tool does not transfer this information.

Password Restrictions

Require Password

Whether or not account passwords are required. On Windows NT, a password is not required when the policy for accounts allows blank passwords. By default, the Migration Tool sets this restriction for Windows NT based on the setting for the NetWare Supervisor Option.

Minimum Password Length

The minimum number of characters required for passwords. The NetWare default is a minimum of 5; the Windows NT default is a minimum of 6. By default, the Migration Tool sets this restriction for Windows NT based on the setting for the NetWare Supervisor Option.

Force Periodic Password Changes

The number of days a password can be used before the user is required to change it. The NetWare default is 40 days; the Windows NT default is 42 days. By default, the Migration Tool sets this restriction for Windows NT based on the setting for the NetWare Supervisor Option.

Require Unique Passwords

The number of different passwords a user is required to use before the system allows reuse of a password. NetWare requires 8 different passwords. The Windows NT default is 5 and can be set from 1 to 8. By default, the Migration Tool sets this restriction for Windows NT based on the setting for the NetWare Supervisor Option.

Allow User to Change Password

Whether or not users can change their own passwords. By default on both NetWare and Windows NT, users can change their passwords. The Migration Tool sets this restriction for each account transferred to Windows NT based on the setting for the NetWare user account.

Grace Logins

Windows NT does not support this restriction, and it is not transferred.

Station Restrictions

Station restrictions limit the workstations from which a user can log in. Workstations are specified according to their network and node addresses. Because Windows NT does not support these restrictions for the NetWare network, they are not transferred. Windows NT supports a similar feature for use on the Windows NT network. For each user, you can specify up to 8 workstations from which the user can log on to the domain.

Time Restrictions

Time restrictions specify the hours during which a user can log in to the network. The Migration Tool sets this restriction for each account transferred to Windows NT based on the setting for the NetWare user account.

On NetWare, time restrictions are set in half-hour blocks. On Windows NT, time restrictions are set in hour blocks. The Migration Tool adjusts blocks set at the half hour to the whole hour when transferring time restrictions. For example, if the NetWare restriction allows a user to log on between 7:30 A.M. and 7:30 P.M., the user will be able to log on between 7:00 P.M. and 8:00 P.M. on Windows NT.

Intruder Detection/Lockout

When intruder detection and lockout is in effect, a specified number of unsuccessful logon attempts is allowed before the account is locked for a specified amount of time. By default, the Migration Tool sets the number of attempts allowed on Windows NT based on the setting for the NetWare Supervisor Option.

By default, NetWare servers allow 7 attempts before locking the account, while Windows NT servers allow 5 attempts before locking the account.

User Disk Volume Restrictions

Disk restrictions limit the amount of disk space a user can use on a NetWare volume. Windows NT does not support this restriction, and it is not transferred.


Comparing Administrative Accounts
NetWare to Windows NT Migration 	7 of 10

Comparing Administrative Accounts

On a NetWare network, the Supervisor has complete control over the network, and you can grant limited administrative privileges to other users and groups by adding them to the lists of managers and operators. Similarly, on a Windows NT network, the administrator and members of the Administrators group have complete control of the network, and you can grant limited administrative privileges to users and groups by adding them to built-in administrative groups.

For more information on the use of administrative groups in Windows NT, see the Windows NT Server Concepts and Planning Guide.

Supervisor

The NetWare Supervisor is equivalent to the Windows NT administrator. Just as users on NetWare can be made Supervisor equivalents, you can grant users full administrative privileges on Windows NT by adding them to the Administrators group.

By default, when transferring user accounts, the Migration Tool does not add accounts that have Supervisor rights to the Windows NT Administrators group. However, you can choose to do so. For more information on transferring administrative privileges, see Chapter 9, "Transferring Users and Groups."

Workgroup Manager and User Account Manager

The closest equivalent to the NetWare Workgroup Manager and User Account Manager is the Account Operators group on Windows NT.

Like Workgroup Managers, Account Operators can create, delete, and manage user and group accounts. Unlike Workgroup Managers, Account operators can manage any user or group except other administrative groups, not just those they have created.

Like User Account Managers, Account Operators can manage and delete user accounts. Unlike User Account Managers, who can manage only users and groups they have been assigned, Account operators can manage any user or group except other administrative groups.

Because user account administration is centralized on a Windows NT domain, there is no need to delegate account administration to individual users who have administrative power on a particular server. For this reason, when transferring accounts, the Migration Tool does not add accounts who are Workgroup or User Account Managers to the Windows NT Account Operators group.

File Server Console Operator

The closest equivalent to the NetWare Console Operator is the Server Operators group on Windows NT. However, members of the Server Operators group have more expansive powers than NetWare Console Operators. In addition to the ability to down the server, broadcast messages, see connection information, and set the system date and time, Server Operators can also back up and restore files and directories, lock and unlock the server, and share and stop sharing directories. Unlike Console Operators, whose control can be restricted to a single server, Server Operators have control of every server in the domain.

Because Server Operators have greater power than Console Operators, the Migration Tool does not transfer users and groups who are Console Operators to the Windows NT Server Operators group.

Print Server Operator and Print Queue Operator

The NetWare Print Server and Print Queue Operators are equivalent to the Windows NT Print Operators group. On a Windows NT network, the functionality represented by NetWare printers and print queues is integrated and administered from Print Manager. Print Operators can perform all of the tasks of Print Server and Print Queue Operators, including change queues and printer forms as well as manipulate the jobs within a queue.

The Migration Tool automatically adds users and groups who are Print Server Operators to the Windows NT Print Operators group. Because adding Print Queue Operators to the Windows NT Print Operators group would grant them more authority than they currently have as NetWare Print Queue Operators, the Migration Tool creates a new group, Queue Operators, and adds NetWare Print Queue Operators to that group. To grant members of the Queue Operators group permission to manipulate documents waiting in a printer's queue, use Print Manager to add the group to the Printer Permissions list for the printer and grant the group Manage Documents permission.

For more information on printing on Windows NT, see Chapter 11 "Completing the Migration," and the Windows NT Server Concepts and Planning Guide.


Comparing Directory and File Security
NetWare to Windows NT Migration 	8 of 10

Comparing Directory and File Security

Like NetWare, Windows NT secures directories and files by controlling groups' and users' access to them. When you use the Migration Tool to transfer directories and files from a NetWare server to a Windows NT Server computer, their effective rights are translated to the equivalent Windows NT permissions. Windows NT security is supported through the NTFS file system. To preserve security, you must transfer files to an NTFS volume.

Supervisors on NetWare and Administrators on Windows NT have complete access to all directories and files; however, Windows NT implements this feature with an additional protection for users. Under NetWare 3.x security, the Supervisor has immediate access to all directories and files. Under Windows NT security, the Administrator does not automatically have immediate access. The owner of a directory or file, most often the user who created the directory or file, controls who can use the directory or file. The owner can set permissions that deny access to the Administrator. However, an Administrator always has the right to take ownership, and, as owner, can grant access to take control of the directory or file. Since administrators can always control directories and files, this scheme protects the system. It also protects users from unwarranted intrusion. Because ownership cannot be returned, users who check the ownership of their directories and files can see whether an administrator has taken control of them.

For more information on Windows NT directory and file security, see the Windows NT Server Concepts and Planning Guide and the Windows NT Server System Guide.

Directory Rights

The effective rights for directories are mapped to the following Windows NT permissions:

Directory Rights

NetWare Directory Rights		Windows NT Directory Permissions
Supervisory (S)		(All) (All)
Read (R)		(RX) (RX)
Write (W)		(W) (W)
Create (C)		(W) (W)
Erase (E)		(D) (D)
Modify (M)		(W) (W)
File Scan (F)		(R) (R)
Access Control (A)		(P) (P)
File Rights

Windows NT does not support the Create (C) and File Scan (F) rights for files. These rights are ignored when files are transferred. The effective rights for files are mapped to the following Windows NT permissions:

File Access Rights

NetWare File Rights		Windows NT File Permissions
Supervisory (S)		(All)
Read (R)		(RX)
Write (W)		(W)
Erase (E)		(WD)
Modify (M)		(W)
File Scan (R)		Does not map
Access Control (A)		(P)


Comparing File Attributes
NetWare to Windows NT Migration 	9 of 10

Comparing File Attributes

As it does with NetWare rights, the Migration Tool maps NetWare file attributes to their Windows NT equivalents when transferring files. NetWare supports a different set of attributes than Windows NT. The following NetWare file attributes are not supported by Windows NT and are ignored: Copy Inhibit (C), Execute Only (X), Indexed (I), Purge (P), Read Audit (Ra), Shareable (Sh), Transactional (T), and Write Audit (Wa). The table below shows how supported NetWare attributes map to Windows NT file attributes.

File Attributes

NetWare File Attributes	Windows NT File Attributes
Read Only (Ro)	Read Only (R)
Delete Inhibit (D)	Read Only (R)
Rename Inhibit (R)	Read Only (R)
Archive Needed (A)	Archive (A)
System (SY)	System (S)
Hidden (H)	Hidden (H)
Read Write (Rw)	None - files without the R attribute can be read and written to.


Migration Decisions
NetWare to Windows NT Migration 	10 of 10

Migration Decisions

You can execute a migration by simply starting the Migration Tool, choosing a NetWare and Windows NT server, and starting the migration. However, in most cases you should run a trial migration to make sure that the migration will execute as you want. In addition, there are a variety of options you may want to consider before actually executing the migration.

The flowcharts in the following sections present an overview of the migration process that you can use to guide your decisions.

Running a Migration

This flowchart outlines the steps of a migration. Use it as a guide when you are running your migration.

Setting User and Group Options

This flowchart covers the options available for transferring users and groups with the Migration Tool. For more information on a particular option and step-by-step procedures, see Chapter 9, "Transferring Users and Groups."

Setting File and Directory Options

This flowchart covers the options available for transferring files and directories with the Migration Tool. For more information on a particular option and step-by-step procedures, see Chapter 10, "Transferring Files and Directories."

Running a Migration

Setting User and Group Options

Setting File and Directory Options


Using the Migration Tool for NetWare
Chapter 8	1 of 7

Using the Migration Tool for NetWare

This chapter discusses the basics of the Migration Tool. Topics include:

Starting and quitting the Migration Tool

Saving migration options for later use

Selecting the servers for migration

Running a trial migration

Using the log files to review migration information

Running a migration


Starting and Quitting the Migration Tool
Using the Migration Tool for NetWare	2 of 7

Starting and Quitting the Migration Tool

When you start the Migration Tool for the first time, the Select Servers For Migration dialog box is displayed so that you can start choosing the NetWare and Windows NT servers you want to use. The migration options for users, groups, directories, and files are set to their defaults.

To select a NetWare server to migrate, you must have Supervisor rights on the server. To transfer data to a Windows NT Server computer, you must be a member of the Administrators group.

When you quit the Migration Tool before running a migration, the current list of servers and the migration settings are saved. The next time you start the utility, the list of servers and the migration settings are restored.

To run the Migration Tool and to access NetWare servers, the Windows NT Server computer must be running the NWLink IPX/SPX Compatible Transport and the Gateway Service for NetWare. For more information on NWLink and the Gateway Service, see Chapter 1 "Setting Up the Gateway Service and NWLink."

To start the Migration Tool

1.	From the File menu in Program Manager, choose Run.

2.	In the Command Line box, type nwconv.

3.	Choose the OK button.

If this is the first time you have started the Migration Tool since running a migration, the Select Servers For Migration dialog box is displayed so that you can start selecting the servers you want to migrate. To see the Migration Tool's main window, either select a pair of servers or cancel the dialog box.

To quit the Migration Tool

In the Migration Tool window, choose the Exit button, or choose Exit from the File menu.

You can add the Migration Tool to a program group to make it easier to start.

To add the Migration Tool to a program group

1.	Arrange your desktop so that you can see both File Manager and the program group in Program Manager where you want to add the Migration Tool.

2.	In File Manager, select nwconv.exe. The file is located in the directory \systemroot\SYSTEM32 with your other Windows NT system files.

3.	Drag the file from File Manager to Program Manager, placing it in the group window or on the group icon.


Saving and Restoring Migration Options
Using the Migration Tool for NetWare	3 of 7

Saving and Restoring Migration Options

When you exit the Migration Tool before running a migration, the list of servers and the migration options you have specified for groups, users, directories, and files are saved. The next time you start the utility, the Migration Tool restores the list of servers and migration options.

When you want to clear the list of servers and return the utility to its default options, you can restore the default configuration.

If you want to save the list of servers and the migration options for use later, you can save this information in a configuration file. By default, configuration files are saved with a .CNF extension.

To save a list of servers and migration options

1.	From the File menu, choose Save Configuration.

2.	In the Save As dialog box, type a name for the file in the File Name box.

You can save the file in a different drive and directory by selecting the drive in the Drives box and directory in the Directories box.

3.	Choose the OK button.

To restore a list of servers and migration options

1.	From the File menu, choose Restore Configuration.

2.	In the Open dialog box, select the filename in the File Name box.

If the file is located on a different drive, you can move to the drive by selecting it in the Drives box. If the file is located in a different directory, you can move to the directory by navigating directories in the Directory box.

3.	Choose the OK button.

To clear the list of servers and restore the default migration options

From the File menu, choose Restore Default Config.


Selecting Servers for Migration
Using the Migration Tool for NetWare	4 of 7

Selecting Servers for Migration

You can select one or more NetWare servers to migrate, and one or more Windows NT Server computers to accept the data from the NetWare servers. For example, you may want to reproduce the configuration of a single NetWare server by transferring the data from it to a similarly configured Windows NT Server computer, or you may want to replace more than one NetWare server with a single Windows NT Server computer.

To select a NetWare server to migrate, you must be logged on to the server as a Supervisor. To transfer data to a Windows NT Server computer, you must be a member of the Administrators group.

You can either add all pairs of servers involved in the migration to the list at one time, or add a pair of servers, make changes to the migration options, and then add the next pair of servers. The Migration Tool applies options set for the current pair of servers to the next pair of servers that you add to the Servers For Migration list. When you want migration options other than the defaults applied to several servers, it is easiest to set the options for one pair of servers and then add the remaining pairs to the list.

To add servers to the Servers For Migration list

1.	Choose the Add button.

2.	In the Select Servers For Migration dialog box:

Choose the Browse button next to the From NetWare Server box, choose a NetWare server from the list in the Select NetWare Server dialog box, and then choose the OK button.

Then choose the Browse button next to the To Windows NT Server box. The Select Windows NT Server dialog box displays domains and computers. Choose a domain name to display a list of computers in the domain. Choose a Windows NT Server computer from the list, and then choose the OK button.

– Or –

Type the name of a NetWare server in the From NetWare Server box and the name of a Windows NT Server computer in the To Windows NT Server box.

3.	Choose the OK button.

To remove servers from the Servers For Migration list

1.	Select the servers in the Servers For Migration list.

2.	Choose the Delete button.


Running a Trial
Using the Migration Tool for NetWare	5 of 7

Running a Trial

Before running an actual migration, you should run a trial migration to make sure that users and groups, and files and directories will be transferred as you planned. During a trial migration, the Migration Tool keeps track of events as though an actual conversion were in progress. Keep this in mind when you are reviewing a trial migration. For example, if you are transferring users from several NetWare servers that contain accounts for the same user, the Migration Tool will report the name conflicts even though no user by that name exists currently on the computer running Windows NT Server. If you have specified shares for file transfers that do not yet exist on the computer running Windows NT Server, do not expect to see them created on the computer until you run an actual migration.

When you run a trial, the Migration Tool generates a set of files that contain migration information.

LOGFILE.LOG contains information on users, groups, and files, including the information that currently exists on the NetWare server.

SUMMARY.LOG presents an overview including the names of servers that were migrated and the number of users, groups, and files that were transferred.

ERROR.LOG shows any information that the Migration Tool could not transfer, and information on any system failures that prevented the migration, for example, running out of disk space.

You can review the files to see what information is on the server you are migrating and what trouble spots there may be in the migration. Then, before running the migration, you can change options for users, groups, directories, and files so that information is transferred the way you want.

For more information on these files, see "Using Log Files" later in this chapter.

To run a trial migration

1.	Add the NetWare and Windows NT servers you want to use for the trial to the Servers For Migration list.

2.	For each pair of servers you are migrating, you can set migration options for users and groups by choosing the User Options button.

3.	For each pair of servers you are migrating, you can select the volumes, directories, and files to transfer, and specify destinations for them on Windows NT Server computers by choosing the File Options button.

4.	To start and run the trial, choose the Trial Migration button.

While the migration runs, a dialog box tracks the progress of the migration.

For flowcharts that show the steps of a migration, see Chapter 7 "NetWare to Windows NT Migration."


Using Log Files
Using the Migration Tool for NetWare	6 of 7

Using Log Files

When you run a trial or actual migration, the Migration Tool records information on the migration in three files: LOGFILE.LOG, SUMMARY.LOG, and ERROR.LOG. When you are running a trial, review the files to see what information is on the servers you are migrating and to see how the information will be transferred. When you are migrating servers, use the information in the log files to troubleshoot the migration.

You can view or print the files using the Migration Tool. The files are located in the directory \systemroot\SYSTEM32. Each time you run a trial or a migration, the Migration Tool creates a new set of files with a .LOG extension. The previous .LOG files are renamed using a number for the filename extension. When you see a list of numbered log files in a directory, those named with the highest number are the most recent.

Setting the Amount of Information to Be Logged

By default, when you run a trial or actual migration, the Migration Tool records complete information for user and group accounts, and summary information for directories and files.

To set the amount of information to be logged

1.	Choose the Logging button.

2.	In the Logging dialog box:

To display a message and pause the migration when an error such as a duplicate username occurs during migration, select the Popup On Errors check box.

To record only the names of users and groups in the log file instead of complete account information, clear the Verbose User/Group Logging check box.

To record a complete list of files transferred, including their sources and destinations, select the Verbose File Logging check box.

3.	Choose the OK button.

Viewing Log Files

The Migration Tool provides a tool, LOGVIEW.EXE, that allows you to view and print log files.

To view log files

1.	Choose the Logging button.

2.	In the Logging dialog box, choose the View Log Files button.

The LogView application starts and automatically displays the current set of log files.

To print a log file

1.	Choose the Logging button.

2.	In the Logging dialog box, choose the View Log Files button.

The LogView application starts and automatically displays the current set of log files.

3.	Select the window showing the file you want to print.

4.	From the File menu, choose Print.

Reviewing the Log File

LOGFILE.LOG provides a complete record of the migration that includes both what was successfully transferred and what failed because of an error.

The file includes the following information:

Transfer Options

A record of the settings for user, group, and file transfer options.

Supervisor Defaults

A record of the defaults for the NetWare Supervisor account.

Group Information

A record of the NetWare groups added to Windows NT.

User Information

By default, when verbose logging is active, the Migration Tool records account information first for the original NetWare account and then for the new Windows NT account. For NetWare accounts, this includes information on password and account restrictions as well as additional information such as allowed login times. A similar set of information is recorded for new Windows NT accounts.

To show allowed login times, the log file presents a chart like the one below where asterisks indicate the blocks of time during which a user can log in.

File Information

By default the Migration Tool lists the volumes copied and the number of files copied. You can also record a complete list of files and directories copied that includes information such as file size and date.

Reviewing the Summary File

SUMMARY.LOG provides statistics for the migration.

The file includes the following information:

Names of migrated servers

Total running time for the migration

Note that the running time for a trial migration will be shorter than that for an actual migration, particularly when files are transferred.

Total number of users transferred per server

Total number of groups transferred per server

Total number of files transferred per server

Total number of name conflicts

Total number of errors

Reviewing the Error File

ERROR.LOG provides a list of any errors that occurred.

User and group names of accounts that were not transferred successfully

Network errors, such as the failure to access a server

System errors, such as a lack of disk space for file transfers


Running a Migration
Using the Migration Tool for NetWare	7 of 7

Running a Migration

Before running a migration, run a trial migration as described earlier in this chapter. This allows you to see and correct problems such as username conflicts before actually migrating servers.

Important

When you run a migration, make sure that all users other than yourself have logged off the servers you are migrating and that files on the servers are closed.

When you start a migration, the Migration Tool checks:

That there is enough room on the destination servers to transfer files.

That the destination volumes use the Windows NT file system (NTFS).

That directory and filenames do not conflict.

When the migration is completed, the Migration Tool displays the log files so that you can review the migration. If you have transferred user and group accounts, the Windows NT primary domain controller replicates user and group account information to the Windows NT backup domain controllers in the domain.

For flowcharts that show the steps of a migration, see Chapter 7 "NetWare to Windows NT Migration."

To run a migration

1.	Add the NetWare and Windows NT servers you want to include in the migration to the Servers For Migration list.

2.	For each pair of servers you are migrating, you can set migration options for users and groups by choosing the User Options button.

3.	For each pair of servers you are migrating, you can select the volumes, directories, and files to transfer, and specify destinations for them on Windows NT Server computers by choosing the File Options button.

4.	To start and run the migration, choose the Start Migration button.

While the migration runs, a dialog box tracks the progress of the migration.


Transferring Users and Groups
Chapter 9	1 of 10

Transferring Users and Groups

This chapter steps you through the options available when transferring users and groups with the Migration Tool for NetWare. Topics include:

Switching off the transfer of groups and users

Setting options for passwords assigned to transferred accounts

Handling name conflicts for user and group names

Transferring account restrictions and administrative rights

Controlling the transfer of user and group accounts using a mapping file

Transferring accounts to a Windows NT master domain


Options for Transferring Users and Groups
Transferring Users and Groups	2 of 10

Options for Transferring Users and Groups

By default, all user accounts are transferred from the selected NetWare server to the domain of the selected Windows NT Server computer except when there is a name conflict. When a username on the NetWare server is identical to a username on the Windows NT domain, the account is not transferred, and an error is logged. When a group name is identical, the account is not transferred, and no error is logged.

In addition, the following default settings affect user and group transfer:

Transferred accounts can be reached without a password.

NetWare account restrictions for passwords and intruder lockout are transferred.

Groups and users who have Supervisor, Workgroup Manager, and User Account Manager rights are transferred to Windows NT without administrative privileges.

To see how users and groups will be transferred by default, you can run a trial migration and then review the file LOGFILE.LOG. You can then adjust settings or use a mapping file created by the Migration Tool to control precisely how accounts are transferred.

You can change user and group options for a pair of servers in the User and Group Options dialog box. To display the dialog box, select the servers in the Servers For Migration list and choose the User Options button.

The following table lists the default options for transferring users and groups, and lists the other options that are available.

Options for Transferring Users and Groups

Default options		Other options
Transfer groups and users		Transfer directories and files only
Allow login without a password		Set password for each account to the account's username Set password for all accounts to a specified password  Use a mapping file to specify a password for each account
Allow continued use of assigned password		Force users to change the password when they log in
Do not overwrite existing Windows NT user accounts when there is a name conflict, but log the conflict		Do not overwrite existing user accounts and do not log conflicts Overwrite existing user accounts and log conflicts Create a new user account when there is a conflict by adding a prefix to the username and log the conflict Use a mapping file to transfer conflicting accounts to new user accounts
Do not overwrite existing group accounts and do not log conflicts		Do not overwrite existing group accounts and log conflicts Create a new group account when there is a conflict by adding a prefix to the group name and log the conflict Use a mapping file to transfer conflicting accounts to new group accounts
Transfer NetWare account restrictions for passwords and intruder lockout		Use Windows NT account restrictions
Do not transfer accounts with Supervisor rights to the Windows NT Administrators group		Transfer accounts with Supervisor rights to the Windows NT Administrators group
Transfer user and group accounts to the domain of selected Windows NT Server computer		Transfer user and group accounts to a trusted master domain


Switching Off Group and User Transfer
Transferring Users and Groups	3 of 10

Switching Off Group and User Transfer

For each server you are migrating, you can switch off group and user transfer in order to transfer files only.

To switch off group and user transfer

1.	In the Servers For Migration list, select a pair of NetWare and Windows NT servers.

2.	Choose the User Options button.

3.	In the User and Group Options dialog box, clear the Transfer Users And Groups check box.


Setting Password Options
Transferring Users and Groups	4 of 10

Setting Password Options

When you transfer users' accounts from a NetWare server, passwords for accounts are not transferred. For accounts created on Windows NT, you can set passwords to no password, the username, or a password of your choice. You can also specify that users must change their passwords the first time they log on.

By default, accounts are transferred with no password set, and users must change the password when they log on.

If you want to specify a password for each account, you can do so by creating and editing a mapping file that maps accounts to new usernames and passwords. For more information on creating and using a mapping file, see "Mapping Accounts," later in this chapter.

To set password options

1.	In the Servers For Migration list, select the pair of servers whose password options you want to change.

2.	Choose the User Options button.

3.	In the User And Group Options dialog box, choose the Passwords tab.

4.	Choose one of the following options to set passwords for transferred accounts:

Choose No Password to allow users to log on without providing a password. The No Password option is the default.

Choose Password Is Username to set the password for each account to the username of the account.

Choose Password Is and type a password in the text box to set the password for all accounts to that password. Passwords can be up to 14 characters long. Keep in mind that Windows NT distinguishes between uppercase and lowercase characters in passwords.

5.	Clear the User Must Change Password check box if you do not want to force users to change their passwords when they log on.

6.	Choose the OK button.


Handling Username Conflicts
Transferring Users and Groups	5 of 10

Handling Username Conflicts

By default, when you transfer usernames from NetWare to Windows NT, names that already exist on the Windows NT server or domain are not transferred. This ensures that existing Windows NT accounts are not changed. When a conflict occurs, it is recorded in the ERROR.LOG file so that you can see it.

You can also:

Specify to neither transfer account information for conflicting names nor log conflicts. If you have transferred accounts from one of several NetWare servers that have identical accounts, you may want to select this option when you are transferring accounts from the additional servers.

Overwrite existing Windows NT account information when there is a name conflict. If you choose this option, keep in mind that you will be changing the passwords and other account information for the current users on the Windows NT domain.

Create a new account on the Windows NT server or domain when there is a conflict by adding a prefix to the current username.

If you want complete control over transferring usernames, you can also use a mapping file. For more information on using a mapping file, see "Mapping Accounts," later in this chapter.

To set options governing username conflicts

1.	In the Servers For Migration list, select the pair of servers whose username options you want to set.

2.	Choose the User Options button.

3.	In the User And Group Options dialog box, choose the Usernames tab.

4.	Choose one of the following options to set how conflicting usernames are handled:

Log Error

This is the default choice. Account information for conflicting usernames is not transferred to Windows NT, and information on each conflict is added to the ERROR.LOG file.

Ignore

Account information for conflicting usernames is not transferred to Windows NT. Conflicting usernames are not included in the ERROR.LOG file.

Overwrite With New Info

Current Windows NT account information for conflicting usernames is overwritten with information from the NetWare server. Information on each conflict is added to the ERROR.LOG file.

Add Prefix

When a conflict occurs, a new account is created by adding a specified prefix to the existing username. Information on each conflict is added to the ERROR.LOG file.

When you choose this option, type a prefix in the Add Prefix box. To avoid errors due to usernames that are too long, keep the prefix short. Usernames on Windows NT can be up to 20 characters long and can contain any uppercase or lowercase characters except the following:

" / \ [ ] : ; | = , + * ? < >


Handling Group Name Conflicts
Transferring Users and Groups	6 of 10

Handling Group Name Conflicts

Because both NetWare and Windows NT groups are used primarily to organize user accounts, there is no information that needs to be transferred with the group name. Consequently, by default, when you transfer group names from NetWare to Windows NT, names that already exist on the Windows NT server or domain are ignored, and name conflicts are not recorded in the ERROR.LOG file. User accounts from the NetWare server are added to the existing Windows NT group.

You can also:

Record group name conflicts in the ERROR.LOG file.

Create a new group name on the Windows NT server or domain when there is a conflict by adding a prefix to the current group name. User accounts from the NetWare group are added to the new group.

Use this option when you are transferring groups from multiple NetWare servers to a single Windows NT domain and there are identical group names on the NetWare servers whose accounts you do not want to merge into one group. For example, if you are migrating all of the servers in the Sales department to a single domain and the servers use identical group names for different groups of users, you can specify a different prefix for group name conflicts for each server you migrate. You could specify NAT- when migrating the server used by National Sales and INTER- when migrating the server used by International Sales. This ensures that needed groups are preserved on the Windows NT domain. If the SALES group exists already on the Windows NT domain, the Migration Tool creates a group called NAT-SALES and a group called INTER-SALES when transferring the SALES groups from the two servers.

If you want complete control over transferring group names, you can also use a mapping file. For more information on using a mapping file, see "Mapping Accounts," later in this chapter.

To set options governing group name conflicts

1.	In the Servers For Migration list, select the pair of servers whose group name options you want to set.

2.	Choose the User Options button.

3.	In the User And Group Options dialog box, choose the Group Names tab.

4.	Choose one of the following options to set how conflicting group names are handled:

Log Error

Conflicting group names are ignored, and information on each conflict is added to the ERROR.LOG file.

Ignore

This is the default choice. Conflicting group names are ignored. Conflicting group names are not included in the ERROR.LOG file.

Add Prefix

When a conflict occurs, a new group name is created by adding a specified prefix to the existing group name. Information on each conflict is added to the ERROR.LOG file.

When you choose this option, type a prefix in the Add Prefix box. To avoid errors due to group names that are too long, keep the prefix short. For example, you could specify NW- as the prefix to indicate that the new group was transferred from a NetWare server. Then a conflict for the group name SALES would result in a new group named NW-SALES. Group names on Windows NT can be up to 20 characters long and can contain any uppercase or lowercase characters except the following:

" / \ [ ] : ; | = , + * ? < >


Transferring Account Restrictions
Transferring Users and Groups	7 of 10

Transferring Account Restrictions

By default, when you transfer user accounts from NetWare to Windows NT, NetWare default account restrictions are transferred to accounts created on Windows NT. If you do not choose to transfer account restrictions, the equivalent current Windows NT account policy settings are used.

When transferring default account restrictions, the Migration Tool transfers the following information:

Require Password

Whether or not account passwords are required. On Windows NT, a password is not required when the policy for accounts allows blank passwords.

Minimum Password Length

The minimum number of characters allowed for passwords. The NetWare default is a minimum of 5; the Windows NT default is a minimum of 6.

Require Password Change

The number of days a password can be used before the user is required to change it. The NetWare default is 40 days; the Windows NT default is 42 days.

Password Reuse

The number of different passwords a user is required to use before the system allows reuse of a password. NetWare requires 8 different passwords. The Windows NT default is 5, and can be set from 1 to 8.

Intruder Lockout

The number of unsuccessful logon attempts allowed before the account is locked. By default, NetWare servers allow 7 attempts before locking the account. The Windows NT default is 5.

To set the transfer of account restrictions

1.	In the Servers For Migration list, select the pair of servers whose transfer of account restrictions you want to set.

2.	Choose the User Options button.

3.	In the User And Group Options dialog box, choose the Defaults tab.

4.	Clear the Use Supervisor Defaults check box to use current Windows NT account policy settings.

– Or –

Choose the Use Supervisor Defaults check box to transfer account restrictions from the NetWare server to Windows NT.


Transferring Administrative Rights
Transferring Users and Groups	8 of 10

Transferring Administrative Rights

By default, groups and users who have Supervisor rights are transferred to Windows NT without administrative privileges. You can choose to add groups and users who have Supervisor rights to the Administrators group on Windows NT. Users added to the Administrators group have power equivalent to NetWare Supervisors in the Windows NT domain.

For more information on Windows NT Server and NetWare administrative accounts, see Chapter 7 "NetWare to Windows NT Migration."

To set the transfer of administrative rights

1.	In the Servers For Migration list, select the pair of servers whose transfer of administrative rights you want to set.

2.	Choose the User Options button.

3.	In the User And Group Options dialog box, choose the Defaults tab.

4.	Choose the Add Supervisors To The Administrators Group check box to add groups and users with Supervisor rights to the Windows NT Administrators group.

– Or –

Clear the Add Supervisors To The Administrators Group check box to transfer groups and users without granting them administrative privileges.


Mapping Accounts
Transferring Users and Groups	9 of 10

Mapping Accounts

Rather than setting general options for names and passwords in the User And Group Options dialog box, you can use a mapping file to specify how account information is transferred to a server running Windows NT.

Use the Migration Tool to create a mapping file. By editing the file, you can specify a new name and password for each user you are transferring and a new name for each group. Entries in the file for which you do not provide a new name are transferred without change. The Migration Tool prompts you to edit the file as soon as it has been created; however, you can edit it at any time using a text editor such as Notepad. The file contains an entry for each user and group, for example:

[THORJ]

NewName=

Password=

To change the username for THORJ to THORJOH and to set THORJ's password to OMEGA48, add the changes following the equal signs:

[THORJ]

NewName=THORJOH

Password=OMEGA48

When you are assigning usernames, keep in mind that they must be unique on the server and within the server's domain. Usernames can be up to 20 characters long and can contain any upper or lowercase characters except the following:

" / \ [ ] : ; | = , + ? < >

Passwords can be up to 14 characters long. Keep in mind that Windows NT distinguishes between uppercase and lowercase characters in passwords.

To create and edit a mapping file

1.	In the Servers For Migration list, select the NetWare server whose groups and users you want to map.

2.	Choose the User Options button.

3.	In the User And Group Options dialog box, select the Use Mappings In File check box.

4.	Type a name for the file in the Use Mappings In File box.

5.	Choose the OK button.

The Migration Tool creates a text file that lists all of the users and groups on the NetWare server you selected and prompts you to edit the file.

6.	Choose Yes to edit the file.

For each username in the file, you can add a new username and password. For each group in the file, you can add a new name.

7.	When you have finished editing the file, save and close it.


Transferring Accounts to a Windows NT Master Domain
Transferring Users and Groups	10 of 10

Transferring Accounts to a Windows NT Master Domain

If you are transferring user accounts to a Windows NT Server network where all user accounts are located in a master domain, you can transfer accounts from your NetWare servers to the domain controller of the master domain. Directories and files are transferred to the Windows NT Server computers specified in the Servers For Migration list.

When you transfer groups to a master domain, they are created as global groups in the master domain and again as local groups on the server specified in the Servers For Migration list. The local group on the server contains the global group from the master domain. This allows you to easily add other global groups to the local group later.

Directories and files transferred to the Windows NT are secured by setting permissions for the transferred users and local groups.

For more information on domains, and local and global groups, see the Windows NT Server Concepts and Planning Guide.

To transfer accounts to a master domain

1.	In the Servers For Migration list, select the pair of servers whose accounts you want to transfer.

2.	Choose the User Options button.

3.	In the User And Group Options dialog box, choose the Advanced button.

4.	Select the Transfer Users To Trusted Domain check box and then choose the name of a domain.


Transferring Files and Directories
Chapter 10	1 of 7

Transferring Files and Directories

This chapter steps you through using the Migration Tool to transfer files and directories from servers running NetWare to servers running Windows NT Server. Topics include:

Switching off the transfer of files and directories

Removing or adding NetWare volumes to transfer

Changing the destination to which NetWare directories and files are transferred

Selecting the NetWare directories and files to transfer

Transferring Hidden and System files


Options for Transferring Files and Directories
Transferring Files and Directories 	2 of 7

Options for Transferring Files and Directories

By default, all appropriate directories and files are transferred from all NetWare volumes on the selected server to the selected Windows NT Server computer. Directories and files that are transferred retain their effective rights provided they are copied to an NTFS volume. For more information on how NetWare rights are transferred to Windows NT permissions, see Chapter 7 "NetWare to Windows NT Migration."

When determining where to transfer directories and files, the Migration Tool looks for a share name on the computer running Windows NT Server that matches the volume name on the NetWare server. If no share exists, the Migration Tool creates one when the migration is run. The Migration Tool locates shares it creates by first looking for enough space on NTFS volumes, and next, if it cannot find a suitable NTFS volume, on FAT volumes.

By default, the following are not transferred:

Hidden files

System files

The \SYSTEM, \MAIL, \LOGIN, and \ETC directories and their files on the NetWare SYS: volume

To see which directories and files will be transferred by default, you can view them in the Files To Transfer dialog box. If the check box next to a directory or file is cleared, that directory or file will not be transferred. You can also run a trial migration and then review the file LOGFILE.LOG to see which directories and files will be transferred.

The following table lists the default options for transferring files and directories, and lists the other options that are available.

Options for Transferring Files and Directories

Default options		Other options
Transfer files and directories		Transfer groups and users only
Transfer all NetWare volumes		Select volumes to transfer
Transfer to default destination shares		Change destination shares
Transfer all files and directories except NetWare  system directories and files		Select directories and files to transfer
Do not transfer system files		Transfer system files in selected directories
Do not transfer hidden files		Transfer hidden files in selected directories


Switching Off File Transfer
Transferring Files and Directories 	3 of 7

Switching Off File Transfer

You can switch off file transfer in order to transfer groups and users only.

To switch off file transfer

1.	In the Servers For Migration list, select a pair of NetWare and Windows NT servers.

2.	Choose the File Options button.

3.	In the File Options dialog box, clear the Transfer Files check box.


Selecting Volumes to Transfer
Transferring Files and Directories 	4 of 7

Selecting Volumes to Transfer

By default, all NetWare volumes are transferred. You can remove and add volumes to the list.

If you add a volume to a NetWare server after you have selected which volumes, directories, and files to transfer, you must add it to the list manually.

To remove a NetWare volume from the transfer list

1.	In the Servers For Migration list, select the server whose volume you want to remove.

2.	Choose the File Options button.

3.	In the File Options dialog box, select the volume you want to remove in the Source Files list, and then choose the Delete button.

To add a NetWare volume to the transfer list

1.	In the Servers For Migration list, select the server whose volume you want to add.

2.	Choose the File Options button.

3.	In the File Options dialog box, choose the Add button.

4.	In the Add Volume To Copy dialog box, select a volume in the Volume box.

By default, the Migration Tool suggests the volume name as the name of the share to which the volume is copied. You can specify a different share, create a new share, or specify a subdirectory of the share as a destination. For more information, see "Specifying a Destination Share" later in this chapter.

5.	Choose the OK button.


Specifying a Destination Share
Transferring Files and Directories 	5 of 7

Specifying a Destination Share

For each NetWare volume, the Migration Tool transfers the contents to a shared directory named after the volume on the computer running Windows NT Server. You can specify a different shared directory and subdirectory as a destination instead. If the shared directory and subdirectory do not exist, the Migration Tool creates them when it runs the migration.

When you are transferring the contents of more than one NetWare server to a single computer running Windows NT Server, you may find that the various NetWare servers use the same volume names. In such a case you may want to specify a destination other than the default so that the files and directories from the various servers are not all merged into a single directory on the computer running Windows NT Server. For example, if all the servers contain a directory called PUBLIC, by default, all the files and directories from the PUBLIC directories are transferred to a single PUBLIC share. Instead, you can transfer each PUBLIC volume to a different share or to a different subdirectory below the PUBLIC share.

To specify a destination directory

1.	In the Servers For Migration list, select the server whose destination you want to set.

2.	Choose the File Options button.

3.	In the File Options dialog box, select the volume in the Source Files list whose destination you want to set.

4.	Choose the Modify button.

5.	In the Modify Destination dialog box:

To transfer the source volume's contents to an available shared directory, select the shared directory in the Share box.

To transfer the source volume's contents to a new shared directory, choose the New Share button. The New Share dialog box allows you to specify a name for the share and a path for the share. For example, specify NWFILES as the share name and the path as d:\NWFILES to create a share called NWFILES and to transfer files and directories to a directory called NWFILES on the d: drive.

You can change the path for new shares, but not existing shares. To change the path of a share, select it in the Share box and choose the Properties button. The Share Properties dialog box allows you to specify a different path. For example, specify the path as d:\NWFILES to transfer files to a directory called NWFILES on the d: drive.

To transfer the source volume's contents to a subdirectory of the shared directory shown in the Share box, type the subdirectory's path in the Subdirectory box. For example, for the PUBLIC share, specify NWFILES to transfer files and directories to the subdirectory NWFILES.

6.	Choose the OK button.


Selecting Directories and Files to Transfer
Transferring Files and Directories 	6 of 7

Selecting Directories and Files to Transfer

By default, all files are transferred except files located on the NetWare administrative directories (\SYSTEM, \LOGIN, \MAIL, and \ETC), and hidden and system files. You can select which directories and files you want to transfer.

If files are added to a NetWare volume after you have finished selecting directories and files, they will be transferred only if all the files in that directory are selected for transfer. In other cases, you must add them to the list of files for transfer.

Only as much of the directory structure as necessary is transferred. If, for example, you have not selected any first level directories for transfer, the first level of the directory structure is not transferred.

To select directories and files to transfer

1.	In the Servers For Migration list, select the server whose files you want to transfer.

2.	Choose the File Options button.

3.	In the File Options dialog box, select the NetWare volume in the Source Files list that contains the directories and files you want to transfer, and then choose the Files button.

4.	The Files To Transfer dialog box displays the directory structure of the selected volume in the left pane and the files in the selected directory in the right pane. Choose a directory to display its subdirectories or use the options on the Tree menu. Select a directory to display its files.

To exclude a directory or file from transfer, clear the check box to the left of the directory or filename.

To transfer a directory or file, select the check box to the left of the directory or filename.

When only some subdirectories or files are selected in a directory, the check box for that directory is grayed.

5.	When you have finished selecting directories and files, choose the OK button.


Transferring Hidden and System Files
Transferring Files and Directories 	7 of 7

Transferring Hidden and System Files

By default, files with the Hidden (H) and System (SY) attributes are not transferred. You can select individual hidden and system files to transfer in the Files To Transfer dialog box, or you can transfer all hidden and system files in the directories you have selected to transfer by using menu options.

To transfer hidden and system files

1.	In the Servers For Migration list, select the server whose hidden or system files you want to transfer.

2.	Choose the File Options button.

3.	In the File Options dialog box, select the NetWare volume in the Source Files list that contains the hidden and system files you want to transfer, and then choose the Files button.

4.	In the Files To Transfer dialog box:

From the Transfer menu, choose Hidden Files to transfer all hidden files in the directories selected for transfer.

From the Transfer menu, choose System Files to transfer all system files in the directories selected for transfer.

5.	Choose the OK button.


Completing the Migration
Chapter 11	1 of 3

Completing the Migration

This chapter provides information on completing a migration. Topics include:

Using Windows NT Server user profiles and logon scripts to replace NetWare login scripts

Information on printing over the Windows NT network


Migrating Login Scripts
Completing the Migration 	2 of 3

Migrating Login Scripts

NetWare and Windows NT both support setting the environment for users who log on to the system. NetWare uses login scripts for this purpose. Because scripts are designed for a particular environment, the Migration Tool does not transfer them.

Windows NT allows you to use either user profiles or logon scripts to set the user environment. User profiles can accomplish everything that a script can; however, there are situations where a script is preferable. For example, because user profiles can be used on Windows NT computers only, use logon scripts to set the environment for MS-DOS - based workstations.

NetWare login scripts typically perform the following tasks. You can use either a Windows NT user profile or logon script for these same tasks.

Map Network Drives

A user profile reestablishes network connections through File Manager. A Windows NT logon script sets network connections using the net use command.

Assign a Print Queue to a Port

A user profile reestablishes connections to printers through Print Manager. A Windows NT logon script maps ports to network print shares using the net use command.

Start Programs

A user profile starts programs by placing them in a Program Manager startup group. A Windows NT logon script starts programs by including the name of the program in the file.

Using Windows NT Logon Scripts

A logon script is a batch (.BAT or .CMD) file used to configure a user's working environment each time the user logs on. Logon scripts can reestablish users' network connections (including connections to NetWare servers), start applications, and perform other tasks.

You can specify a logon script for one or more users from User Manager For Domains, the tool used to administer user accounts, groups, and security policies. You cannot set logon scripts for groups, but you can select all the users in a group and assign them the same logon script.

A logon script is always downloaded from the server that validates a user's logon request. The server locates the logon script by following the server's logon script path, usually \systemroot\SYSTEM32\REPL\IMPORT\SCRIPTS.

Because any Windows NT domain controller in the domain can validate a logon request, logon scripts for all user accounts in the domain must exist on every backup domain controller in the domain. You can perform the task of replicating logon scripts to servers automatically by using the Windows NT Replicator service.

For more information on logon scripts, see the Windows NT Server Concepts and Planning Guide and the Windows NT Server System Guide.

To assign logon scripts

1.	In the Administrative Tools group, choose User Manager For Domains.

2.	From the User menu, choose Select Users.

3.	In the Select Users dialog box, select the name of the group whose users you want to assign a logon script, and choose the Select button.

4.	Choose the Close button.

5.	From the User menu in the User Manager dialog box, choose Properties.

6.	In the User Properties dialog box, choose the Profile button.

7.	In the User Environment Profile dialog box, type the filename of the logon script in the Logon Script Name box.

If the logon script is stored in a subdirectory of the logon script path, precede the filename with that relative path. For example, you might type sales\anniep.cmd.

8.	Choose the OK button.

Using User Profiles

User profiles contain the per-user settings for the Windows NT environment. These settings include network connections, printer connections, program groups and items, and the appearance of windows and the screen. Connections made through a user profile are made in addition to connections made using a Windows NT logon script.

When a user logs on, the user's profile is loaded, and the user's Windows NT environment is configured according to that profile. On a Windows NT Server network, profiles can ensure that any workstation a user logs on to will be set up according to the user's preferences. You can also use profiles to tightly control a user's working environment.

Create and edit user profiles using User Profile Editor. Assign profiles to users using User Manager for Domains. You cannot assign user profiles to a group, but you can select all the users in a group and assign them the same profile. For each user, you can assign either a mandatory user profile or a personal user profile. A mandatory user profile cannot be changed by the user and remains the same from one session to the next. A personal user profile retains changes the user makes to the per-user settings of the Windows NT environment, and restores the latest settings each time that user logs on to any workstation running Windows NT.

To create and assign user profiles

1.	In the Administrative Tools group, choose User Manager for Domains.

To add network connections to the profile, use File Manager to make the connection, and select the Reconnect At Logon check box in the Connect Network Drive dialog box.

To add printer connections to the profile, use Print Manager to make the connection.

To start programs using the profile, add the programs you want to start to a startup group in Program Manager.

2.	To assign a profile to a user, use User Manager For Domains.

For more information, see the Windows NT Server Concepts and Planning Guide and the Windows NT Server System Guide.


Printing in Windows NT
Completing the Migration 	3 of 3

Printing in Windows NT

In a NetWare environment, you must create a print queue on the file server, install the print server and define a printer, and then assign the queue to the printer. In a Windows NT environment, simply use Print Manager to create a printer on the server and then share it.

A Windows NT printer is a virtual device that combines the printer and print queue functionality found in NetWare. You can create more than one Windows NT printer for a single physical printer, and each printer can have its own properties. For example, for the same physical printer, you can create a printer that prints during the day but is available to a restricted group of users, and a second printer that is available to all users but only prints the documents sent to it at night. A scheme like this can keep the physical printer available for important documents during the day, yet allow everyone to print large or less urgent documents during hours that are not as busy.

Network printing on Windows NT includes the following features:

Workstations running Windows NT can print to network printers without installing a print driver locally. Users can connect to the printer using Print Manager and print immediately.

The administrator can control access to network printers. Using Print Manager, you can restrict access to a printer to specific users and groups. For more information on printing administration in NetWare and Windows NT, see Chapter 7 "NetWare to Windows NT Migration."

Printers can be connected directly to the network through the Data Link Control (DLC) protocol. You can use Print Manager to create and share a printer for these devices just as though they were connected locally to the computer.

NetWare print queues are supported through the Gateway Service for NetWare. To print to NetWare printers, connect to the printer in Print Manager. Once connected, you can use Print Manager to share the NetWare print queue so that workstations that are not running the Client Service for NetWare can print to the queue.

For more information, see the Windows NT Server Concepts and Planning Guide and the Windows NT Server System Guide.


NWLink Registry Values
Appendix A	1 of 6

NWLink Registry Values

Microsoft NWLink is an implementation of the IPX/SPX protocols used in NetWare networks. In addition, the module NWLink NetBIOS provides support for the Novell implementation of the NetBIOS protocol.

This appendix describes the Registry parameters that you can modify for the following elements:

Global parameters for the IPX/SPX component of NWLink

Parameters that affect individual network adapter cards bound to NWLink

The NetBIOS component of NWLink NetBIOS, including modification of parameters supporting the Microsoft extensions to Novell NetBIOS

Caution

All entries have reasonable defaults that should not need to be modified. If a parameter does not appear in the Registry, the default value described in this appendix applies. Be careful when modifying Registry entries, because any change can easily affect the performance of a conversation between the sender and receiver.

You can impair or disable Windows NT if you make incorrect changes in the Registry while using Registry Editor. Whenever possible, use administrative tools such as Control Panel to make configuration changes, rather than using Registry Editor. If you make errors while changing values with Registry Editor, you will not be warned, because Registry Editor does not recognize semantic errors.

To make changes to the NWLink configuration using Registry Editor

1.	Run REGEDT32.EXE from File Manager or Program Manager, or at a command prompt, type start regedt32 and press ENTER.

When the Registry Editor window appears, you can press F1 to get Help on how to make changes in Registry Editor.

2.	In Registry Editor, click the window titled HKEY_LOCAL_MACHINE on Local Machine, and then click the icons for the SYSTEM subtree until you reach the appropriate subkey, as described in each of the following sections.

The NWLink keys do not appear in the Registry unless the NWLink protocol is installed using the Network option in Control Panel. After the service is installed, not all entries appear by default in the Registry. If the entry is not there, the default value for that entry is used.


NWLnkIPX: Global IPX Parameters
NWLink Registry Values	2 of 6

NWLnkIPX: Global IPX Parameters

The following parameters are global for the entire transport. The Registry path for these value entries is the following:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet	\Services\NWLnkIPX\Parameters

RipAgeTime	REG_DWORD	1 to 65535 minutes
IPX maintains an RIP cache in order to locate computers on a remote network. The RipAgeTime entry informs IPX how long to wait before requesting an RIP update for an entry. This timer is reset when an RIP announcement is received for an entry in the RIP cache.

Default:  5 minutes

RipCount	REG_DWORD	1 to 65535
When the RIP protocol layer is trying to find a route on the network, this parameter specifies how many times to send a request before giving up. Related parameter:  RipTimeout.

Default:  5

RipTimeout	REG_DWORD	1 to 65535 half-seconds
Specifies the time-out between RIP request packets being sent out when the RIP protocol layer is trying to find a route on the network. Related parameter:  RipCount.

Default:  1 (1 half-second)

RipUsageTime	REG_DWORD	1 to 65535 minutes
IPX maintains a RIP cache in order to locate computers on a remote network. The RipUsageTime entry informs IPX how many minutes to wait before an entry in the RIP cache will be deleted from the cache. This timer is reset when a packet is sent to the remote computer.

Default:  15 minutes

SourceRouteUsageTime	REG_DWORD	1 to 65535 minutes
Specifies the number of minutes an unused entry can remain in the token ring source routing cache before it is flushed.

Default:  10

InitDatagrams	REG_DWORD	1 to 65535
Specifies the number of datagrams initially allocated by IPX. Related parameter:  MaxDatagrams.

Default:  10

MaxDatagrams	REG_DWORD	1 to 65535
Specifies the maximum number of datagrams that IPX will allocate. Related parameter:  InitDatagrams.

Default:  50

SocketStart	REG_DWORD	0 to 65535
Specifies the start of the range that IPX uses to auto-assign sockets. Related parameters:  SocketEnd, SocketUniqueness.

Default:  0x4000

SocketEnd	REG_DWORD	1 to 65535
Specifies the end of the range that IPX uses to auto-assign sockets. Related parameters:  SocketStart, SocketUniqueness.

Default:  0x5fff

SocketUniqueness	REG_DWORD	1 to 65535
Specifies the number of sockets that IPX sets aside when auto-assigning a socket. For example, if SocketUniqueness is 8 and SocketStart is 0x4000, IPX will set aside the range 0x4000-0x4007. Related parameter:  SocketStart, SocketEnd.

Default:  8

VirtualNetworkNumber	REG_DWORD	0 to 4294967295
Specifies the virtual network number of this computer.

Default:  0

RipTableSize	REG_DWORD	1 to 65535
Specifies the number of buckets in the RIP hash table.

Default:  7

DedicatedRouter	REG_DWORD	Boolean
When set to 1 (true), this computer is a dedicated router and will not have services running on it.

Default:  0 (false)

EthernetPadToEven	REG_DWORD	Boolean
When set to 1 (true), Ethernet sends should be padded to an even length to accommodate ODI card drivers that can receive only even-length frames.

Default:  1 (true)

SingleNetworkActive	REG_DWORD	Boolean
When set to 1 (true), either the LAN or the WAN line can be active on the computer, but not both at once. This setting allows the Gateway Service for NetWare or the Client Service for NetWare to correctly locate NetWare servers on the WAN when dialed in.

Default:  0 (false)

DisableDialoutSap	REG_DWORD	Boolean
When set to 1 (true), IPX should disable SAP announcements and responses on dial-out WAN lines. This prevents the WAN line from being tied up with router to router SAP traffic and allows the Gateway Service for NetWare or the Client Service for NetWare on the machine to correctly discover servers on the WAN.

Default:  0 (false)

DisableDialinNetbios	REG_DWORD	Boolean
When set to 1 (true), IPX should prevent NetBIOS type 20 packets from going out over dial-in WAN lines. This setting prevents unneeded traffic on the WAN. The only case where DisableDialinNetbios should be false is when a NetBIOS application on the local computer needs to connect to a remote computer over a dial-in WAN line.

Default:  1 (true)


NWLnkSPX: Global SPX Parameters
NWLink Registry Values	3 of 6

NWLnkSPX: Global SPX Parameters

The following parameters are global for the entire transport. The Registry path for these value entries is the following:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet	\Services\NWLnkSPX\Parameters

ConnectionCount	REG_DWORD	1 to 65535
Specifies the number of times the probe will be sent when SPX is trying to connect to a remote node. If no response is received after the probes are sent, an error will occur. Related parameter:  ConnectionTimeout.

Default:  10

ConnectionTimeout	REG_DWORD	1 to 65535 half-seconds
Specifies the time between connection probes when SPX is trying to connect to a remote node. Related parameter:  ConnectionCount.

Default:  2 (1 second)

KeepAliveCount	REG_DWORD	1 to 65535
Specifies how many times to send a keep-alive probe before timing out if there is no response. Related parameter:  KeepAliveTimeout.

Default:  8

KeepAliveTimeout	REG_DWORD	1 to 65535 half-seconds
Specifies the time that the local side should wait before sending a probe to the remote to verify that the SPX connection is still alive. Related parameter:  KeepAliveCount.

Default:  12 (6 seconds)

WindowSize	REG_DWORD	1 to 10 SPX packets
Specifies the window to use in the SPX packets. SPX uses the Allocation field of the SPX packet to tell the remote how many receives are available for receiving data. The WindowSize entry specifies what value to put in the SPX Allocation field.

Default:  4

InitPackets	REG_DWORD	1 to 65535
Specifies the initial number of packets that SPX allocates.

Default:  5

MaxPackets	REG_DWORD	1 to 65535
Specifies the maximum number of packets that SPX will allocate.

Default: 30

InitialRetransmissionTime	REG_DWORD	1 to 65535millisecond
Specifies the amount of time that SPX will wait for an acknowledgement before sending a probe.

Default:  500 milliseconds

SpxSocketStart	REG_DWORD	0 to 65535
Specifies the start of the range that SPX uses to auto-assign sockets

Default:  0x4000

SpxSocketEnd	REG_DWORD	1 to 65535
Specifies the end of the range that SPX uses to auto-assign sockets.

Default:  0x7fff

SpxSocketUniqueness	REG_DWORD	1 to 65535
Specifies the number of sockets that SPX sets aside when auto-assigning a socket. For example, if SpxSocketUniqueness is 8 and SpxSocketStart is 0x4000, SPX will set aside the range 0x4000-0x4007.

Default:  8

MaxPacketSize	REG_DWORD	1 to 65535
Specifies the maximum packet size that SPX-2 will use when negotiating packet size with the remote network node. SPX-2 will use the correct size for the network if it is smaller than MaxPacketSize.

Default:  4096

RetransmissionCount	REG_DWORD	1 to 65535
Specifies the number of probes that SPX sends while awaiting an acknowledgement for data.

Default:  8


NWLink Parameters for the Network Adapter Card
NWLink Registry Values	4 of 6

NWLink Parameters for the Network Adapter Card

These parameters are specific for each binding of NWLink to a network adapter card. The Registry path for these value entries is the following:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services	\NWLnkIPX\NetConfig\<adapter name>

BindSap	REG_DWORD	Type field
Specifies the Ethertype if the frame format is Ethernet II. The Ethertype field is only relevant if Ethernet II frames are to be sent or received. You can choose the frame type using the Network icon in Control Panel. For more information, see the explanation for the PktType entry. Related parameter:  PktType.

Default:  8137 (in hex)

EnableFuncaddr	REG_DWORD	Boolean
When set to 1, this parameter specifies that the IPX functional address will be enabled if this card is a token ring card. If this value is 0, the IPX functional address will not be added. The IPX functional address is C00000800000 (hex). Novell has been phasing out use of this, but it is still in use in some places. It is up to the application to take advantage of the IPX functional address. In most instances, the broadcast address (FFFFFFFFFFFF hex) is used instead.

Default:  1 (true)

MaxPktSize	REG_DWORD	0 to 65535
Specifies the maximum frame size the network adapter card should be allowed to transmit. If this number is 0, NWLink will get this information from the card driver. This parameter allows the administrator to make the maximum transmit size for a card smaller than the card driver allows. A scenario in which you might want to change this entry is in an environment in which the network adapter card on one side of a conversation is on a link that has a larger frame size than the link on the other side of a conversation-for example, if the sending station is linked to a 16 Mbps token ring and the receiving station is linked to an Ethernet network.

Default:  0

NetworkNumber	REG_MULTI_SZ	Number
Specifies the network number (in hex) to be used for this adapter. If this number is 0, the NWLink will get the network number from the network as it is running. This parameter is set using the Network icon in Control Panel. IPX network numbers are 4 bytes (8 hex characters) long. An example of an IPX network number is AABBDDFF. You should not have to enter a specific value because NWLink will determine it for you. Make sure to get the network number for your IPX subnet from the network administrator if you want to enter a specific number.

If multiple packet types are used for an adapter, the network number for each can be specified by adding corresponding entries in the NetworkNumber multistring.

Default:  0

PktType	REG_MULTI_SZ	0, 1, 2, 3, 4, or FF
NWLink supports Ethernet, token ring, FDDI, and ArcNet® topologies. The PktType parameter specifies the packet form to use. The valid hexadecimal values are the following:

Value	Packet form
0	Ethernet_II
1	Ethernet_802.3
2	802.2
3	SNAP
4	ArcNet
FF	Auto-detect
If multiple packet types are used for an adapter, the network number for each can be specified by adding corresponding entries in the NetworkNumber multistring.

If the adapter is an Ethernet adapter, choose between values 0 through 3. If the adapter is either a token ring or FDDI adapter, choose between values 2 and 3. If you are using an ArcNet adapter, choose value 4. If the adapter is a token ring or FDDI adapter, values 0 and 1 will work the same as value 2. Related parameter:  BindSap.

Default:  1 (802.3)

SourceRouteBcast	REG_DWORD	0 or 1
Specifies the source route to be used when transmitting a packet to the broadcast MAC (Media Access Control) address (FFFFFFFFFFF hex). If this value is 0, the packet will be transmitted to the single-route broadcast (0xC2, 0x70). If the value is 1, the packet will be transmitted to the all-routes broadcast (0x82, 0x70). Related parameters:  SourceRouteDef, SourceRouting, and SourceRouteMCast.

Default:  0

SourceRouteDef	REG_DWORD	0 or 1
Specifies the source route to be used when transmitting a package to a unique MAC address that is not in the source routing table. If the MAC address is in the source routing table, the route in the table will be used. If this value is 0, the packet will be transmitted to the single-route broadcast (0xC2, 0x70). If the value is not 0, the packet will be transmitted to the all-routes broadcast (0x82, 0x70). Related parameters:  SourceRouteBcast, SourceRouting, and SourceRouteMCast.

Default:  0

SourceRouteMcast	REG_DWORD	Boolean
Specifies the source route to be used when transmitting a packet to a multicast MAC address (C000xxxxxxxx). If this value is 0, the packet will be transmitted to the single-route broadcast (0xC2, 0x70). If the value is not 0, the packet will be transmitted to the all-routes broadcast (0x82, 0x70). Related parameters:  SourceRouteBcast, SourceRouteDef, and SourceRouting.

Default:  0

SourceRouting	REG_DWORD	Boolean
Specifies whether to use source routing. This parameter is only used if the adapter is a token ring adapter. If there are no source routing bridges on the token ring, disable this entry to disable all of the source routing logic. Related parameters:  SourceRouteBcast, SourceRouteDef, and SourceRouteMCast.

Default:  0 (false)

DefaultAutoDetectType	REG_DWORD	0, 1, 2, 3, or 4
Specifies the packet type to use if IPX cannot detect any servers when detecting the network on startup. If a new packet type is detected, this value is updated by the transport. The valid values are the following:

Value	Packet form
0	Ethernet_II
1	Ethernet_802.3
2	802.2
3	SNAP
4	ArcNet
Default:  2 (802.2)

EnableWanRouter	REG_DWORD	Boolean
When set to 1 (true), the RIP router should be enabled for this adapter.

Default:  1 (true)


NWLnkNB Entries for Microsoft Extensions to Novell NetBIOS
NWLink Registry Values	5 of 6

NWLnkNB Entries for Microsoft Extensions to Novell NetBIOS

The Microsoft Extensions to Novell NetBIOS (NWLink NetBIOS) are included to enhance the performance of the traditional Novell NetBIOS protocol. NWLink NetBIOS can detect automatically whether it is talking to a Novell NetBIOS implementation that does not understand these extensions; in such a case, NWLink NetBIOS will fall back to the standard Novell NetBIOS protocol currently used in NetWare networks. However, significant performance gains can be realized if the extensions are used (for example, if the NetBIOS conversation occurs between two Windows NT computers).

The Registry path for these value entries is the following:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet	\Services\NWLnkNB\Parameters

AckDelayTime	REG_DWORD	50 to 65535 milliseconds
Determines the value of the delayed acknowledgement timer.

Default:  250

AckWindow	REG_DWORD	0 to 65535 frames
Specifies the number of frames to receive before sending an acknowledgement. The AckWindow entry is used as a clocking mechanism on networks in which the sender is networked on a fast LAN, but the receiver is networked on the other side utilizing a slower link. By automatically forcing acknowledgements, the sender can keep sending frames continually. If both the sender and receiver are located on a fast link, you can set AckWindow to 0 to turn off sending an acknowledgement to the sender. Alternatively, NWLink NetBIOS can be set to dynamically determine whether to use the AckWindow parameter based on the setting of AckWindowThreshold. Related parameter:  AckWindowThreshold.

Default:  2

AckWindowThreshold	REG_DWORD	0 to 65535 milliseconds
Specifies the threshold value for the round-trip time that defines when AckWindow will be ignored. The round trip time is an estimate of how long it takes for a frame to be sent and received from a workstation. NWLink NetBIOS determines this estimate and uses it as a basis for determining whether it is necessary to send automatic acknowledgements. If AckWindowThreshold is set to 0, NWLink NetBIOS relies on the AckWindow entry. Related parameters:  AckWindow.

Default:  500

EnablePiggyBackAck	REG_DWORD	0 or 1
Allows the receiver to piggyback acknowledgements. Piggybacking acknowledgements can occur when the receiver has detected the end of a NetBIOS message. When the sender and receiver are not participating in two-way NetBIOS traffic, you should set EnablePiggyBackAck to 0. An example of one-way traffic is a stock update application, where a server constantly sends NetBIOS messages to clients but the client does not need to respond.

If EnablePiggyBackAck is set to 1 but there is no back traffic, NWLink NetBIOS waits the number of milliseconds determined by AckDelayTime before sending the acknowledgement, and then it turns off support for piggybacking acknowledgements. If the workstation at some point starts sending as well as receiving data, NWLink NetBIOS turns support back on for piggybacking acknowledgements. Related parameter:  AckDelayTime.

Default:  1 (true)

Extensions	REG_DWORD	0 or 1
Specifies whether to use NWLink NetBIOS extensions discussed in this section.

Default:  1 (true)

RcvWindowMax	REG_DWORD	1 to 49152 frames
Specifies the maximum number of frames the receiver can receive at one time. The value specified by RcvWindowMax is sent to the sender during session initialization to give the sender an upper bound on the number of frames that can be sent at one time. Related parameters:  AckDelayTime, AckWindow, AckWindowThreshold, EnablePiggyBackAck, and RcvWindowMax.

Default:  4


NWLnkNB Entries for Novell NetBIOS or Microsoft Extensions
NWLink Registry Values	6 of 6

NWLnkNB Entries for Novell NetBIOS or Microsoft Extensions

The Registry path for these value entries is the following:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet	\Services\NWLnkNB\Parameters

BroadcastCount	REG_DWORD	1 to 65535
Specifies the number of times to send a broadcast. If Internet is set to 1, the BroadcastCount is doubled. Related parameter:  BroadcastTimeout.

Default:  3

BroadcastTimeout	REG_DWORD	1 to 65535 half-seconds
Specifies the time between sending find-name requests. This value is not affected if Internet is set to 1. Related parameter:  BroadcastCount.

Default:  1

ConnectionCount	REG_DWORD	1 to 65535
Specifies the number of times to send a connection probe. A connection probe is sent by the initiator of a session if a connection could not be made to the remote computer. If Internet is set to 1, the ConnectionCount is doubled. Related parameter:  ConnectionTimeout.

Default:  5

ConnectionTimeout	REG_DWORD	1 to 65535 half-seconds
Specifies the time between sending connection probes when initiating a session.

Default:  2

InitialRetransmissionTime		REG_DWORD	1 to 65535 milliseconds
Specifies the initial value for the retransmission time. Related parameter:  RetransmitMax.

Default:  500

Internet	REG_DWORD	0 or 1
Specifies whether to change the packet type from 0x04 to 0x14 (Novell WAN broadcast).

Default:  1 (true)

KeepAliveCount	REG_DWORD	1 to 65535
Specifies the number of times to send a session-alive frame before timing out if there is no response. Related parameter:  KeepAliveTimeout.

Default:  8

KeepAliveTimeout	REG_DWORD	1 to 65535 half-second
Specifies the time between sending session-alive frames. Related parameter:  KeepAliveCount.

Default:  60

RetransmitMax	REG_DWORD	1 to 65535
Specifies the maximum number of times the sender should retransmit before assuming that something is wrong with the link. Related parameter:  InitialRetransmissionTime.

Default:  8