10 Integracja NT i NetWare File and Print Services for NetWare

Operating System

File and Print Services for NetWare

Administrator's Guide

Abstract

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This white paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

Microsoft, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Other product and company names mentioned herein may be the trademarks of their respective owners.

Microsoft Corporation • One Microsoft Way • Redmond, WA 98052-6399 • USA

04/00

Contents

Installing File and Print Services for NetWare

Microsoft File and Print Services for NetWare is a utility that enables a computer running Microsoft Windows NT Server version 4.0 or 3.51 to function like a NetWare 3.12 file and print server. Novell NetWare clients can then access files and printers shared on the Windows NT Server computer without any modifications to their NetWare client software. The Windows NT Server computer can also continue to serve Microsoft network clients as normal. Using File and Print Services for NetWare (FPNW), you can integrate Windows NT Server and NetWare on your network. You can also easily migrate some or all of your servers from NetWare to Windows NT Server, as you can migrate servers without having to change client software at the same time.

This package contains two versions of File And Print Services For NetWare: version 4.0, which runs on Windows NT Server 4.0, and version 3.51, which runs on Windows NT Server 3.51.

This section provides information about the following topics:

An introduction to File and Print Services for NetWare

Planning for installation

Installing the utility

Configuring the utility

Managing NetWare Client Accounts

On Windows NT Server computers that have File and Print Services for NetWare installed, creating and managing user accounts for users of NetWare clients is similar to creating and managing Windows NT user accounts. This section provides information about creating NetWare client accounts and how to set account policies.

The following topics are included in this section:

A comparison of Windows NT and NetWare user and administrative accounts
Creating NetWare client accounts

User and Group Accounts

When File and Print Services for NetWare is installed on a server, User Manager for Domains enables you to set up, configure, and modify NetWare client accounts the same way you would for regular Windows NT accounts. When you create accounts for NetWare clients, you make them NetWare enabled. A NetWare enabled-account is a Windows NT user account that has a NetWare password associated with it.

When an account is NetWare enabled, the user of that account can access (over the network) Windows NT Server computers that run File and Print Services for NetWare. The user can do this while running standard NetWare client software — no additional software is required on the client computer.

Additionally, Windows NT Server has built-in group accounts that have administrative privileges. By adding a NetWare client account to one of these built-in groups, you can assign the same supervisor privileges as are assigned on a NetWare network. For more information about Windows NT Server built-in group accounts, see the Windows NT Server Concepts and Planning Guide.

Note

The Everyone group on Windows NT Server works a little differently than other built-in groups. The Everyone group always includes all users, including users with user accounts, users from other domains, and guest users. You cannot add users to or delete users from the Everyone group. Because you cannot modify the membership of the Everyone group, it does not appear in User Manager for Domains. It appears only in dialog boxes where you assign permissions or rights to groups and users.

When you install File and Print Services for NetWare on a Windows NT Server computer, an account named Supervisor is automatically created on the Windows NT Server computer. The Supervisor account is also added to the Administrators group on the server, allowing that account to have all administrative (supervisor) abilities on the server.

You can make an existing Windows NT user or group account be NetWare enabled by selecting Maintain NetWare Compatible Login in the User Properties dialog box. You can also copy existing NetWare user accounts from a NetWare server to a Windows NT Server computer using the Windows NT Server Migration Tools for NetWare. For more information about copying NetWare account information to a Windows NT Server computer, see the Windows NT Server Networking Supplement.

Comparing User Accounts

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

An account that has been NetWare enabled in a Windows NT domain allows the user to log on from a computer running NetWare client software and use resources that you have shared using File and Print Services for NetWare. The user is also able to use resources shared by any other Windows NT Server computers running File and Print Services for NetWare in the domain. In addition, the user can also use resources shared by any Windows NT Server computer running File and Print Services for NetWare in a trusting domain. In each of these cases, the user must attach or log in to each server that he or she wants to use.

For NetWare networks, most default account restrictions are set using the Supervisor Options feature and can be changed for individual user accounts. For Windows NT Server computers, some account restrictions are set for individual user accounts, while others are enforced for all accounts in the domain. Restrictions that apply to all user accounts in the domain are set as account policies in Windows NT Server.

BEGIN BREAK

END BREAK

The following table summarizes NetWare account restrictions and their equivalent File and Print Services for NetWare account restrictions.

NetWare account restriction	FPNW equivalent account restriction	Description

Expiration Date	Expiration Date	Sets a date when the account expires. Accounts expire at the end of day on the date you have set.
Account Disabled	Account Disabled	Disables accounts so users cannot log in.
Limit Concurrent Connections	Limit Concurrent Connections	Limits the number of connections a NetWare user can make.
Require Password	Permit Blank Password	Determines whether or not passwords are required. On Windows NT Server computers, a password is not required when the policy for accounts allows blank passwords.
Minimum Password Length	Minimum Password Length	Sets the number of required characters in the password. For an account on File and Print Services for NetWare, the default is a minimum of six characters.
Force Periodic Password Changes	Maximum Password Age	The number of days a password can be used before the user is required to change it. For user accounts using File and Print Services for NetWare, the default is 42 days.
Grace logins	Grace Logins	Specifies the number of times a user can log in with an expired password.

BEGIN BREAK

END BREAK

NetWare account restriction	FPNW equivalent account restriction		Description

Allow User To Change Password	User Cannot Change Password		Determines whether or not users can change their own passwords.
Require Unique Passwords	Password Uniqueness		The number of different passwords a user is required to use before the system allows a password to be reused. For user accounts using FPNW, the default is five, and can be set from one to eight.
Station Restrictions	Log On From All, Or Some Workstations		Determines which workstations a user can log in from.
Time Restrictions	Logon Hours		Specifies the hours during which a user can log in to the network. When time restrictions are translated from a NetWare server to a Windows NT Server computer, the time restrictions are adjusted to start and end on the hour.
Intruder Detection/Lockout		Account Lockout		When intruder detection and lockout options are in effect, a specified number of unsuccessful logon attempts is allowed before the account is locked for a specified amount of time. By default, servers running File and Print Services for NetWare allow five logon attempts before locking the account. The count is reset and the account unlocked after 30 minutes.
User Disk Volume Restrictions		—		Disk restriction limits the amount of disk space a user can use on a NetWare volume. Windows NT does not support this type of restriction; on Windows NT Server computers running File and Print Services for NetWare, user accounts do not have disk space limitations.

BEGIN BREAK

END BREAK

Comparing Administrative Accounts

On a NetWare network, a Supervisor has complete control over the network, and 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, members of the Administrators group have complete control of the network, and can grant full or limited administrative privileges to users and groups by adding them to built-in administrative groups. The Windows NT network provides built-in groups that by default have a particular set of user rights. Because user account administration is centralized on a Windows NT domain, there is no need to delegate account administration to multiple users who have individual administrative powers on particular servers.

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

The following table summarizes the built-in abilities of the administrative groups.

Built-in abilities	Assigned to

Create and manage user accounts	Administrators, Account Operators^*
Create and manage local and global groups	Administrators, Account Operators^*
Assign user rights	Administrators
Lock a server	Administrators, Server Operators
Override a lock of the server	Administrators, Server Operators
Format a server's hard disk	Administrators, Server Operators
Create common groups	Administrators, Server Operators
Keep the local profile	Administrators, Server Operators, Account Operators, Print Operators, Backup Operators
Share and stop sharing volumes (directories)	Administrators, Server Operators
Share and stop sharing printers and print queues	Administrators, Server Operators, Print Operators

^*Account Operators cannot modify the accounts of Administrators.

The following table summarizes the NetWare administrative privileges and their Windows NT equivalents. These administrative privileges are compared in the following sections.

NetWare administrative privilege	Windows NT equivalent

Supervisor	Administrator
Workgroup Manager	Account Operator
User Account Manager	Account Operator
File Server Console Operator	Server Operator
Print Server Operator	Print Operator
Print Queue Operator	Print Operator

Supervisor

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

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. The Account Operators group exists only on Windows NT Server computers that have been designated as the primary domain controller (PDC) or a backup domain controller (BDC).

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.

File Server Console Operator

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

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. The Windows NT Print Operators group can perform all of the tasks of both NetWare Print Server and Print Queue Operators, including changing queues and printer forms and manipulating the jobs within a queue.

If you want to restrict some users to only the tasks that NetWare Print Queue Operators perform, remove those users from the Print Operators group, and then give them Manage Document permission for individual printers. Users who have Manage Document permission can manipulate the documents waiting in the print queue but cannot administer the printer.

BEGIN BREAK

END BREAK

Creating NetWare Client User Accounts

You create user accounts for NetWare clients the same way you create user accounts for Microsoft network users, by using User Manager for Domains. Additional information is included for the account to be NetWare enabled.

When you create a NetWare-enabled account (either by creating a new account or enabling an existing account for NetWare), the account's Windows NT Server password and NetWare password are synchronized. If you are creating a new account (as NetWare-enabled), the password you supply for the Windows NT account will be the same for the NetWare client. If you are enabling an existing Windows NT Server account to be used from a NetWare client, you are prompted to provide a new password for that user.

For instructions on creating NetWare compatible accounts, see “Creating a NetWare Compatible User Account” in the online Help.

Note

The new Add User Accounts administrative wizard in Windows NT Server version 4.0 supports File and Print Services for NetWare, and can be used to create and modify NetWare-enabled accounts. To access the wizard, click the Start button, click Programs, click Administrative Tools, and then click Administrative Wizards.

To administer a user account property associated with one of the buttons at the bottom of the dialog box, click the button, and then complete the dialog box. Those properties are described in the following sections.

Groups Property

Putting NetWare-enabled user accounts into groups is the same as putting regular Windows NT user accounts into groups. Putting users into groups makes it easier and faster to grant multiple users access to a resource. To give a permission or right to all the users in a group, you just give that permission or right to the group itself.

When you assign a NetWare-enabled account to a group, keep in mind any domain trust relationships that you have established. You need to decide if you want the groups to have access to all servers and workstations in the domain and in trusting domains (a global group), or just access to the servers in a particular domain (a local group). In either case, NetWare clients won't be able to use the resources of Windows NT Server computers that don't have File and Print Services for NetWare installed. For additional information about groups, see the Windows NT Server Concepts and Planning Guide.

User Profile Property

Use the User Profile property to set the location of the user's profile script, the logon script, the home directory, and the NetWare home directory relative path. When you choose the User Profile button, the User Environment Profile dialog box appears. All entries in this dialog box are optional.

User Profile

The location for the Windows NT user profile is specified in the User Environment Profile dialog box. The user profile applies only when the user logs on from a Windows NT Workstation computer. For more information about user profiles, see the Windows NT Server Concepts and Planning Guide.

Logon Scripts

A user with a NetWare-enabled account can have two logon scripts (or login scripts). The Windows NT logon script is run when the user logs on from a Microsoft client computer, such as one running Windows NT Workstation, Windows 95, or LAN Manager.

When a user logs in from a NetWare client, up to two login scripts may run. First, the server's system login script (if any) runs. Then the user's personal login script runs. Each server can have one system login script, which is the same for every user and runs when any user logs in. A NetWare client user's personal login script is unique to that user.

On a server running File and Print Services for NetWare, you edit personal login scripts for NetWare clients in User Manager for Domains. You can edit the server's system login script by editing the Net$log.dat file, located in the SYSVOL\PUBLIC directory.

To edit a user's login script, double-click the user's name in the list of users in User Manager for Domains, click NW Compat, then click Edit Login Scripts.

Personal login scripts for NetWare clients are stored in the SYSVOL\MAIL directory. Each user that has a login script defined on the server has a subdirectory within this MAIL directory, and the subdirectory name is the same as the user's NetWare object ID. This subdirectory contains a file called LOGIN, which is the script that is executed when the NetWare client logs in.

Login scripts for NetWare clients are not replicated between Windows NT Server computers in a domain, unless you explicitly establish replication of the SYSVOL\MAIL directory tree. For more information about replication, see the Windows NT Server System Guide.

Note

Do not use the set command with the comspec environmental variable in NetWare login scripts. You can use the comspec variable but you cannot reset the value of comspec within the login script.

Logon Scripts in a Trusted Domain Environment

In a trusted domain environment, a user who has an account in a trusted account domain may log on from a NetWare client computer to a server running File and Print Services for NetWare in a trusting resource domain. The user's login script will run only if it exists on the server in the trusting resource domain.

Therefore, if you use NetWare login scripts with File and Print Services for NetWare, you should replicate them to the SYS\MAIL directories of any File and Print Services for NetWare server to which the user may log onto. This includes File and Print Services for NetWare servers in resource domains. For more information on account domains, resource domains, and the Windows NT Server domain structure, see the Windows NT Server Concepts and Planning Guide.

When setting up replication of logon scripts, set up the primary domain controller of the domain containing the user account as the export server. This server is where changes are made to the login script when you use the Edit Login Script option in User Manager for Domains.

Note that if the trusting resource domain also contains NetWare-enabled user accounts, these user accounts will probably have the same object id as user accounts in the account domain. In this case, login script conflicts will occur (where a user logging on will have another user's login script run), as NetWare login scripts are identified by the object id of the user account. If you use NetWare login scripts, you should not put NetWare-enabled user accounts in resource (or second-tier) domains.

Home Directory

The purpose of the user's home directory is to provide the user with a specific directory to store personal files and directories.

The settings in the Home Directory area of the User Environment Profile dialog box apply only when the user logs on from a Microsoft network client.

For users logging on from NetWare clients, you can set the NetWare Home Directory Relative Path. This specifies the path to the user's home directory relative to the server's Home Directory Root Path. The actual home directory is specified in two parts: the root of the home directory is specified on a per server basis; the relative path is specified in the user's account.

For example, suppose there are two users, JoeS and KathyS. The NetWare Home Directory Relative Path for JoeS is DIR\JOES, and for KathyS, it is DIR\KATHYS. There are also two servers, NT1 and NT2. On NT1, the Home Directory Root Path is SYS:ONE, and on NT2, it is SYS:TWO. In this case, the following statements are true:

When JoeS logs on to NT1, his full home directory path there is SYS:ONE\DIR\JOES.

When JoeS logs on to NT2, his path is SYS:TWO\DIR\JOES.

When KathyS logs on to NT1, her full home directory path is \\NT1\SYS\ONE\DIR\KATHYS.

Although there may be times when multiple home directories for one user on different servers might be advantageous, most users will only require a single home directory on a single server, so that all of their files are in one place. Therefore, if there are multiple servers running File and Print Services for NetWare in the domain and users will be using their home directories, it is recommended that the user's login script explicitly map a drive to the user's home directory on the server that actually contains the user's single home directory.

Logon Hours Property

Use this property to set the hours during which the user can log on to the server. The logon hours are set for a NetWare user account just as they are for a Windows NT user account. However, while NetWare networks use logon hour restrictions in half-hour (30-minute) increments, Windows NT Server computers use full-hour (60-minute) increments.

For user accounts using File and Print Services for NetWare, the logon and logoff times when a user is allowed to use the server are moved to the nearest whole hour, if necessary. When these time limits are changed, the user is allowed more time on the server. For example, if the NetWare network time restriction allows logon starting at 8:30 A.M., the Windows NT Server computer allows logon at 8:00 A.M. If the NetWare network logoff restriction is for 5:30 P.M., the Windows NT Server computer changes the logoff restriction to 6:00 P.M.

Logon To Property

Use the Logon To property to determine the Windows NT Workstation computers that the user can log onto and the NetWare compatible computers from which the user can log on. For instructions on how to specify the NetWare compatible computers from which the user can log on, see “Setting Workstation Restrictions” in Help.

Account Property

Use this property to define an account expiration date (if any) and to specify whether an account is a global or local account.

When an account has an expiration date, the account is disabled at the end of that day. Expired accounts are not deleted, only disabled. When an account expires, a user who is logged on remains logged on but cannot establish new network connections and cannot log on again after logging off.

For more information about local and global accounts, see the Windows NT Concepts and Planning Guide.

NetWare Properties

Use these properties to set NetWare-specific account information, such as the NetWare account password expiration, the number of grace logins for an account, and how many concurrent connections a user may have at the server. Grace logins are additional logins that a user is allowed to make after their password has expired. The grace logins provide the user an opportunity to change their expired password. Concurrent connections are different connections to resources shared on a single server. For example, if you limit a user's concurrent connections to three, then the user can only have three simultaneous connections to resources at the server.

Note

The NetWare Compatible Password Expired check box cannot be selected for a user at the same time you are changing the user's password. To change a user's password and select this check box, you must change the password, click OK, then again open the user account, click NW Compat, and click the NetWare Compatible Password Expired check box.

Changing Windows NT and NetWare Network Passwords

When you create a new user account and enable it for NetWare, or when you make an existing account NetWare-enabled, you assign the account a password. This password is set as both the user's Windows NT Server password (which the user types when logging on from a Microsoft client) and the user's File and Print Services for NetWare password, which the user uses when logging on from a NetWare client.

When an administrator needs to change a NetWare-enabled user's password, use User Manager for Domains, as you would to change the password for any Windows NT Server account. This changes both the user's Windows NT Server password and File and Print Services for NetWare password.

When NetWare-enabled users need to change their own passwords, how they should do so depends on what computer they are using.

When using a NetWare client computer, they use the setpass or chgpass command. These commands change both the user's Windows NT Server and File and Print Services for NetWare passwords. These commands are identical, and are provided under two different command names.

When using a Windows NT Workstation version 4.0 or version 3.51 client computer, the user just uses CTRL+ALT+DEL as normal. This changes both the user's Windows NT Server password and File and Print Services for NetWare password.

When using any other type of Microsoft client, such as an older version of Windows NT Workstation, Windows 95, or LAN Manager, if the user changes the password using the normal method for that client computer, only the user's Windows NT Server password will be changed. In this case, the user should also use the setpass or chgpass utility to change the File and Print Services for NetWare password.

Note

If the primary domain controller of the domain where the user's account is located does not both run Gateway Service for NetWare and have File and Print Services for NetWare installed, or if the user's computer cannot access the primary domain controller over the IPX/SPX protocol, then chgpass and setpass will change only the user's File and Print Services for NetWare password.

The chgpass, setpass, and login utilities work only if the support files Rpc16c1.rpc, Rpc16c6.rpc, and security.rpc are in the same directory as the utility file. When File and Print Services for NetWare is installed on a server, these files are copied to the SYS:\PUBLIC directory on the server. If you want users to run chgpass, setpass, or login from any other directory, copy the .rpc files as well as the .exe file to that directory.

Introducing File and Print Services for NetWare

File and Print Services for NetWare helps you integrate a Windows NT network and NetWare network by enabling you to perform the following tasks:

Enable users of NetWare client computers to access resources at the Windows NT Server computer

Share the directories and printers of a Windows NT Server so they are accessible to NetWare clients

Use a Windows NT Server computer to manage NetWare printers. By doing so, you can also make the NetWare printers available to users of Microsoft client computers.

The administration of NetWare accounts on a Windows NT network is centralized in the Windows NT Directory database (also called the security accounts manager database or SAM). You do not need to maintain separate NetWare accounts for a user on each Windows NT Server computer in the network. Instead, each account in the Windows NT Directory database can be enabled for NetWare client use.

File and Print Services for NetWare supports the following functions:

File access and the ability to manipulate file settings and permissions from Server Manager and third-party tools that manipulate NetWare servers

Creation and management of user accounts using User Manager for Domains

Printing and print queue manipulation

Remote administration

Secured logins

Packet burst and large internal packet (LIP)

NetWare locking and synchronization primitives that are used by some NetWare-specific applications

Long filenames, compatible with OS/2® long file name (LFN) support

However, File and Print Services for NetWare does not support the following NetWare groups and functions:

Workgroup Managers

Accounting

User disk volume restrictions

Setting Inherited Rights Masks (IRMs)

NetWare loadable modules

Transaction Tracking System (TTS)

When File and Print Services for NetWare is installed on a Windows NT Server computer, the server is able to communicate with NetWare client computers. As shown in the following figure, a server running File and Print Services for NetWare understands both the NetWare Core Protocol (NCP) and Microsoft Server Message Blocks (SMB).

A Windows NT Server computer running File and Print Services for NetWare can communicate with both NetWare clients and clients running Windows NT Workstation, Windows 95, or LAN Manager.

Planning for Installation

Before installing File and Print Services for NetWare, you should understand how the utility works with your Windows NT and NetWare networks. Before beginning the installation, you need to know the Ethernet or token-ring frame types already established on the NetWare network, and how you want those frame types to work with the network adapter cards in the computer where you will be installing File and Print Services for NetWare.

If you have network numbers already assigned, File and Print Services for NetWare automatically detects them, as long as the NetWare server or routers are available on the network. If you don't have network numbers assigned, the default of 00000000 is assigned as the internal network number, and you can change it later. If you have more than one network connected with routers, or if you are using multiple frame types on the same network adapter, you might need to configure the NetWare network numbers so there are no conflicts in data transmission. For more information about network number assignments, see Windows NT Server Services for NetWare Networks, contained in the Windows NT Server package.

If you have not already installed the NetWare Link IPX/SPX compatible transport (NWLink), you are prompted to install it before installing File and Print Services for NetWare. The NWLink transport is an implementation of the Internetwork Packet Exchange (IPX) and Sequenced Packet Exchange (SPX) protocols used in NetWare networks. For more information about NWLink, see Windows NT Server Services for NetWare Networks.

If you want to be able to assign effective rights for files and directories in a NetWare volume, you should install File and Print Services for NetWare on a server that uses the Windows NT file system (NTFS). You can create NetWare volumes on servers that use the file allocation table (FAT) file system, but you will not be able to enforce file-specific security. For more information about planning, review the information on Windows NT Server network security in the Windows NT Server Concepts and Planning Guide.

When you install File and Print Services for NetWare on a server, the File and Print Services administration tools are also installed on the server. You use these tools (extensions to User Manager for Domains and Server Manager) to administer the utility. Additionally, you can install just the administration tools on other computers running Windows NT Server or Windows NT Workstation, and then use these computers for remote administration of servers running the File and Print Services for NetWare utility.

Using File and Print Services for NetWare in Domains

On NetWare 2.x or 3.x networks, user accounts are administered by making changes separately on each server in the network. On Windows NT networks, servers are organized into domains. A domain is a collection of computers that share a common user account database and security policy. In a domain, one server (called the primary domain controller or PDC) stores all the accounts. A primary domain controller is a computer running Windows NT Server that authenticates domain logons and maintains the security policy and the master database for a domain. When you create or modify an account, you do it only once, on the primary domain controller. It then automatically replicates the change to the other servers in the domain. For user account information, the group of servers behave as though they were a single server.

In addition to the simplified administration, the network is also easier for end users, as they can reach all the domain's resources with a single user name and password.

For larger networks, you can link domains by establishing trust relationships between them. Trust relationships are links between domains that enable pass-through authentication. Once linked by trust, accounts in one domain can be used in another; the user has to log on to only one server to be able to use resources in the trusted domains.

You can think of a domain as an expansion of a single NetWare bindery to being used by several servers. NetWare servers, however, are not considered part of a Windows NT Server domain, nor can they be included in a trust relationship. For more information about domains, see the Windows NT Server Concepts and Planning Guide.

When you use File and Print Services for NetWare in a network with multiple domains, and trust relationships exist between the domains, you must keep a few points in mind. You might have a scenario where a NetWare-enabled user has an account in one domain (such as a master domain in the master domain model), and the user needs to access a server (running File and Print Services for NetWare) that is located in a domain that trusts the master domain. To ensure that the user can log in to the File and Print Services for NetWare server, you should do the following: install File and Print Services for NetWare on the primary domain controller in the trusted (master) domain, and install the File and Print Services for NetWare administrative tools on every backup domain controller in the master domain. This step ensures that the domain controller that authenticates the users' logon attempts (which may be a different domain controller each time) understands NetWare-enabled user accounts. Note that the File and Print Services for NetWare service does not have to be started on the primary domain controller — it needs only to be installed.

When File and Print Services for NetWare is installed on a server, you can administer the server from a different computer (running either Windows NT Workstation or Windows NT Server) in the same domain, or in a different domain. To do this, you must install the File and Print Services for NetWare administration tools on the computer from which you are administering the server. You are not required to have the File and Print Services for NetWare utility installed on the computer you use for administration.

However, if you want to use different tools (such as third-party administrative tools) to remotely administer File and Print Services for NetWare from a computer located in a different domain, then you must install File and Print Services for NetWare on the primary domain controller in the domain containing your user account, and install the File and Print Services for NetWare administrative tools on every backup domain controller in that domain. This step ensures that the computer validating your logon request understands NetWare-enabled user accounts.

If you install File and Print Services for NetWare on a Windows NT Server computer running as a server (instead of a primary or backup domain controller), the following guidelines show which users can use NetWare client computers to access the server.

If the server is in a domain, and the domain's primary domain controller has File and Print Services for NetWare installed (and the backup domain controllers have the File and Print Services for NetWare administrative tools installed), then users with NetWare-enabled accounts on the server, as well as NetWare-enabled user accounts in the domain, can access the server. Note that the File and Print Services for NetWare service does not have to be started on the primary domain controller — it needs only to be installed.

Installing the utility or its administrative tools on each domain controller ensures that the server that authenticates each user's logon request will always be a server that understands NetWare-enabled user accounts.

Only NetWare-enabled accounts can access the server.

Installing File and Print Services for NetWare

The Setup program for File and Print Services for NetWare creates a NetWare volume on the drive you specify (the default is drive C:). This volume is represented by a directory named SYSVOL, and SYSVOL includes a directory structure for NetWare client accounts. This SYSVOL functions similarly to the NetWare file server's SYS: volume. The following subdirectories are added to drive:\SYSVOL during installation:

Subdirectory	Description

LOGIN	Contains the utilities that NetWare clients use to log into Windows NT Server computers running File and Print Services for NetWare. When NetWare clients first connect to the Windows NT Server computer, a mapping to the LOGIN directory is automatically created.
MAIL	Contains subdirectories for each user. The subdirectory is specified by the user bindery object identification. The user subdirectories contain the user login scripts.
PUBLIC	Contains the utilities that NetWare clients use for accessing and using resources on a server running File and Print Services for NetWare. The utilities are: attach, capture, endcap, login, logout, map, setpass, and slist. For more information, see “Managing File and Print Services for NetWare.”
SYSTEM	Contains the files for printing and print server support.

By default, both NTFS file permissions and share permissions for the SYS: volume are set to allow full control to the whole network. Depending on your environment, you may want to change these permissions to improve security on the SYS volume.

If you are installing File and Print Services for NetWare in a domain, a user account named FPNW Service Account is created at installation. File and Print Services for NetWare uses this account to log in and perform operations between domain controllers in a domain. During the installation, you are prompted to supply a password for the FPNW Service Account. You must supply the same password on all the domain's servers on which you are installing File and Print Services for NetWare. The service account is automatically added to the Administrator's group.

Note

The FPNW Service Account is necessary to start File and Print Services for NetWare on all servers in the domain. Do not delete this account; if you do, the service will fail to start.

When you install File and Print Services for NetWare, it adds functionality to Server Manager, User Manager for Domains, and Control Panel. A NetWare Supervisor account is also created to which you can assign a NetWare password. The Supervisor account, which is created for administering NetWare servers, is automatically added to the Administrators group.

Server Manager gains a new menu, FPNW, where you can create, manage, and delete volumes that have been shared for NetWare clients.

User Manager for Domains has the new option to make an existing or new user account NetWare-enabled. A NetWare properties button is added to the Properties dialog box for users and groups. It is available only when a user is identified as a NetWare user. Use this button to configure NetWare-specific user account information. For more information about managing user and group accounts, see “Managing NetWare Client Accounts.”

In Control Panel, a new FPNW icon is added. Use this icon to configure the server and to manage connections and file usage at the server. For more information, see “Managing File and Print Services for NetWare.”

Additionally, some of the common utilities that are compatible with NetWare are installed. These 16-bit utilities can be used by clients running MS-DOS® so they can log in and access the services provided by File and Print Services for NetWare. These services are listed in the following table and described in more detail in “Managing File and Print Services for NetWare.”

To	Use these commands

Log in and log out	login, chgpass, setpass, attach, and logout
Use network resources	map and slist
Use printing resources	capture and endcap

If you install only the File and Print Services for NetWare Administration Tools, only the extensions to User Manager for Domains and Server Manager are installed. None of the system services that allow you to create accounts or volumes on the local computer, or any of the command-line utilities are installed.

Installation

To install File and Print Services for NetWare on a Windows NT Server computer, use the Network icon in Control Panel. After installation, you need to restart the computer.

During installation, you are prompted to choose between two options: installing the entire utility or just the administration tools. Choose File and Print Services for NetWare to install all the files necessary to run the utility on the local server. Choose File and Print Services for NetWare Administrative Tools Only to install only those files needed to perform remote administration of other servers.

To install File and Print Services for NetWare, you must be logged on as a member of the Administrators group.

Note

The Spooler service must be running on the server on which you are installing File and Print Services for NetWare.

Version 4.0

To install File and Print Services for NetWare on a Windows NT Server 4.0 computer

1. Double-click My Computer, then double-click Control Panel.

2. Double-click Network.

3. Click the Services tab, then click Add.

4. Click Have Disk.

Important

If File and Print Services for NetWare appears in the Network Service list, do not select it; instead, click Have Disk.

5. Insert the Services for NetWare compact disc in the computer's CD-ROM drive.

6. Type the appropriate path, and click OK.

The path is drive:\FPNW\NT40\processor, where drive is the drive letter of the CD-ROM drive and processor is the server's processor type. For example, type d:\fpnw\nt40\i386 to install on an x86-based computer with a CD-ROM drive at drive D. The possible values for processor are i386, MIPS, ALPHA, and PPC.

7. Select File and Print Services for NetWare, and click OK.

8. Fill out the Install File and Print Services for NetWare dialog box. For more information about the dialog box, click Help.

9. If you are installing File and Print Services for NetWare in a domain, you are prompted to enter a password for the FPNW Service Account.

If you install File and Print Services for NetWare on multiple domain controllers in a domain, you must specify the same password for each account on domain controllers where you install the utility.

10. Click Close, and then restart the computer to complete the installation.

Version 3.51

To install File and Print Services for NetWare on a Windows NT Server 3.51 computer

1. Double-click the Network icon in Control Panel.

2. In the Network Settings dialog box, click Add Software.

3. In the Add Network Software dialog box, select <Other> from the bottom of the list of available software, and then click Continue.

4. Insert the File and Print Services for NetWare compact disc into your CD-ROM drive.

5. In the Insert Disk dialog box, type the appropriate path to File and Print Services version 3.51.

The path is drive:\FPNW\NT351\processor, where drive is the drive letter of the CD-ROM drive and processor is the server's processor type. For example, type d:\fpnw\nt351\i386 to install on an x86-based computer with a CD-ROM drive at drive D. The possible values for processor are i386, MIPS, ALPHA, and PPC.

6. In the Select OEM Option dialog box, select File and Print Services for NetWare, and then click OK.

BEGIN BREAK

END BREAK

7. In Directory For SYS Volume, type the location for the SYSVOL directory that will be the NetWare SYS: volume.

This volume is the location for NetWare client home directories, login scripts, mail, and system files.

Note

Setup selects a default location for SYSVOL, which is C:\SYSVOL. It is recommended that you install this directory on an NT File System partition; if you install the NetWare volume on a non-NTFS partition, you lose the security features that NTFS provides and will not be able to set or enforce file or directory security settings.

8. Type a password for the supervisor's account in Supervisor Account.

You must type the same password in Password and Confirm Password. The password can be as many as 14 characters, and is case-sensitive.

9. If you are installing File and Print Services for NetWare in a domain, you are prompted to enter a password for the FPNW Service Account.

If you install File and Print Services for NetWare on multiple domain controllers in a domain, you must specify the same password for this account on each domain controller on which you install the utility.

10. In the Advanced Tuning group box, select one of the options described in the following table to tune the server's performance.

You can reconfigure the server's performance after you have installed it. For more information, see “Configuring File and Print Services for NetWare” later in this section.

Option	Description

Minimize Memory Usage	Decreases the amount of memory required to run File and Print Services for NetWare. Choose this option if the server will be used mainly for minimal file operations (for example, if you need more memory for application services).
Balance Between Memory Usage And Performance	Balances the amount of memory the server uses with the speed at which it will run. Choose this option if the server will be used for sharing applications (for example SQL Server) and as a network file and print server.
Maximize Performance	Increases the speed at which the server will run. Choose this option if the server will be used mainly for heavy network activity, such as network file sharing and as a print server for NetWare clients.

11. Click OK to complete the installation.

Restart the Windows NT Server to complete the installation process.

Upgrading From Version 3.51 to Version 4.0

If you're already running File and Print Services version 3.51 on a server, you can upgrade it to version 4.0.

To upgrade to File and Print Services for NetWare 4.0 from version 3.51.

1. Double-click My Computer, then double-click Control Panel.

2. Double-click Network.

3. Click the Services tab.

4. Click File and Print Services for NetWare, then click Update.

5. Insert the Services for NetWare compact disc in the computer's CD-ROM drive.

6. Type the appropriate path, and click OK.

The path is drive:\FPNW\NT40\processor, where drive is the drive letter of the CD-ROM drive and processor is the server's processor type. For example, type d:\fpnw\nt40\i386 to install on an x86-based computer with a CD-ROM drive at drive D. The possible values for processor are i386, MIPS, ALPHA, and PPC.

7. Click Close, and then restart the computer to complete the installation.

Enabling Filter of NetWare-Enabled Users

User Manager for Domains includes a feature that enables you to filter the list of users to show only NetWare-enabled users. To enable this feature on servers that previously ran File and Print Services for NetWare 3.51, you must copy the setnwusr utility from the Services for NetWare compact disc and run it. You need to run it only once after upgrading to File and Print Services for NetWare
version 4.0.

To copy the utility, put the Services for NetWare compact disc in the CD-ROM drive, and type the following: (assuming the CD-ROM is drive d)

expand d:\fpnw\nt40\platform\setnwusr.ex_ %systemroot%\system32

where platform is i386, MIPS, ALPHA, or PPC.

To run the utility, click Start, click Run, then type setnwusr.

Configuring File and Print Services for NetWare

When you have finished installing File and Print Services for NetWare, you can use Control Panel to change the server tuning (for example, to make it run faster or take up less memory), and to configure the frame types and network numbers used. Also, by default File and Print Services for NetWare is configured to automatically start when the server starts. If you want to change the service to be manually started, use the Services icon in Control Panel.

If necessary, you can also change the FPNW Service Account password for the domain.

For instructions on how to do these tasks, see the online Help topics:

“Configuring File and Print Services for NetWare”

“Configuring NWLink for FPNW”

“Configuring Startup”

“Changing the FPNW Service Account Password”

Tuning Server Performance

When you tune the memory usage or server performance after you have installed File and Print Services for NetWare, you can balance the amount of memory the server uses against how fast the server runs.

For instructions on how to do this task, see the online Help topic “Configuring File and Print Services for NetWare.”

Configuring Frame Types and Network Numbers

After installation, you can adjust the frame types that are assigned to network adapters and assign network numbers. If you make any changes to the frame types, adapters, or network numbers, you have to restart the server for these changes to take effect. Before making any changes to the adapter and frame types, be sure that the changes will be compatible with your existing NetWare network.

You can configure both network numbers and internal network numbers. You should assign an internal network number even if the server has a single network card with a single frame type. The server's internal network number must be a unique network number across the internetwork.

If each of the server's network cards has just one frame type, you can have File and Print Services for NetWare automatically detect and configure the frame type for each card. However, if you have multiple frame types on a network, you should explicitly set the frame types to ensure the network works correctly. You should also be sure to explicitly set frame types if you have different network segments that never communicate with each other (such as one segment using EtherNet 802.2 and another using 802.3), or if network numbers are not clearly assigned and constant on your network.

You can also attach frame types to specific adapters, or multiple frame types to a single adapter. The adapters and frame types determine how Windows NT Server will communicate with the NetWare network. For each entry in the list of adapter cards and frame types, you must have individual, nonzero network numbers. If you don't assign a network number to a particular combination of network card and frame type, the default of 00000000 is assigned, and File and Print Services for NetWare will detect the appropriate network number.

Be sure to remember to set frame types and network numbers for each network card in the server.

For instructions on how to do this task, see the online Help topic “Configuring NWLink for FPNW.”

Configuring Startup

By default, File and Print Services for NetWare is configured to start automatically when the server starts. A supervisor can change the service to start only when needed.

You may want to do this when you install File and Print Services for NetWare on a domain's primary domain controller only to enable the domain controllers in that domain to authenticate the logon requests of NetWare-enabled users, and do not plan to have that primary domain controller share resources directly to NetWare client users.

For instructions on how to do this task, see the Help topic “Configuring Startup.”

Changing the FPNW Service Account Password

The FPNW Service Account is a user account that the FPNW Service uses to log on to each computer on which it is installed. All the actions taken by File and Print Services for NetWare happen under the context of the FPNW Service Account.

Generally, you should not have to change the password of this account. However, if you notice that the password for the account has become out of sync, you should change it. If it is necessary to change the password for the FPNW Service Account, you must complete the following tasks:

Use User Manager for Domains to change the account password once for the entire domain.

At each domain server that runs File and Print Services for NetWare, change the password the local service uses to log on. This password must match the password you set for the account in the domain.

For instructions on how to do this task, see the Help topic “Changing the FPNW Service Account Password.”

END BREAK

Installing the File and Print Services for NetWare Administrative Tools

You can install the File and Print Services for NetWare administrative tools at any computer running Windows NT Workstation or Windows NT Server. You can then use this computer to remotely administer servers running File and Print Services for NetWare.

Installing the administrative tools on the backup domain controllers in a domain also allows those servers to authenticate logon requests from NetWare-enabled users (as long as the File and Print Services for NetWare utility is installed on the domain's primary domain controller). For example, suppose that some servers in the Accounting domain run File and Print Services for NetWare, and the Accounting domain trusts the MIS domain. If you install File and Print Services for NetWare on the MIS primary domain controller, and install the File and Print Services for NetWare administrative tools on all the MIS backup domain controllers, you can then make any user account in the MIS domain NetWare-enabled, and give it access to resources shared by File and Print Services for NetWare in the Accounting domain.

Installing the administrative tools installs the extended User Manager for Domains, Print Manager, and Server Manager.

Note

When you administer File and Print Services for NetWare remotely from a workstation not in the same domain as the server you are administering, you must create a connection to a resource on the File and Print Services for NetWare server before you can administer the server.

Version 4.0

To install the File and Print Services for NetWare 4.0 administrative tools on a computer running Windows NT Workstation 4.0 or Windows NT Server 4.0

1. Double-click My Computer, then double-click Control Panel.

2. Double-click Network.

3. Click the Services tab, then click Add.

4. Click Have Disk.

Important

If File and Print Services for NetWare Administrative Tools Only appears in the Network Service list, do not select it; instead, click Have Disk.

5. Insert the Services for NetWare compact disc in the computer's CD-ROM drive.

6. Type the appropriate path, and click OK.

7. Select File and Print Services for NetWare Administrative Tools Only, and click OK.

8. If the computer runs Windows NT Workstation, copy srvmgr.exe from the Windows NT Server 4.0 compact disc to the \systemroot\winnt directory of the computer.

You can now administer File and Print Services for NetWare on remote servers. You may want to add User Manager for Domains and Server Manager to your computer's Administrative Tools program group.

To add User Manager for Domains and Server Manager to your workstation's Administrative Tools program group

1. Click Start, point to Settings, then click Taskbar.

2. Click the Start Menu Programs tab, then click Advanced.

3. In the left pane, double-click All Users, double-click Start Menu, double-click Programs, then double-click Administrative Tools.

4. On the File menu, click New, then click Shortcut.

5. Type usrmgr, then click Next.

6. Type User Manager for Domains, then click Finish.

7. Repeat steps 4-6, this type typing srvmgr in step 5 and Server Manager in step 6.

Version 3.51

To install the File and Print Services for NetWare version 3.51 administrative tools on a computer running Windows NT Workstation 3.51 or Windows NT Server 3.51

1. Double-click the Network icon in Control Panel.

2. Click Add Software.

3. Select <Other> from the bottom of the list of available software, and then click Continue.

4. Insert the File and Print Services for NetWare CD-ROM into your CD-ROM drive.

5. Type the appropriate path, and click OK.

6. Select File and Print Services for NetWare Administrative Tools Only, and then click OK.

7. If the computer runs Windows NT Workstation, copy srvmgr.exe from a Windows NT Server 4.0 compact disc to the \systemroot\winnt directory of the computer.

You can now administer File and Print Services for NetWare on remote servers. You may want to add User Manager for Domains and Server Manager to your computer's Administrative Tools program group.

To add User Manager for Domains and Server Manager to your workstation's Administrative Tools program group

1. In File Manager, open Administrative Tools.

2. From the File menu, click New.

3. Click Program Item.

4. Under Description type User Manager for Domains, and under Command Line type usrmgr.exe. Then click OK.

5. Repeat steps 2 through 4, this time typing Server Manager under Description, and srvmgr.exe under Command Line.

Installing the Online Administrator's Guide

Services for NetWare includes an online version of the Administrator's Guide. For instructions on installing this online manual, see the Services for NetWare release notes.

Managing Printers

With File and Print Services for NetWare, you can enhance printing interoperability on your network in the following ways:

You can enable NetWare client computers to print on printers attached to or controlled by servers running Windows NT Server.

You can use a Windows NT Server computer to manage printers previously managed by NetWare print servers. This can include printers cabled to computers acting as NetWare print servers and printers attached directly to the network through network print server devices.

Once you are using a Windows NT Server computer to manage a printer previously managed by NetWare, users of Microsoft client computers (such as those running Windows NT Workstation, Windows 95, and LAN Manager) can then send print jobs to that printer.

This section provides information about using File and Print Services for NetWare to share printers. The following topics are included in this section:

Making Windows NT Server printers available to NetWare clients

Using Windows NT Server to manage NetWare printers, and make those printers available to users of Microsoft client computers

Managing printers shared by File and Print Services for NetWare

Overview

The following sections discuss these topics:

An overview of Windows NT Server printing and printing terminology

How you can use File and Print Services for NetWare to enhance your network printing

Windows NT Server Printing

When using a Windows NT Server computer, the word printer can have two meanings. A printer can be a physical printer (the actual printer hardware); this is also called a print device. A printer can also mean a logical printer, a software interface between Windows NT Server and a print device. A logical printer is a software representation of a physical print device.

A logical printer can represent either a physical printer cabled directly to an LPT or COM port on the server, or it can represent a printer physically located elsewhere on the network.

Because Windows NT Server uses logical printers as representations of physical devices, you have flexibility when configuring your printers. You can create more than one printer representing the same physical printer, or you can create a printer that prints to a file. For example, if you have a single-print device cabled to your computer, you can create a logical printer for yourself that is not shared over the network and a second logical printer that is shared. Both printers send print jobs to your one physical printer. You can then set a lower priority for the shared printer, ensuring that the jobs you send to your higher-priority printer are printed first.

Controlling access to a shared printer is simple. You set permissions on it, specifying exactly who can administer the printer, and who can send print jobs to the printer.

Using File and Print Services for NetWare

When you create and share a logical printer on a server running File and Print Services for NetWare, you can make the printer available to users of both Microsoft client software and NetWare client software.

If you have a printer physically cabled to a server running Windows NT Server (also called a local printer), you make the printer available to both Microsoft client users and NetWare client users by creating a logical printer and sharing the printer. To access the printer, NetWare clients use the printer name you set when you create the printer. (A NetWare client specifies the printer's printer name in the queue option in the capture utility.) Microsoft clients, however, use the printer's share name to access it.

For network-connected printers controlled by Windows NT Server over the datalink control (DLC) protocol, you follow the same instructions as in the preceding paragraph. Network-connected printers are printers connected directly to network cable (such as the Hewlett-Packard® JetDirect printer). NetWare clients can use these printers the same way as they use printers cabled to the Windows NT Server computer-by specifying the printer's printer name as the queue name in the capture utility.

If you have printers controlled by NetWare print servers, you can make these printers available to Microsoft client users. To do so, you create a logical printer to represent the NetWare printer, and assign that logical printer to a special printer port. These special printer ports are named NetWareCompatiblePServern where n is a number.

Note

Whenever you create a logical printer to represent a NetWare printer, you should assign it to a NetWareCompatiblePServern port that is not currently assigned to any other printer. If you need to make more NetWareCompatiblePServern ports available, increase the value of the PServerPorts key in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FPNW
\Parameters key of the Registry. For more information, see Appendix A, “Configuring Registry Information.”

BEGIN BREAK

By default, there are two of these ports, but if you need more you can configure a Registry setting.

Then, to associate NetWare print servers, attached printers, and print queues to the Windows NT Server printer, use the Print Servers command on the FPNW menu in the Server Manager utility.

As illustrated in the following figure, with File and Print Services for NetWare, print jobs submitted by either a Microsoft client or NetWare client can be serviced by printers attached to the Windows NT Server computer or attached directly to the network, or attached to NetWare print servers.

With File and Print Services for NetWare, Microsoft clients and NetWare clients can use both Windows NT Server printers and NetWare printers.

Note

For certain NetWare utilities to be used to print files to printers managed by a server, the MaxUsers setting in the HKEY_LOCAL_MACHINE\SYSTEM
\CurrentControlSet\Services\NcpServer\Parameters key of the server's Registry must be set to 250 or less.

Installing, Sharing, and Managing a Windows NT Server Printer

To install a printer to be controlled by a Windows NT Server computer running File and Print Services for NetWare, use the Add Printer wizard, just as if you were installing the printer on any Windows NT Server computer. (Access the Add Printer wizard by double-clicking My Computer, and then double-clicking Printers.)You must be logged on as an administrator or Print Server Operator in order to install, share, and manage printers.

When you install a printer, the information you provide includes the printer name, driver, and an optional description. Then you specify a printing destination. The destination can be a port, a file, or a network address. You are prompted to select the appropriate printer driver or to install a new one if necessary.

Microsoft clients then refer to the printer by the share name, while NetWare clients refer to it by its printer name. NetWare clients specify the printer name as the queue name when using the capture utility. The following example associates the NetWare client's LPT2: port with a Windows NT Server printer with the printer name of LASER.

capture /l=2 /q=laser

Note

When a NetWare client requests that a banner be used, the Windows NT local printer substitutes a separator page if a separator page has been defined for the local printer object. Separator pages are assigned on a per queue basis, which is different from NetWare banners, which are assigned on a per job basis.

Also, when the order of print jobs is changed for a Windows NT Server printer, it might take up to one minute before the NetWare clients see the new order of the print jobs.

Using File and Print Services for NetWare with NetWare Printers

With File and Print Services for NetWare, you can use a Windows NT Server computer to manage the following types of NetWare printers:

Printers cabled to computers functioning as NetWare print servers.

Printers attached directly to the network, including both printers that contain a network card, and printers connected by the use of third-party print server devices.

When you set up one of these printers, both NetWare clients and Microsoft clients can access the printer.

Using Print Server on the FPNW menu in Server Manager, you can:

Set up print servers that are serviced by FPNW.

View, add, and remove printers.

Change the password for the print server.

Change the file servers that are serviced by the print server.

For each printer that is serviced by a print server, you can:

Configure the printer.

Determine which users will be notified of a printer error.

Configure which print queues the print device will service.

BEGIN BREAK

END BREAK

Setting Up NetWare Printers

To set up NetWare printers using Windows NT Server, you follow this overall process:

To set up a NetWare printer for management by File and Print Services for NetWare

1. Use the Add Printer wizard to create a logical printer, assigning it to a NetWareCompatiblePServern port and/or a local port.

2. Use Print Server on the FPNW menu in Server Manager to add the print server.

3. Use Print Server to add the printer to the print server.

4. Use Print Server to add the print queue to the print server. The queue you select here is the logical printer you created in step 1, with the Add Printer wizard.

For most NetWare printers, including printers attached to a computer acting as a print server, you follow all of the steps in the following procedures. However, for other printers, such as printers attached directly to the network through print server devices and printers that contain network cards, you may need to use the utilities that are included with the print server device or printer to configure part of the printer setup. For more information, see “Considerations for Network-Attached Printers,” later in this section.

To use the Add Printer wizard to create a logical printer

1. On the Windows NT Server computer, double-click My Computer

2. Double-click Printers.

3. Double-click Add Printer.

4. Click My Computer, then click Next.

5. Select a check box for a NetWareCompatiblePServern port that is not already assigned to a printer, then click Next.

6. Follow the rest of the instructions in the wizard to create the logical printer. When the wizard prompts whether to share the printer, be sure to click Shared.

Note

If you need to make more NetWareCompatiblePServern ports available, increase the value of the PServerPorts key in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FPNW
\Parameters key of the Registry. For more information, see Appendix A, “Configuring Registry Information.”

To create a print server to serve the printer

1. From the FPNW menu in Server Manager, click Print Server.

If you used a third-party utility to create the print server, and this print server already appears in the list in the Print Servers for dialog box, then skip to the next section, “Adding Printers to the Print Server.” Otherwise, follow the rest of the steps in this procedure.

2. In the Print Servers for dialog box, click Add.

3. In Print Server, type the print server name. This should be the name of the actual NetWare print server that is servicing the printer.

4. In Full Name, type a full description of the print server.

5. In Password, type the password for the print server; then type the same password in Confirm Password.

The passwords you type in Password and Confirm Password must be the same.

The passwords will be encrypted as you type, and asterisks (*) will appear in the boxes instead of letters or numbers.

6. Click OK.

Adding Printers to the Print Server

After you add the print server, you then add printers to be serviced by the print server.

To add printers attached to the print server

1. From the FPNW menu in Server Manager, click Print Servers.

2. From the Print Server list in the Print Servers for dialog box, click the print server where you want to add or view the printers, and then click Printers.

If you used a third-party utility to create the printer, and this printer already appears in the list in the Print Servers for dialog box, then skip to the next section, “Assigning Print Queues.” Otherwise, follow the rest of the steps in this procedure.

3. To add a printer to the print server, click Add.

4. In Printer, type the name of the printer you are attaching to the print server. This should match the name of the printer as known by the NetWare print server.

5. In Port, choose the number of the printer port.

Port contains the list of NetWare configurable printers.

6. In Type, choose the type of printer port, such as parallel, serial, or if the port is defined elsewhere. Then click OK to add the printer to the print server.

If you are adding a printer to multiple print servers, you can define the printer's parameters once; then use the Defined Elsewhere parameter under Type on subsequent print servers.

If you define the port to be a parallel port, you have the option to configure that port as follows:

Option	Description	Range	Default

Interrupts	The hardware setting.	Values are 3 through 7.	7
Buffer Size	Amount of memory in a printer's buffer.	Values are between 1K and 20K.	3K
Starting Form	Paper types used in printing.	Forms are assigned a number between 0 and 255.	0
Queue Service Mode	Determines how the printer handles different forms. There are four types as shown in the following table.	-	-

The four Queue service modes are shown in the following table:

Type	Description

Change forms as needed	The printer prints all jobs in the queue, changing print forms as required.
Minimize form changes within queues	The printer prints all jobs in a queue that have the same print form first. The jobs that require the current form prints first.
Service only currently mounted form	The printer prints only the jobs that require the current print form, beginning with the highest priority queue.
Minimize form changes across queues	The printer prints all jobs across all queues that have the same print form first. The queues are searched in order of priority.

BEGIN BREAK

END BREAK

If you are installing a serial port printer, you can also configure the following Serial Port options. Be sure these settings correspond with the printer settings.

Option	Description	Range	Default

Baud rate	The rate at which data travels across the wire. A higher baud rate means the data transmission is faster.	-	9600 bits per second (BPS)
Data bits	Specifies the number of bits used to form a character.	Values are between 5 and 8.	8
Parity	Specifies the method of error checking.	None, Even, or Odd	None
Use X-On / X-Off	Prevents the transmission of data at a speed faster than the receiving system can accept it. Use this parameter if your printer supports this option.	-	-

BEGIN BREAK

END BREAK

Print Queues

When you are assigning print queues to a printer, you can also set the priority of the queue. When setting up a printer for use with File and Print Services for NetWare, the print queue you assign to the print device is the logical printer you created on the server running Windows NT Server.

If you are setting up a network-attached printer and you used a third-party utility to assign the queue to the printer, you are finished configuring the printer. Otherwise, follow the steps in the following procedure.

To select the print queues that the printer will service

1. From the FPNW menu in Server Manager, click Print Servers.

2. Click the print server whose print queues you want to set, and then click Printers.

3. Under Printer, select the printer whose print queues you want to set, and then click Queues.

4. To add a queue, select it in Available Queues and click Add.

When setting up a NetWare printer for use with File and Print Services for NetWare, the queue you select here should be the logical printer you created using the Add Printer wizard.

5. To remove a queue, select it in Queue, and click Remove.

6. To set a queue's priority, select it and under Priority, type or select the priority number you want that queue to have.

The priority levels are 1 to 10, and 1 is the highest priority.

7. When you are finished, click OK.

BEGIN BREAK

END BREAK

Setting Up a Print Server to Service a Printer Queue on a Different File Server

Use the following procedure to set up a print server to service a printer queue located at another server. In this situation, either server can be running File and Print Services for NetWare.

1. On the server where the printer is physically located, create a printer queue.

2. On the other server, create a printer queue. If this server is running File and Print Services for NetWare, set the queue to print to a NetWareCompatiblePServerx port, and be sure to select Shared in the Add Printer wizard.

3. On each server, create a print server. These two print servers must have the same name.

4. On each server, add the other server as a file server to be serviced by the local print server.

5. On the server where the printer is physically located, create a printer. Set it to print to the port to which the printer is physically attached.

6. On the other server, create a printer, with the same name as the printer you created in step 5. Set the printer's type to Defined Elsewhere.

7. If you have made any changes to the print server software, unload the software and reload it.

Configuring Print Servers

After a print server has been installed, you can remove printers from the print server, change the print server name and password and the file servers that are serviced by the print server.

You can also remove a print server. When you remove a print server, users will no longer be able to print to printers serviced by the print server.

For instructions on configuring print servers, see the online Help.

Configuring Printers Serviced by Print Servers

After a printer has been added to a print server, you can change the printer's settings and specify the users that will be notified when a printer error occurred.

When you change the printer settings, you reconfigure those settings you made when you installed the printer. However, you cannot change the printer port. If you want to change the printer port, you will need to remove the printer and add it again, assigning it to a new port.

Considerations for Network-Attached Printers

File and Print Services for NetWare is compatible with network-ready printers as well as network print server devices, which are used to attach a printer directly to the network.

The following list shows what network-ready printers and print server devices have been tested with File and Print Services for NetWare as of press time, and discusses some special considerations you need to know when setting up these types of printers. For more information, see the documentation included with the printer or network print server device.

AXIS NPS 550

Castelle LANpress

Emulex NetJet Card

Extended Systems ESI2866A NetJet Card

Hewlett-Packard® JetDirect® (using IPX/SPX)

After you create a print queue for the printer, use the jetadmin utility (included with the printer) to assign a name to the printer and select the print queue.

Intel® NetPort®

After you create a print queue for the printer, use the npadmin utility (included with the network print server device) to set up the printer. You must also copy the EN.NPX file from the floppy disks included with the print server device to the LOGIN directory of the File and Print Services for NetWare server.

To use the npadmin utility, you must copy the following files to a public directory on your network, and run the utility from that directory:

NPADMIN.EXE
NPADMIN.HLP
NPADMIN.CWA
NPMONO.CWA
SERFLASH.EXE
README.TXT
NFLASH.NET
ENGLASH.SER

Managing File and Print Services for NetWare

To manage File and Print Services for NetWare, you use a few easy-to-use graphical user interface administrative tools, such as the FPNW option in Control Panel and the Properties command on the FPNW menu in Server Manager. With these tools, you can perform a variety of tasks including controlling user connections, managing volumes, and sending messages to users.

This section provides information about managing File and Print Services for NetWare as well as information on using the command-line utilities that are included in the package. The following topics are included in this section:

Managing File and Print Services for NetWare properties

Controlling user connections

Managing volumes

Sending messages

Using command-line utilities

BEGIN BREAK

END BREAK

Managing Properties

Administrators using File and Print Services for NetWare can specify the maximum number of connections to the server that users are allowed, control specific connections to files, and send messages to all users connected to the server. Additionally, an administrator can assign or change the home directory root path, define a default NetWare printer, and determine if the server will respond to find-nearest-server requests from NetWare clients.

Most of these functions are controlled by the FPNW option in Control Panel. Clicking FPNW displays the following dialog box.

To manage corresponding properties that apply to Microsoft client users, use Server Manager or the Server option in Control Panel.

File and Print Services for NetWare also supports performance monitoring and event logging. Use Performance Monitor and Event Viewer, located in the Administrative Tools program group, to perform these tasks.

Managing User Connections

Click Users in the File and Print Services for NetWare on [Server] dialog box to see NetWare client connections to the server and to specific files, disconnect users from the server, and send messages to all users connected to the server.

Click Users to disconnect current NetWare users from the server when it is appropriate. You might need to do this task when you are going to stop File and Print Services for NetWare, or shut down the entire server. To avoid data loss, always warn users before disconnecting them from the server. For more information about sending messages, see “Sending Messages to Connected Users,” later in this section.

Managing Volumes

Click Volumes in the File and Print Services for NetWare on [Server] dialog box to view the volumes shared by the server and the users connected to the volumes, and to disconnect users from volumes.

Click Volumes to disconnect current NetWare users from the server when it is appropriate. (This disconnects the user from the entire server, not just the volume selected.)You might need to do this task when you want to allow another user to connect to a volume that already has its maximum number of users connected. To avoid data loss, always warn users before disconnecting them from the server. For more information about sending messages, see the section “Sending Messages to Connected Users,” later in this section.

Note

Disconnecting NetWare MS-DOS® clients from the server might cause the MS-DOS client computer to stop responding.

Managing Open Files

Click Files in the File and Print Services for NetWare on [Server] dialog box to view the server files opened by NetWare clients and to close files when necessary. To avoid data loss, always warn connected users before closing resources.

Sending Messages to Connected Users

You can send messages to selected users or to all users.

To send messages to selected users, use the FPNW icon in Control Panel. To send messages to all users, use the Send Message command on the NetWare menu in Server Manager.

For instructions on how to perform these tasks, see “Sending a Message to Selected Users” and “Sending a Message to All Connected Users” in the online Help.

Command-Line Utilities

File and Print Services for NetWare includes several commonly used utilities that NetWare client users can run at the system prompt. File and Print Services for NetWare also uses a new parameter for the Windows NT net user command.

Utilities

Using the utilities provided, NetWare clients can perform basic network operations, such as logging in and out and using network resources. If you have NetWare utilities installed on a NetWare server, you can also remotely use these utilities.

The following table lists the utilities provided with File and Print Services for NetWare. The command formats for these utilities are described in the following sections.

To	Use these commands

Log in or log out	login, chgpass, setpass, attach, logout
Use network resources	map, slist
Use printing resources	capture, endcap

Attach Command

Use the attach command to log in to another server (running either NetWare or Windows NT Server with File and Print Services for NetWare) while remaining logged in to the current server. If you do not specify the server name and user name in the command, you are prompted to enter these names. If a password is required, you are prompted to enter it.

You must be logged in to a server before you can use the attach command to log in to additional servers. Although the attach command connects you to a server, it does not create a drive mapping to that server. However, once attached, you can make drive mappings to that server without supplying your password.

Syntax: attach [server[/name]]

Where:

server is the name of the server in which you want to attach.

name is the user name you want to use on that server.

For example, a NetWare client user named ChrisDr, to log on to a server names JUPITER, would enter the following command at the system prompt:

attach jupiter /chrisdr

Capture Command

Use the capture command to view print queues and printers, redirect a print job to another print queue, print from an application without exiting the application, and print multiple copies of a print job.

Syntax: capture [option]

Where:

option is one of the following options:

Option	Description

autoendcap	Lets you send a job to a network printer or to a network file when you exit or enter an application. The autoendcap option is useful if you want to save several different screens or files from the same application to the same network file. The autoendcap option does not automatically end the capture of an LPT port, as its name implies. The default is enabled.
banner = name	Specifies the text that appears on the lower part of a banner page. Replace name with any word or phrase up to 12 characters. The default is your user name and the print job filename.
copies = n	Specifies how many copies you want to print. Replace n with a number from 1 to 999. The default is 1.
create = path	Creates the file in which you want to store the data. If you want to save the file in your default or current directory, replace path with the name of the file you want to create. You must use a network drive with the create option to specify where you want to store the file (server, directory, volume, and filename).

BEGIN BREAK

END BREAK

Option	Description

form= path or n	Specifies the form on which to print the job. Replace form with the name of the form, or replace n with number of the form.
formfeed	Enables the formfeed after your print job has been printed. When formfeed is enabled, the printer prints the next job at the top of the next sheet of paper. However, if an application automatically enables formfeed, using this option causes an extra blank page to be fed through the printer. The default is enabled.
keep	Keeps all data at the server if your workstation freezes or loses power while you are transferring data to the server. If your workstation does freeze or stop (that is, loses its connection to the server), the server will also send the data it received from your workstation to a print queue for printing. If you plan on capturing data over several hours, use this option. If you don't include the keep option and your workstation stops during the capture, the server discards the data it has received.
local = n	Specifies which LPT (local printing port) to capture. Replace n with 1, 2, or 3. The default is LPT1.
name = name	Specifies the text that appears on the upper part of the banner page. Replace name with any word or phrase up to 12 characters. The default is your user name.
noautoendcap	Prevents data from being sent to a network printer or a file when you enter or exit an application. The default is disabled.
nobanner	Specifies that no banner page should be printed.
noformfeed	Disables formfeed at the printer. The default is disabled.
nonotify	When set, you are not sent a notification that your job has printed. You need to use this option only if notify is enabled in your print job configuration and you want to disable it. The default is enabled.
notabs	Ensures that all the tab characters in your print job arrive at the printer unchanged. Use this option if your application can format the print job, or if you have problems printing graphics.
notify	Notifies you when your job has been printed. This option does not notify you if the printer has a problem or if your job cannot be printed. The default is disabled.

BEGIN BREAK

END BREAK

Option	Description

queue = queue	Specifies which queue the print job should be sent. If multiple queues are mapped to a printer, you must include this option to select a queue. Replace queue with the name of a queue. The default is the queue in which spooler 0 has been assigned.
server = server	Specifies which server the print job should be sent. The default is your current server.
show	Displays the current status of LPT ports: Whether they are captured Whether they are set to send data to a network printer or to a file How capture options are set Using the show option does not affect the capture of an LPT port. You cannot use show with other capture options.
tabs = n	Use this option if your application can't format the print job. Replace n with a number from 0 to 18. The number you specify indicates the number of characters in one tab stop. The default is 8.
timeout = n	The timeout option sends data to the printer a specified number of seconds after the application last writes to a file. It allows you to print from an application without exiting the application. Replace n with a number from 1 to 1,000. If the timeout option is set too low, you might have problems printing some files, especially files with graphics. Increase the timeout option if only parts of files are being printed or if the files do not print at all. The default is 0, disabled.

Chgpass Command

Use chgpass to create or change a File and Print Services for NetWare password (and a regular account password) on one or more servers running Windows NT Server, File and Print Services for NetWare, or NetWare. This command is identical to setpass. You can also synchronize passwords on multiple servers. You must be attached to a NetWare server before you can set or change your password on it. If you are attached to more than one server with the same password, this command sets the passwords to be the same on all the servers (both Windows NT Server and NetWare) to which you are logged in.

BEGIN BREAK

END BREAK

A password can contain up to 127 characters but cannot include control characters, which are the first 32 characters in the ASCII character set. Chgpass does not support extended characters in passwords. The following syntax should be used:

chgpass [server] [/username]

where server is the name of the server on which you want to set or change your password. The current server is the default; and /username is the name of the user whose password you want to set or change. The current user name is the default.

Endcap Command

Use endcap to end the capture of one or more of your client computer's LPT ports (local parallel printing ports). You can also use endcap to send data to a local File and Print Services for NetWare or NetWare network printer or a file. You always use capture before using endcap. If you do not specify an option, endcap ends the capture of the LPT1 port. Here is the sample syntax:

endcap [option]

Where:

option is one of the following options:

Option	Description

all	Ends the capture of all LPT ports with one endcap command.
cancel	Ends the capture of the LPT1 port and discards any data without printing it.
cancelall	Ends the capture of all LPT ports and discards any data without printing it.
cancellocal = n	Ends the capture of the specified LPT port and discards any data without printing it. Replace n with 1, 2, or 3.
local = n	Ends the capture of the specified LPT port. Replace n with 1, 2, or 3.

BEGIN BREAK

END BREAK

Login Command

Use the login command to start your login script for a particular server and gain access to that server's resources. A user's access to a server's resources is always limited by the user's rights on that server. Whenever you type a login command, you not only log in to the specified file server, but you also automatically log out of any servers to which you were attached before you typed the login command. If your password has expired, you are prompted to change your password before logging out. The system login script is stored in the SYSVOL\PUBLIC\Net$log.dat file.

Syntax: login [server[/name]] [/clearscreen] [/noattach] [/script path]

where

server is the name of the server to which you want to log in.

name is the user name in which you want to log in.

/clearscreen clears the workstation screen as soon as you enter your password.

/noattach starts the login script you specify in the script option without logging out of your current server or attaching to a new server.

/script overrides the system and personal login scripts with the login script you specify as path. The path must be the complete path specification.

Logout Command

Use the logout command to log off from one or all servers to which you are attached. When you log out of a server, you terminate your access to that server and all of your temporary drive mappings to that server are lost.

Syntax: logout [server]

where

server is the name of the server from which you want to log off.

BEGIN BREAK

END BREAK

Map Command

Use the map command to view current drive mappings, create or change network drive mappings, create or change search drive mappings, map a drive to a fake root directory, and map the next available drive.

Drive mappings are temporary and are deleted when you log out or turn off your workstation. Drives mapped to fake root directories are also deleted. You can save drive mappings, including fake root mappings in your login script if you want them to be used each time you log in. If you map a local drive to a network directory path, you are prompted to assign the drive letter to a network drive.

Syntax:

To view current drive mappings, type:

map [drive:]

To create or change network drive mappings, type:

map path

map drive: = [drive: | path]

map [option] drive:

To create or change search drive mappings, type:

map [option] drive: = [drive:path]

To map a drive to a fake root directory, type:

map [root] drive:= [drive: | path]

where

drive is the drive letter mapped to the directory you want to work with.

path is the directory path you want to work with.

root maps the drive to a fake root directory.

option is one of the following options:

Option	Description

delete	Deletes a default, network, or search drive mapping.
insert	Changes search drive mappings.
next	Maps the next available drive to a specified path.
remove	Deletes a default, network, or search drive mapping.

Setpass Command

Identical to chgpass; see “Chgpass Command” earlier in this section for more information.

Slist Command

Use the slist command to view a list of the servers running either NetWare or File and Print Services for NetWare.

Syntax: slist [server] [/continue]

where

server is the name of the file server whose information you want to view. You can use wildcard characters, such as the question mark (?) or the asterisk (*), to view a group of file servers.

/continue displays the list of file servers in a continuous screen without stopping.

Net User Command

File and Print Services for NetWare uses a new parameter for the Windows NT net user command. The new parameter allows an administrator to make an account NetWare-enabled. You can use the net user command to add a new NetWare-enabled account, make an existing account NetWare-enabled, or disable an existing NetWare account.

The new command syntax for adding a NetWare-enabled account using the net user command is as follows:

net user username [password | *] /fpnw[:yes | no]

If no password is specified, you are prompted to supply one. Once an account is NetWare-enabled and you change the account password with net user, both the Windows NT and NetWare network passwords are changed.

If you use the /fpnw parameter without a yes or no argument, the account is NetWare-enabled (default is yes). If you use the no argument, the account is NetWare-disabled.

For example, if you want to add a user that has a NetWare-enabled account, type the following command at the command prompt. You are prompted to enter a password.

net user joes /add /FPNW

To disable the use of NetWare for an existing account, type the following command:

net user chrisjo /FPNW:no

BEGIN BREAK

END BREAK

Digital NetPrint/100

This print server device supports only Ethernet frame type 802.3.

Xircom Pocket Adapter

After you create a print queue for the printer, use the psetup utility (included with the network print server device) to set up, assign a name to the print device, and assign it to a queue. Also, this device supports only Ethernet frame type 802.3.

Milan Fastport 3100

This device supports only Ethernet frame type 802.3.

Appendix A

File and Print Services for NetWare Registry Parameters

The configuration Registry stores values that define the working environment for the Windows NT operating system and any services installed on the Windows NT Server computer. Usually, to change these values, you use graphical tools, such as Control Panel and Windows NT Setup. Windows NT Server also includes a utility, the Registry Editor (Regedt32.exe), which you can use to inspect and modify the configuration Registry directly.

Before you modify the Registry, it is strongly recommended that you read the Registry sections of the Windows NT Workstation Resource Guide (found in the Microsoft Windows NT Workstation Resource Kit).

Caution

Using the Registry Editor to edit entries in the Registry is equivalent to editing raw sectors on a hard disk. If you make mistakes, your computer's configuration could be damaged. You should edit Registry entries only for settings that you cannot adjust using the user interface, and you should use extreme care when doing so.

The parameters listed in the following sections are used by File and Print Services for NetWare. They are located in the Registry subtree HKEY_LOCAL_MACHINE\SYSTEM
\CurrentControlSet\Services\FPNW\Parameters

Installed File and Print Services for NetWare Parameters

The following parameters are installed in the Registry when File and Print Services for NetWare is installed on a Windows NT Server computer. The parameters can be modified.

AlertEveryoneOnDiskFull = REG_DWORD 0x00000001

Controls whether an alert message saying the disk is full is sent to all NetWare clients currently attached to the server, or just to users who are attached and are members of the Administrators group. Values are 0 and 1; the default is 1 (to alert all users).

Description = REG_SZ "Description"

This string is the description for the server and is shown in the File and Print Services for NetWare properties dialog. NetWare clients do not see this string and it is not used except to display the server name.

EnableBurst = REG_DWORD 0x00000001

Enables and disables packet burst. If the value is 1, packet burst is enabled. If the value is 0, packet burst is disabled. The default is 1.

EnableForcedLogoff = REG_DWORD 0x00000001

Enables forcing NetWare clients off when their account time-out is reached. If set to 1, the client is forced off. If set to 0, only a warning is sent to the user, who won't be forced off. The default is 1.

EnableLip = REG_DWORD

Enables large internet packet (LIP) negotiation. This parameter has no affect if the EnableBurst value is 0. Values are 0 and 1. The default is 1 for LIP enabled.

HomeBaseDirectory: REG_SZ

The default path where users' home directories are stored. The default is SYS:.

LoginDirectory = REG_SZ

Points to the directory that NetWare clients connect to when they connect to the server but are not yet logged in. If this parameter is not present, NetWare client users will not be able to log in if they are attached to the server. The login directory should exist and at a minimum have a copy of Login.exe and Slist.exe (these are installed when File and Print Services for NetWare is installed). It can be any valid value and is specified as a volume:path\subpath. The default is SYS:LOGIN.

MaxReceivePacketSize = REG_DWORD

The receive buffer size. The server cannot receive a message larger than this size from a NetWare client. It defaults to the value that the IPX transport returns as the largest packet size for the network. The default value is the maximum. The minimum value is 512K. If 0 is specified, the default is used. It is recommended that this setting not be changed since the default is the maximum. However, it's possible in some situations, such as mixed token ring/Ethernet configurations, that this value may be changed, since nonpaged memory is wasted if this is set larger than the largest packet size for the network.

MaxSearchesPerClient = REG_DWORD

Defines the maximum number of outstanding directory searches a NetWare client can have open concurrently. The minimum value is 32. The default is 128. There is no maximum, but be aware that this parameter takes up memory and is only reused when the table is full.

MaxUsers = REG_DWORD

Controls the maximum number of NetWare clients that can be connected to the server. The default value of 1000 is the maximum. A value of 0 means use the default. (Note that this value must be 250 or smaller for certain NetWare utilities to be used to print files to printers managed by the server.)

NumberOfWatchDogPackets = REG_DWORD

The number of watchdog packets the server sends to the NetWare client before the connection is closed, if the watchdog packets go unanswered. If no value is specified, a value of 5 is used. The minimum value is 1. There is no maximum value.

PServerPorts = REG_DWORD

The number of logical print server ports (named NetWareCompatiblePServern), provided in Print Manager to represent NetWare printers. You may want to raise this if you are creating many print queues on the server to send jobs to NetWare printers. The range is 1 to 64, and the default is 2.

RespondToNearestServer = REG_DWORD

Disables responding to the Get Nearest Server request from NetWare clients on the local network wire. If this value is set to 0, users on the same wire as the server connect to other servers rather than the local server if they don't have a preferred server set. This parameter has no effect for users on other network wires. Values are 1 (respond as normal) and 0 (don't respond). The default is 1.

Size = REG_DWORD

Specifies, in general terms, the workload the server can expect. It establishes the maximum number of receive buffers to allocate, the initial number of receive buffers to allocate, and the number of worker threads to allocate. Possible values are 1 (minimize memory usage), 2 (balance memory with performance), and 3 (maximize performance ). The default is 3.

WatchDogInitialDelay = REG_DWORD

Specifies the number of seconds the server waits before sending a NetWare client a watchdog keep-alive request. The minimum value is 15 seconds. If no value is specified, the default is 300 seconds (5 minutes). It is recommended that you not disable this parameter. There is no maximum value.

WatchDogSecondaryDelay = REG_DWORD

The number of seconds the server waits between sending watchdog packets to a NetWare client. If no value is specified, the default is 60 seconds. The minimum value is 10 seconds. There is no maximum value.

Parameters Available but Not Installed

The following parameters can be added to the Registry but are not automatically installed when File and Print Services for NetWare is installed on a Windows NT Server computer.

AllowableBadSequencePkts = REG_DWORD

The maximum number of bad packets that File and Print Services for NetWare will receive from a particular NetWare client before it closes the connection from that client. Closing such connections protects the server against security attacks. The range is 0 to -1 (unlimited), and the default is 10.

BlockingWorkerThreads = REG_DWORD

Specifies the number of threads set aside by File and Print Services for NetWare to service requests that can block the thread for a significant amount of time. Larger values can increase performance but use more memory. A value that is too large can impede performance by causing excessive task switching. The range is 1 to 64, and the default depends on the configuration of the server.

CacheEntryTimeout = REG_DWORD

Specifies the length of time, in minutes, before an unreferenced cache entry is closed. The default time is five minutes, the valid range is one to ten minutes.

ClearTextPasswords = REG_DWORD

Specifies whether File and Print Services for NetWare will accept clear text passwords from clients. The allowable values are 0 (never accepted), 1 (accepted for PServers only), and 2 (accepted for all uses). The default is 1.

CoreCacheBuffers = REG_DWORD

Extra buffers (separate from the Windows NT Server cache manage) used to cache small sequential reads and writes. The range is 0 to 1024 buffers, the default depends on the server's configuration.

CoreCacheBufferSize = REG_DWORD

The size, in bytes, of the buffers specified in CoreCacheBuffers. The allowable values are 0, 4096, and 8192. The default is the size of a single page, which depends on the server's architecture (x86, MIPS®-based, Alpha AXP™-based, or PowerPC®-based).

DefaultBannerFileName = REG_DWORD

The full path of the banner file to be used when NetWare clients send print jobs without specifying a banner file. There is no default.

DefaultQueueName = REG_SZ

The print queue to be used when NetWare clients send print jobs to the server without specifying a print queue. Do not set this value directly in the Registry; instead, use the FPNW icon in Control Panel.

DisableWriteCacheCriteria = REG_DWORD

If the available disk space (in kilobytes) on the server falls below this amount, File and Print Services for NetWare will stop caching writes. The range is 0 to -1 (unlimited), and 1024K is the default.

DiskFullCriteria = REG_DWORD

Specifies (in 1K increments) the point at which an alert saying the disk is full is sent to administrators or all users. The minimum is 0; there is no maximum. The default is 10K.

EmulateNtfsShareable = REG_DWORD

Enables per-file Shareable options to be set. Valid values are 0 and 1.

If set to 0, or on volumes that do not use NTFS, volume-wide shareable processing as specified by EmulateShareableFlag is used.

If set to 1, users can set the Shareable flag on a per file basis on NTFS volumes. For files marked with the Shareable flag set, logic similar to that used in NCPSRV_COMPATIBILITYOPEN_DENYNONE is used when clients open the specified file. If a file is marked as not Shareable, logic similar to that used in NCPSRV_COMPATIBILITYOPEN_EXCLUSIVE is used when a client opens the file.

EmulateShareableFlag = REG_DWORD 0x

Affects how FPNW grants access to files that are requested for exclusive access. Valid values are 1-3. Meanings of these values are listed below:

NCPSRV_COMPATIBILITYOPEN_DENYNONE (1)

All requests for read-only exclusive are mapped to read/write deny none. If the same client later opens the file for write, the same handle is used. FPNW ensures that only one client at a time has the file open for write. Allows VLM and NETx clients to run programs concurrently, and enables setup programs that open the file for write when they already have it open exclusively for read. However, Microsoft clients or local clients can modify the file without FPNW knowing about it since FPNW only has it open as read/write deny none; also, clients using a file for synchronization or clients that must have the file exclusively may encounter difficulty. This option is recommended only for users who are sure they don't have applications that will experience problems with this mode. This value is equivalent to the Shareable bit being set on a NetWare server.

NCPSRV_COMPATIBILITYOPEN_DENYWRITE (2)

This is the default mode. In this mode, all requests for read-only exclusive are translated to read deny write. This enables all MS-DOS programs to be loaded concurrently from multiple clients. However, requests for write exclusive cannot be folded into existing read-inclusive requests, so some setup programs fail in this mode.

NCPSRV_COMPATIBILITYOPEN_EXCLUSIVE (3)

This is the strictest option. When clients request exclusive use of a file, they get exclusive use. VLM and NETx clients cannot load the same executable files at the same time since one of them will have it open exclusively. The file is opened read/write exclusive even if the client requests read exclusive. This mode usually causes the most errors, but it is the only way to enable some applications to function. This value is equivalent to the Shareable bit being not set on a NetWare server.

If a value of 0 is specified (or if no value is specified), the server defaults to DenyWrite (2).

EnablePassthrough = REG_DWORD

Specifies whether File and Print Services for NetWare will accept pass-through authentication requests from Windows 95 NCP servers. The default is Yes.

EnforceNetWareSecurity = REG_DWORD

Specifies whether File and Print Services for NetWare enforces security on requests to read the entries in the server's print queues. False specifies that security is not enforced and all users can read the queue entries; True specifies that security is enforced. The default is False.

FilterNWUsers = REG_DWORD

Specifies whether File and Print Services for NetWare, when receiving a request to enumerate the server's users, lists all users or only NetWare-enabled users. The default is False, which enumerates all users.

FormsHashTableSize = REG_DWORD

Specifies the number of slots in the forms hash table. The average number of entries searched while looking for a form can be calculated as follows:

(NF / HTS) /2

where NF is the number of forms on the computer and HTS is the number of slots in the forms hash table. The default value is 20 slots, and the valid range is 10 to 40.

FPNW\PServerPort = REG_DWORD

Used by the NWMon print monitor to determine the number of jobs that may simultaneously be serviced by NetWare PServers. This parameters may be incremented if there are several PServers, or if the PServers service several printers. For busy queues, this should not exceed one port per PServer printer. The default value for this is two ports; the maximum is 16 ports.

InitialReceiveBuffers = REG_DWORD

Sets the number of receive buffers initially allocated and the minimum number of receive buffers the server will keep allocated. These are only freed when the server is unloaded. Defaults for size = 1,2,3 are 2,20,40. The minimum is the default value. The maximum value is the value of MaxReceiveBuffers.

JobInfoAllocHint = REG_DWORD

The base allocation size used when obtaining job information from WinSpool. This size is adjusted as the server is running to indicate the largest allocation required. The default value is 1024 bytes, and the valid range is sizeof(JOB_INFO_2) to 2048.

LockRetryCount = REG_DWORD

Specifies the number of times File and Print Services for NetWare retries an open on a file if the result of the open is that the file is in use. The range is 0 to 100, and the default is 5.

LogFormNameChanges = REG_DWORD

If LogFormNameChanges is set to anything but 0, the server will log the form name as it is available to the NetWare client. Most Windows NT form names do not conform to the NetWare client constraints and must be adjusted. The event log string is as follows: The Windows NT form name name is available to NetWare users as new name. The name was changed because of NetWare naming constraints.

LogPrinterNameChanges = REG_DWORD

If LogPrinterNameChanges DWORD is set to anything but 0, the server will log the printer share name as it is available to the NetWare client. Most Windows NT printer share names do not conform to the NetWare client constraints, and must be adjusted. The event log string is as follows: The Windows NT printer share name name is available to NetWare users as new name. The name was changed because of NetWare naming constraints.

LowVolumeThreshold = REG_DWORD

Specifies (in percentage of disk space) the point at which a warning is sent out to administrators or all users that the disk is close to reaching capacity. The minimum is 0; the maximum is 100. The default is 10.

MaxCachedOpenFiles = REG_DWORD

The maximum number of files that File and Print Services for NetWare keeps open per client (under certain circumstances), when the client sends a close request. The range is 0 to -1 (unlimited), and the default is 4.

MaxReceiveBuffers = REG_DWORD

The maximum number of receive buffers the server will keep allocated. The server may go over the limit for short times when processing burst requests but will immediately free the excess buffers. Defaults for size = 1,2,3 are 64,128,256. The minimum is 10. There is no maximum, but keep in mind this is a nonpaged pool.

MaxWorkItemIdleTime = REG_DWORD

Specifies the amount of time (in seconds) that a work item (receive buffer) can stay on the idle queue before it is freed.(However, the number of receive buffers is never allowed to fall below the minimum specified by the MinFreeWorkItems parameter. The range is 0 to -1 (unlimited), and default is 300 seconds.

MaximumFreeJBCs = REG_DWORD

MaximumFreeSJEs = REG_DWORD

MaximumFreeLPCWorkItems = REG_DWORD

Specify the maximum number of respective free structures (allocated but no longer used) to keep in the free list before any others are actually released back to the heap. The default value for these are 12 entries, with a valid range of 4 to 64.

MinFreeWorkItems = REG_DWORD

Specifies the minimum number of work items (receive buffers) that File and Print Services for NetWare keeps allocated. The range is 4 to 1024. The default depends on the setting for the Size parameter. If Size is 1 or 2, the default is 4, and if Size is 3, the default is 40.

NonblockingWorkerThreads = REG_DWORD

Specifies the number of threads set aside by the server to service requests that cannot block the thread for a significant amount of time. Larger values can increase performance but use more memory. A value that is too large can impede performance by causing excessive task switching. The range is 1 to 128, and the default depends on the server's configuration.

NTQueueDirectory = REG_EXPAND_SZ

Specifies the directory location for the print spooler files. The specified directory should be a valid directory. The default is %systemroot%\NWSPOOL.

OplockBreakWait = REG_DWORD

Specifies the time (in seconds) that the server waits for a client to respond to an oplock break request. Smaller values can allow detection of crashed clients more quickly. The range is 0 to 240, and the default is 60.

PrinterInfoAllocHint = REG_DWORD

The base allocation size used when obtaining printer information from WinSpool. This size is adjusted as the server is running to indicate the largest allocation required. The default value is 1024 bytes, and the valid range is sizeof(PRINTER_INFO_2) to 2048.

PrintJobNotifyFlag = REG_SZ

Specifies whether File and Print Services for NetWare will notify users, using the Windows NT Server Messenger Services, of finished print jobs. The possible values are 0 (never notify users), 1 (notify users that request to be notified in the capture command), and 2 (always notify users). The default is 1.

QCBEntryTimeout = REG_DWORD

Specifies the amount of time, in minutes, since the last use that must elapse before a QCB is freed. The range is 1 to 10 minutes; the default is 5 minutes.

ReturnShareableFlag = REG_DWORD

Sets the Shareable property globally for all files in all volumes on the server. The default is Yes.

SerialNumber = REG_DWORD

Sets the serial number that is returned to client computers that ask for it.

UserGroupSyncInterval = REG_DWORD

How often (in days) File and Print Services for NetWare cleans up user-defined registry objects. The range is 1 to 30, and the default is 7 days.

For More Information

For the latest information on Windows NT Server, check out our Web site at http://www.microsoft.com/ntserver and the Windows 2000/NT Forum at http://computingcentral.msn.com/topics/windowsnt.

Windows 2000 White Paper 4

File and Print Services for NetWare 73

Wyszukiwarka

Podobne podstrony:
10 Integracja NT i NetWare Directory Service Manager for NetWare
10 Integracja NT i NetWare, 10 Integracja NT i NetWare, Potrzeby ludzkie i środki ich zaspokajania
10 integracjaid 11290 ppt
10 x shed outline assembly and plan
10 faktów nt. nowego systemu dowodzenia Siłami Zbrojnymi RP (MON)
M46 Pump and Motor Service Manual
SHSBC329 THE TONE ARM AND THE SERVICE?CSIMILE
Multimedia Messaging Service For Gprs And Umts
10 killer job interview questions and how to answer them
10 integracjaid 11290 ppt
managing corporate identity an integrative framework of dimensions and determinants
DEPARTMENT OF HEALTH AND HUMAN SERVICES PROTECTION OF HUMAN SUBJECTS
Multimedia Messaging Service For Gprs And Umts
Borderline Pathology An Integration of Cognitive Therapy and Psychodynamic Thertapy
10 x 16 shed outline assembly and plan
VT Integrity Services for Networking
FIDE Trainers Surveys 2018 10 01 Dejan Bojkov Fictions and Reality Oppositon
Dos Santos Ferreira D , Staubach W Global and local regularity of Fourier integral operators on weig

więcej podobnych podstron