#EDIR DATA#
DOCTYPE='BOOK' PUBLICID='' SYSTEMID='/dtd/docbook.dtd'Installing and Using NetSyncInstalling and Using NetSyncNovell, Inc.DisclaimerNovell, Inc. makes no representations or warranties with
respect to the contents or use of this manual, and specifically
disclaims any express or implied warranties of merchantability or
fitness for any particular purpose. Further, Novell, Inc. reserves the
right to revise this publication and to make changes to its content,
at any time, without obligation to notify any person or entity of such
revisions or changes.Further, Novell, Inc. makes no representations or warranties
with respect to any NetWare software, and specifically disclaims any
express or implied warranties of merchantability or fitness for any
particular purpose. Further, Novell, Inc. reserves the right to make
changes to any and all parts of NetWare software, at any time, without
any obligation to notify any person or entity of such changes.TrademarksThe following are registered trademarks of Novell, Inc.: DR DOS, Fastpath, LAN WorkPlace, LANalyzer, NetWare, NetWare Name Service, Novell Press, UnixWare, WordPerfect.UNIX is a registered trademark of Novell, Inc. in the United States and other countries, licensed exclusively through X/Open Company, Ltd.The following are trademarks of Novell, Inc.: Advanced NetWare, Enterprise Certified NetWare Engineer, ECNE, EXOS, FirstMail, Global MHS, HSM, Hardware Specific Module, Hot Fix, IPX, IPX/SPX, IPXWAN, Internetwork Packet Exchange, LSL, Link Support Layer, MLI, MLID, MSL, MSM, MacIPX, MacNCP, MacNDS, Media Support Module, Mirrored Server Link, Multiple Link Interface, Multiple Link Interface Driver, NCP, NDR, NDS, NE/2, NE/2-32, NE1000, NE1500T, NE2000, NE2100, NE3200, NE32HUB, NLM, NLSP, NMS, NSE Pro, NTR2000, NVT, NetSync, NetWare 3, NetWare 4, NetWare 4.01, NetWare 4.1, NetWare Application Notes, NetWare Care, NetWare Client, NetWare Core Protocol, NetWare DOS Requester, NetWare Directory Services, NetWare Express, NetWare IPX Router, NetWare Link Services Protocol, NetWare Link/Frame Relay, NetWare Link/PPP, NetWare Link/X.25, NetWare Loadable Module, NetWare Logotype (teeth logo), NetWare MHS, NetWare Management Agent, NetWare Management System, NetWare Message Handling Service, NetWare MultiProtocol Router, NetWare Navigator, NetWare Peripheral Architecture, NetWare Ready, NetWare Requester, NetWare Runtime, NetWare SFT, NetWare SFT III, NetWare Tools, NetWare UAM, NetWare/IP, Netware Notify, Network Support Encyclopedia Professional Volume, Novell Labs, Novell Research Reports, Novell Virtual Terminal, ODI, Open Data-Link Interface, Packet Burst, Personal NetWare, RX-Net, RXNet/2, Red Box, SFT, SFT III, SMS, SPX, Sequenced Packet Exchange, Storage Management Services, Streams, TSM, Topology Specific Module, Transaction Tracking System, TTS, VLM, Virtual Loadable Module, "Yes, It Runs With NetWare Logo", and the "Yes, NetWare Tested and Approved Logo".The following are registered service marks of Novell, Inc.: Novell Technology Institute, NetWire.The following are service marks of Novell, Inc.: Novell Registry, Certified NetWare Administrator, CNA, Certified NetWare Engineer, CNE, Certified NetWare Instructor, CNI, Novell Authorized Service Center, NASC, Novell Technical Support.The following are collective marks of Novell, Inc.: Novell Authorized Reseller, Technical Support Alliance, TSA.3Com, 3+Share, and TokenLink are registered trademarks of 3Com Corporation.4.3BSD is a trademark of the Regents of University of California, Berkeley.ARCnet is a registered trademark of Datapoint Corporation.AT is a registered trademark of International Business Machines Corporation.AT&T is a registered trademark of American Telephone & Telegraph.Adobe and PostScript are registered trademarks of Adobe Systems Incorporated.Apple, AppleShare, AppleTalk, EtherTalk, ImageWriter, LaserWriter, LocalTalk, Macintosh, and MultiFinder are registered trademarks, and Finder and Mac are trademarks, of Apple Computer, Inc.Btrieve is a registered trademark of Btrieve Technologies, Inc.Canon is a registered trademark of Canon, Inc.COMPAQ is a registered trademark of COMPAQ Computer Corporation.Cisco Systems is a trademark of Cisco Systems, Inc.Citizen is a registered trademark of Tokei Kabushiki Kaisha.Claris is a trademark and MacWrite is a registered trademark of Claris Corporation.CompuServe is a registered trademark of CompuServe, Inc.DEC, DECnet, and Digital are trademarks of Digital Equipment Corporation.DeskJet, DeskWriter, LaserJet, PaintJet, PaintWriter, and PCL are registered trademarks of Hewlett-Packard Company.Diablo is a registered trademark of Xerox Corporation.DynaText is a registered trademark of Electronic Book Technologies, Inc.Epson is a registered trademark of Seiko Epson Corporation.EtherPrint is a trademark of 3Com Corporation.TokenPrint is a registered trademark of Dayna Communications.EtherFlex is a registered trademark of Extended Systems International.GatorBox is a registered trademark of Cayman Systems.Hewlett Packard, HP, HP-GL, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company.Hayes is a registered trademark of Hayes Microcomputer Products, Inc.IBM, OS/2, Micro Channel, ProPrinter, and PS/2 are registered trademarks and AFP, Presentation Manager, and SAA are trademarks of International Business Machines Corporation.Intel is a registered trademark and Pentium is a trademark of Intel Corporation.LaserBridge is a registered trademark of Sonic Systems.Lotus is a registered trademark of Lotus Development Corporation.MS-DOS and Microsoft are registered trademarks and LAN Manager is a trademark of Microsoft Corporation.MacPlot is a registered trademark of Microspot.NEC, Spinwriter, and Pinwriter are registered trademarks of NEC Corporation.NFS is a registered trademark of Sun Microsystems, Inc.Okidata and MicroLine are registered trademarks of Oki Electric Industry Co., Ltd.PageMaker is a registered trademark of Aldus Corporation.Panasonic is a registered trademark of Panasonic Office Automation.PowerPrint is a trademark of GDT Softworks, Inc.SQL Server is a trademark of Sybase, Inc.SprintTalk is a registered trademark of Digital Products.Ultra is a trademark of Hayes Microcomputer Products, Inc.Unicode is a registered trademark of Transoft Ltd.Word is a registered trademark of Microsoft Corporation.XT is a trademark of International Business Machines Corporation.Xerox is a registered trademark and XNS is a trademark of Xerox Corporation.cc:Mail is a trademark of cc:Mail, a Division of Lotus.All other trademarks, service marks, certification marks, and
collective marks --- registered or not --- are the property of their
respective owners.Copyright Notices© Copyright 1983-1994 Novell, Inc. All rights reserved. No
part of this publication may be reproduced, photocopied, stored on a
retrieval system, or transmitted without the express written consent
of the publisher.TYPE="VERT"Novell, Inc.122 East 1700 SouthProvo, UT 84606U.S.A.User Comment FormNovell encourages and welcomes your feedback and suggestions on ways we can improve our manuals. You can help us by sharing your comments and suggestions about how our manuals could be made more useful to you, and about any inaccuracies or information gaps they contain.Submit your comments by printing this User Comment form (click on the icon to display the form, then select "Print" from the "File" menu), filling it in, then faxing or mailing it to us.LABEL="0" FLOAT="0"User Comment FormFILEREF="ucomment.tif"PAGENUM=5 ID="BP1"How to Use This ManualRENDERAS="SECT1"IntroductionInstalling and Using NetSync tells you how to connect NetWare3.1x servers to a NetWare 4.1 server using NetSync.RENDERAS="SECT1"Contents OverviewRENDERAS="SECT2"Before Using NetSyncThis chapter describes what you need to do before installing NetSync and gives you conceptual information about NetSync.RENDERAS="SECT2"Installing NetSyncThis chapter gives instructions on how to install a NetSync cluster by installing NETSYNC4 on a NetWare 4.1 server and installing NETSYNC3 on NetWare 3.1x servers.RENDERAS="SECT2"Using the NetSync Options MenuThis chapter describes how to configure NetSync and monitor its operation.RENDERAS="SECT2"Printing Support for NetSyncThis chapter describes how printing works in NetSync.RENDERAS="SECT2"NetSync IssuesThis appendix covers issues NetWare issues that apply specifically to using NetSync.PAGENUM=6 ID="BP2"RENDERAS="SECT1"Documentation ConventionsThis manual uses the following Novell® conventions.RENDERAS="SECT2"Asterisk ( * )An asterisk denotes a trademarked name belonging to a third-party company. Novell trademarks are denoted with specific trademark symbols (®, TM, etc.).An ownership listing of all (Novell and third-party) trademarks cited in a manual can be found either on the disclaimer page in the front or in a "Trademarks" section at the back of printed manuals. A trademarks list is also available in the DynaText* online documentation.RENDERAS="SECT2"CommandsBoldface characters indicate items that you type, such as commands and options. You can use any combination of uppercase and lowercase letters.For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\A INSTALLRENDERAS="SECT2"Delimiter Bar ( | )In syntax examples, a delimiter bar separating two command options indicates that you can choose one of the options.For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"-S | -RDo not type the bar.RENDERAS="SECT2"DOS CommandsDOS commands and command option letters are shown in uppercase letters. For example: FTPD.Because DOS is not case-sensitive, you can type DOS commands in uppercase or lowercase letters.PAGENUM=7 ID="BP3"RENDERAS="SECT2"DOS Filenames, Directory Names, and PathnamesDOS filenames, directory names, and pathnames are shown in uppercase letters. For example, AUTOEXEC.BAT.Because DOS is not case-sensitive, you can type these names in uppercase or lowercase letters.RENDERAS="SECT2"EllipsesEllipses in syntax examples indicate that parameters, options, or settings can be repeated.For example, in the commandFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN SERVER1/SUPERVISOR /option...you could replace option with any number of available options.RENDERAS="SECT2"EmphasisItalic type also indicates emphasized text. For example:Remember to load the driver before you install the application.RENDERAS="SECT2"IconsChecklists, which often contain prerequisites, are marked with the "Checklist" icon to the left of this text.Procedures to follow in order to accomplish a specified task are marked with the "Procedure" icon to the left of this text.Additional or "nonessential" but noteworthy information is marked with the "Note" icon to the left of this text.Vital information about system or software requirements, etc., that deserves particular attention is marked with the "Important" icon to the left of this text.Guidelines or tips about fine-tuning, optimizing, etc., which might be applicable to your site or situation but maybe not to all, are emphasized with the "Suggestion" icon to the left of this text.PAGENUM=8 ID="BP4"Warnings about potential danger to data, hardware, or person are emphasized with the "Warning" icon to the left of this text. RENDERAS="SECT2"Key NamesAngle brackets surround the name of a key. For example, MOREINFO="NONE"<Enter> corresponds to the MOREINFO="NONE"Enter key on your keyboard. MOREINFO="NONE"<Ctrl>+<c> means hold down the MOREINFO="NONE"Ctrl key and simultaneously type the letter MOREINFO="NONE"c (in lowercase, in this case).RENDERAS="SECT2"OptionsIn syntax examples, braces indicate that you are required to choose one of the enclosed options. For example, the following notation means that you must include a 0 or a 1 in the command:FORMAT="LINESPECIFIC"MOREINFO="NONE"{0, 1}RENDERAS="SECT2"Square BracketsIn syntax examples, boldface type enclosed in square brackets indicates command options that you can type as needed. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"FTP [ -D ] [ -F ]RENDERAS="SECT2"System ResponseMonospace type shows system-generated responses that appear on your workstation screen. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"TNVT220>RENDERAS="SECT2"VariablesItalic type indicates variables---descriptive item names, such as command parameters---that you replace with appropriate values.For example, in the command:FORMAT="LINESPECIFIC"MOREINFO="NONE"FTP -F remote_host
PAGENUM=9 ID="BP5"you type the name of a computer on your network in place of remote_host.RENDERAS="SECT1"Online HelpMARK=BULLETContext-sensitive help. If you are using a NetWare menu utility and want more information about how to complete a task, press MOREINFO="NONE"<F1>.If you are unsure how to use a command, type the command name and add the /? option for help. For example, for help with the RIGHTS command, type "RIGHTS /?".DynaText online documentation. The DynaText viewer allows you to read NetWare documentation from your DOS, MS Windows, Macintosh*, UNIX, or OS/2* workstation.All NetWare 4TM and 3.12 documentation except the Quick Access Guide are available on the NetWare Online Documentation CD-ROM.RENDERAS="SECT1"Additional Help ResourcesMARK=BULLETNovell Authorized Service CenterSM (NASC) locations. NASCSM facilities are local support providers authorized and supported by Novell. They provide both telephone and on-site assistance, and should be your first source for technical support.For the Novell Authorized Service Center nearest you, in the U.S. and Canada call 1-800-338-NASC.Hardware documentation. Many network problems occur because of malfunctioning hardware.If you can isolate a problem to a certain computer component or cable segment, check the manuals that came with the hardware involved.NetWare Management SystemTM (NMS) services. NMSTM services helps you manage the cabling system, computers, software, and other components of the network.For more information about using NMS on your network, contact your Novell Authorized ResellerCLM representative.PAGENUM=10 ID="BP6"Other Novell publications. NetWare Applications Notes and Research Reports cover technical aspects of NetWare based system design, implementation, and management.Application Notes is a collection of technical articles published monthly. Research Reports is published as the research becomes available.To purchase subscriptions and back issues of these publications from within the United States or Canada, call the Novell Research Order Desk at 1-800-UPDATE1. From other locations, call 801-429-5380.Third-party books and periodicals. A number of books on NetWare, including books published by Novell PressTM publishing, are available at most bookstores.In addition, numerous networking periodicals give advice on configuring, managing, and troubleshooting your network.NetWire® forum on the CompuServe® bulletin board. A fairly inexpensive way to get up-to-date advice and patches is through NetWire on the CompuServe bulletin board.To open a CompuServe account, call one of the following numbers and ask for "Representative 200"MARK=BULLETIn the United States or Canada: 1-800-524-3388In the United Kingdom: 0800-289-378In Germany: 0130-37-32In other European countries: 44-272-255-111In locations other than the United States, Canada, or Europe, use the appropriate country code for the U.S. and call 614-457-0802. Ask for "Representative 200." This phrase identifies you as a Novell customer.Technical Support Database and NetWire forum on the Internet. The Novell FTP sites support access through FTP, Gopher, and World Wide Web (WWW) systems. Over 9,000 documents exist on the WWW system for providing technical hints and information.PAGENUM=11 ID="BP7"To access the Novell Internet sites, log in as ANONYMOUS and use your E-mail address as your password.   Contact one of the following site addresses:TYPE="VERT"In the United States: ftp.novell.comIn Germany: ftp.novell.deIn the United Kingdom: ftp.salford.ac.ukIn Canada: novell.nrc.caSee public areas in these sites for possible listings of other sites addresses. FaxBack Service. Novell provides a FaxBack Service for obtaining additional product information to help with support needs.To access the Novell FaxBack Service, complete the following steps.MARK=BULLETWithin the continental United StatesTYPE="VERT"1. Dial 1-800-NETWARE (1-800-638-9273).2. Press #1 (the "Presale Product Information and Upgrade Information" option).3. Again press #1 (the "Receive Product Information via Fax" option).Outside the continental United StatesDial 1-801-429-2772. You are connected directly to the FaxBack Service.Follow the directions provided on the phone. You are prompted to enter a document number and then a fax number to send the document to.Network Support Encyclopedia Professional VolumeSM (NSE Pro) package. This encyclopedia gives customers access to regularly updated information on products and services---plus patches, fixes, and more---from Novell and other vendors.The NSE ProSM package is distributed on CD-ROM on a subscription basis. Updates are sent out several times each year. More information is available on NetWire or from your Novell Authorized Reseller.Troubleshooting hardware and software. Specialized hardware and software packages, such as the Novell LANalyzer® software, are available to help you isolate network problems.Customer service. You can contact your Novell Authorized Reseller for technical assistance.PAGENUM=12 ID="BP8"Most Novell Authorized Resellers have Certified NetWare EngineerSM representatives on their staffs ready to assist users with their networking problems.RENDERAS="SECT1"User CommentsWe are continually looking for ways to make our products and our documentation as easy to use as possible.You can help us by sharing your comments and suggestions about how our documentation could be made more useful to you and about inaccuracies or information gaps it might contain.Submit your comments either by filling out the "User Comments" form at the end of this document or by writing to us directly at the following address:TYPE="VERT"Novell, Inc.Technical Publications MS C-23-1122 East 1700 South Provo, UT 84606 USAWe appreciate your comments.LABEL="1"PAGENUM=1 ID="BP9"ID="FM43011"Before Using NetSyncRENDERAS="SECT1"ID="FM80581"What IDXID="w4970"BOOK="_idx" COLLECTION="nw41" TIDREF="i2680"
NetSync DoesNetSync IDXID="w4971"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"
is a management utility that allows you to extend part of the benefits of the NetWare® Directory ServicesTM architecture to NetWare 3.1x file servers. Specifically, NetSync lets youMARK=BULLETSynchronize NetWare 3.1x users and groups with objects in a NetWare 4.1 server's bindery contextFor more information, see "BOOK="cncptenu" COLLECTION="nw41"Bindery context" in Concepts.When you update or create a user in the bindery context of the NetWare 4.1 host, that user is synchronized with all NetWare 3.1x servers in the NetSync cluster. (A NetSync IDXID="w4972"BOOK="_idx" COLLECTION="nw41" TIDREF="i663"IDXID="w4973"BOOK="_idx" COLLECTION="nw41" TIDREF="i2680"cluster consists of one NetWare 4.1 server and up to 12 attached NetWare 3.1x servers.) The user now exists on all NetWare 3.1x servers that are part of the cluster and are actively attached. Consequently, you don't have to update or create this user on each NetWare 3.1x server.Manage NetWare 3.1x users and groups from within the NetWare 4.1 administrative utilities (NETADMIN or NetWare Administrator)Do not use SYSCON for these tasks.Move NetWare 3.1x print services to a NetWare 4.1 server(See Chapter 4, IDREF="FM47705""Printing Support for NetSync," page 41.)Manage NetWare 3.1x printing with the NetWare 4.1 print utilities (NetWare Administrator or PCONSOLE)Do not use NetWare 3.1x printing utilities to manage print services moved to the NetWare 4.1 host.PAGENUM=2 ID="BP10"RENDERAS="SECT1"When to IDXID="w4974"BOOK="_idx" COLLECTION="nw41" TIDREF="i2680"
Use NetSyncUse NetSync on your NetWare 3.1x and NetWare 4.1 servers if:MARK=BULLETYou are running NetWare Name Service® (NNS) software and don't want to upgrade all servers in an NNS® domain to NetWare 4.1 simultaneouslyYou need a temporary solution for central administration of a mixed network before full migration to NetWare 4.1--if you want a centrally administered, mixed NetWare 3.1x and NetWare 4.1 network that consists of at least one 4.1 server and a maximum of twelve 3.1x servers per 4.1 serverYou want to make existing NetWare 3.1x users, groups, and print queues part of the NetWare 4.1 Directory database, without upgrading all NetWare 3.1x servers to NetWare 4.1Do not use IDXID="w4975"BOOK="_idx" COLLECTION="nw41" TIDREF="i2680"
NetSync ifMARK=BULLETYou have only NetWare 4TM servers on your networkYou intend to migrate all your NetWare 3.1x servers to NetWare 4.1 simultaneously or within a short time periodYou plan to have a separate network supervisor for each NetWare 3.11 server in your network who will continue to manage users and groups with SYSCON and other NetWare 3.1x utilitiesYou do not see a need to make NetWare 3.11 users and groups part of the NetWare 4.1 Directory databasePAGENUM=3 ID="BP11"RENDERAS="SECT1"ID="FM20501"How NetSync WorksTo run NetSync, you select one NetWare 4.1 server to be the 
host for up to 12 NetWare 3.1x servers. The IDXID="w4976"BOOK="_idx" COLLECTION="nw41" TIDREF="i2675"
host's function is to MARK=BULLETAct as a repository for bindery objects that are copied into its bindery contextDownload all the objects in its bindery context to the 3.1x servers that are synchronized with the hostContinuously monitor changes to objects in the NetWare 4.1 bindery context, and then download those changes to all attached NetWare 3.1x servers in the NetSync cluster Update the bindery of 3.1x servers when they are brought up again after downtimeRENDERAS="SECT2"ID="FM51976"NetSync ModulesYou load NetSync NLMTM programs first on the NetWare 4.1 host server and then on the NetWare 3.1x servers. These programs allow the servers to communicate with each other. They initially copy (IDXID="w4977"BOOK="_idx" COLLECTION="nw41" TIDREF="i4691"
upload) all IDXID="w4978"BOOK="_idx" COLLECTION="nw41" TIDREF="i2826"
users and groups from the NetWare 3.1x servers' binderies into the bindery context of the NetWare 4.1 server, as illustrated in the following figure.LABEL="1-1" FLOAT="0"NetWare 3.1x bindery is uploaded to NetWare 4.1 hostFILEREF="n41ns17a.tif"PAGENUM=4 ID="BP12"NetSync depends on the setting of a bindery context on the NetWare 4.1 server, and this bindery context must not be IDXID="w4979"BOOK="_idx" COLLECTION="nw41" TIDREF="i2680"
changed. The default bindery context set for NetWare 4.1 is the container where the server is installed.  However, you can set the bindery context for NetSync to any context in the Directory; the NetWare 4.1 host's Server object does not have to be part of this bindery context.For more information on setting a bindery context, see "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.All bindery and Directory Services User and Group objects are combined and copied to each NetWare 3.1x server. Each NetWare 3.1x server IDXID="w4980"BOOK="_idx" COLLECTION="nw41" TIDREF="i1216"IDXID="w4981"BOOK="_idx" COLLECTION="nw41" TIDREF="i848"
then has a IDXID="w4982"BOOK="_idx" COLLECTION="nw41" TIDREF="i2680"
copy of this "IDXID="w4983"BOOK="_idx" COLLECTION="nw41" TIDREF="i4338"IDXID="w4984"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"
super-bindery," as illustrated in the figure below.LABEL="1-2" FLOAT="0"Super-bindery copied to 3.1x serversFILEREF="n41ns18a.tif"Consequently, any NetWare 3.1x user can access any other NetWare 3.1x server that is part of the same NetSync cluster. (File access is still controlled by trustee rights, which must be assigned locally on each server, as before.)The following illustration shows example users and groups on one NetWare 4.1 and two NetWare 3.1x servers before the installation of NetSync. PAGENUM=5 ID="BP13"LABEL="1-3" FLOAT="0"Users and Groups before installing NetSyncFILEREF="n41ns11a.tif"After the installation of NetSync, the example users and groups are distributed as follows.LABEL="1-4" FLOAT="0"Users and Groups after installing NetSyncFILEREF="n41ns12a.tif"PAGENUM=6 ID="BP14"RENDERAS="SECT2"Bindery SynchronizationUnder normal circumstances, IDXID="w4985"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"
synchronization of the NetWare 3.1x servers' binderies with the NetWare 4.1 Directory is required only once---when the NetWare 3.1x server is first brought into the NetSync environment. Updates from the NetWare 4.1 bindery context to the NetWare 3.1x servers then happen automatically and continuously, whenever changes are made to objects in the NetWare 4.1 server's bindery context.The NetWare 4.1 server also downloads the bindery context to a NetWare 3.1x server whenever that 3.1x server is brought up again after downtime. This download brings the 3.1x server up to date on changes made to the bindery context while it was down.RENDERAS="SECT2"Use NETADMIN, Not IDXID="w4986"BOOK="_idx" COLLECTION="nw41" TIDREF="i2826"IDXID="w4987"BOOK="_idx" COLLECTION="nw41" TIDREF="i4365"
SYSCONAfter synchronization, make all changes to users or groups on the NetWare 3.1x servers with NETADMIN or NetWare Administrator. Changes made this way are automatically dispersed to all other servers in the NetSync cluster.Any changes made with NetWare 3.1x administrative utilities (such as SYSCON) on NetWare 3.1x servers are not copied to other servers in the cluster, so your servers will get out of sync. Therefore, don't use SYSCON except to manage accounting charge rates on each NetWare 3.1x server. (Accounting rate changes are not handled by NetSync.)  If, after installing NetSync, you use SYSCON to change user or group information on a 3.1x server and want to synchronize this information, you must re-copy the bindery information to the NetWare 4.1 server. (See IDREF="FM45212""Copying a NetWare 3.1x Server's Bindery to NetWare 4.1," page 38.)RENDERAS="SECT2"Multiple 4.1 Servers in the NetSync Bindery ContextIf you have more than one NetWare 4.1 server running NetSync with the same bindery context, all NetWare 3.1x servers attached to these hosts are synchronized with the same "super-bindery."For example, assume five NetWare 4.1 servers have the same bindery context. All five servers are running NetSync, and each of them has 12 NetWare 3.1x servers attached. PAGENUM=7 ID="BP15"All 60 NetWare 3.1x servers upload their binderies to the 4.1 bindery context, and the whole bindery context then gets downloaded to these 60 NetWare 3.1x servers. While there is no fixed upper limit to the number of NetWare 4.1 servers per bindery context, be aware that NetSync is a memory- and CPU-intensive process. The more objects being synchronized, the more synchronization overhead the servers experience.RENDERAS="SECT2"Moving IDXID="w4988"BOOK="_idx" COLLECTION="nw41" TIDREF="i3465"
Print ServersWith NetSync, you can move all NetWare 3.1x print servers and merge them into a single print server on the NetWare 4.1 server. Existing IDXID="w4989"BOOK="_idx" COLLECTION="nw41" TIDREF="i3442"
print queues appear the same to users, but are now serviced by the NetWare 4.1 print server. Old NetWare 3.1x print utilities are automatically replaced with NetWare 4.1 print utilities that have been copied to the NetWare 3.1x servers.For more on NetSync printing, see Chapter 4, IDREF="FM47705""Printing Support for NetSync," page 41.RENDERAS="SECT2"Which 
Objects Are 
SynchronizedNetSync synchronizes the following objects:MARK=BULLETUsers and all their properties, for example, passwords, login scripts, and login restrictionsGroupsProfiles (NetWare Name Service)Print queues created on NetWare 3.1x servers and changes made to print queues on the NetWare 4.1 serverRENDERAS="SECT2"What Information Does Not Get SynchronizedMARK=BULLETUser SUPERVISOR (each NetWare 3.1x server will have a separate SUPERVISOR and corresponding password)User object ADMIN (on the NetWare 4.1 server)PAGENUM=8 ID="BP16"Print queues created on the NetWare 4.1 server.Accounting charge rates and account balances (specific to NetWare 3.1x servers; charge rates are managed through SYSCON.)Object names that include characters that were illegal in bindery names (Illegal characters for bindery names are $, ?, \, /, ", [, ], :, |, <, >, +, and =. Illegal characters can vary among different languages.) File system rights that NetWare 3.1x users and groups have on the NetWare 3.1x server (these rights continue to be server-specific and are only valid for the volumes on those servers)System login scriptsRENDERAS="SECT2"NetSync 
ModulesNetSync consists primarily of three loadable modules: NETSYNC4, NETSYNC3, and REMAPID. These and other modules (explained in the following table) are needed for NetSync to function properly.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="24*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare ModuleCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4990"BOOK="_idx" COLLECTION="nw41" TIDREF="i2683"
NETSYNC4COLNAME=2 ROTATE="0" MOREROWS="0"Loaded on the NetWare 4.1 "host" server. Use this module to control the NetSync cluster. You can authorize NetWare 3.1x servers and copy necessary files to 3.1x servers. Once synchronized, when changes are detected, NETSYNC4 copies (downloads) updated Directory information to all attached NetWare 3.1x servers in the cluster. It also copies updated Directory information to 3.1x servers that are brought up again after downtime.NETSYNC4 should run continuously, so you should add the command MOREINFO="NONE"LOAD NETSYNC4 to the NetWare 4.1 server's AUTOEXEC.NCF file. (This command can be added automatically during the NetSync installation process.)COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4991"BOOK="_idx" COLLECTION="nw41" TIDREF="i2681"
NETSYNC3COLNAME=2 ROTATE="0" MOREROWS="0"Loaded on each NetWare 3.1x server in the cluster. Copies (uploads) the 3.1x server's bindery information to the NetWare 4.1 server's bindery context, then continues to communicate with the NetWare 4.1 server to receive updates to its bindery. NETSYNC3 converts the 3.1x PRINTDEF and PRINTCON databases to a database format compatible with NetWare 4.1 so you can move print servers and their associated queues and printers to NetWare 4.1.NETSYNC3 creates a working directory (NETSYNC) for the NetSync log files under SYS:SYSTEM.NETSYNC3 should run continuously, so you should add the command MOREINFO="NONE"LOAD NETSYNC3 to the NetWare 3.1x server's AUTOEXEC.NCF file. (This command can be added automatically during the NetSync installation process.) However, NETSYNC3 can run only if NETSYNC4 is already loaded on the NetWare 4.1 server.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w4992"BOOK="_idx" COLLECTION="nw41" TIDREF="i3733"
REMAPIDCOLNAME=2 ROTATE="0" MOREROWS="0"Autoloaded by NETSYNC3.NLM on every NetWare 3.1x server in the cluster. This module handles password synchronization and must remain loaded even if the NETSYNC3 module is unloaded. REMAPID should run continuously, so you should add the command MOREINFO="NONE"LOAD MOREINFO="NONE"REMAPID to the NetWare 3.1x server's AUTOEXEC.NCF file. (This command can be added automatically during the NetSync installation process.) COLNAME=1 ROTATE="0" MOREROWS="0"Additional NetWare 3.1x loadable modules (CLIB, STREAMS, NWPSRV3X, NWSNUT, AFTER311, A3112, and PBURST [NetWare 3.11 only])COLNAME=2 ROTATE="0" MOREROWS="0"The latest versions of these modules must replace older versions on all NetWare 3.1x servers in the NetSync cluster. These modules are automatically copied to your NetWare 3.1x servers when you install NetSync.PAGENUM=9 ID="BP17"RENDERAS="SECT2"Location of IDXID="w4993"BOOK="_idx" COLLECTION="nw41" TIDREF="i2676"
NetSync Log FilesNetSync log files track the messages displayed while NetSync is running. This includes all events that were handled, uploads and downloads that were completed, and so on.Log files are located in SYS:SYSTEM\NETSYNC on each NetWare 3.1x server in the cluster and on the NetWare 4.1 server. PAGENUM=10 ID="BP18"This directory is created when you load NETSYNC3 on a NetWare 3.1x server, and is created on a NetWare 4.1 server during the regular server installation process. The log file is an ASCII file, default maximum size 0.5 MB, called NETSYNC.LOG. This file will grow to the designated size. If it is not cleared before it reaches 0.5 MB (or other specified size), this file is automatically renamed to NETSYNC.OLD and a new NETSYNC.LOG is begun. To change the maximum size of the log file, see IDREF="FM69293""Changing the Size of the Log File," page 34.Only two NETSYNC log files are retained at any time. Older files are deleted automatically.You can turn off the log file option so that none is created (see IDREF="FM13051""Disabling the Log File," page 36). By turning off the log file, you might notice an increase in the speed of network operations.RENDERAS="SECT2"What Happens When You IDXID="w4994"BOOK="_idx" COLLECTION="nw41" TIDREF="i2826"IDXID="w4995"BOOK="_idx" COLLECTION="nw41" TIDREF="i4669"IDXID="w4996"BOOK="_idx" COLLECTION="nw41" TIDREF="i2680"
Unload NetSyncWhen you unload NETSYNC4 at the NetWare 4.1 server's console, NETSYNC3 is automatically unloaded from all authorized NetWare 3.1x servers in the NetSync cluster. To reload, load NETSYNC4 before NETSYNC3.REMAPID.NLM, which handles password synchronization and is automatically loaded by NETSYNC3.NLM, must remain loaded on the NetWare 3.1x server.REMAPID.NLM must remain resident for users to continue to be able to log in to a NetWare 3.1x server. If you unload REMAPID, you must reload REMAPID to restore the passwords or manually assign new passwords to all users in the system.PAGENUM=11 ID="BP19"RENDERAS="SECT1"ID="FM52736"Managing NetSync IDXID="w4997"BOOK="_idx" COLLECTION="nw41" TIDREF="i4714"IDXID="w4998"BOOK="_idx" COLLECTION="nw41" TIDREF="i2326"
UsersRENDERAS="SECT2"Don't Use SYSCONManage IDXID="w4999"BOOK="_idx" COLLECTION="nw41" TIDREF="i2326"
users and groups only from within NetWare 4.1 utilities (NETADMIN or NetWare Administrator.) Do not use IDXID="w5000"BOOK="_idx" COLLECTION="nw41" TIDREF="i4364"
SYSCON to administer these objects, because changes made in SYSCON are not synchronized across the NetSync cluster.Consequently, using SYSCON on a NetWare 3.1x server to manage users and groups will cause this 
server to become IDXID="w5001"BOOK="_idx" COLLECTION="nw41" TIDREF="i2826"
out of sync. Thus, the whole purpose of using NetSync is defeated.RENDERAS="SECT2"ID="FM84011"Eliminate 
Duplicate 
Objects before Using NetSyncMake sure that there are no duplicate Directory Services or bindery object names (except names of print queues or printers) that refer to different objects on any NetWare servers that are part of the same NetSync cluster.Any existing Directory Services object takes precedence over any bindery object of the same name.Objects with identical names can exist on different NetWare 3.1x servers that are uploaded into the same bindery context under NetSync. However, NetWare Directory Services on the NetWare 4.1 server does not allow more than one object with the same name in the same bindery context. Consequently, when you upload NetWare 3.1x binderies into the same context, conflicts may arise.Duplicate object conflicts can arise for MARK=BULLETObjects of the same type Objects of different typesExisting objects in a bindery context pathObject names containing diacritic charactersPAGENUM=12 ID="BP20"RENDERAS="SECT3"Objects 
of the Same TypeAssume that two user objects named Joe are on two NetWare 3.1x servers that will be part of the same NetSync cluster.MARK=BULLETIf the two Joes are the same person, NetSync will IDXID="w5002"BOOK="_idx" COLLECTION="nw41" TIDREF="i4714"IDXID="w5003"BOOK="_idx" COLLECTION="nw41" TIDREF="i2409"
merge the two objects in the NetWare 4.1 bindery context. Be aware that the user Joe on the first NetWare 3.1x server to be synchronized (Joe A) takes precedence-- he gets created as an object with all properties intact. When NetSync encounters the second user Joe (Joe B), it scans Joe B's properties for any that did not exist for Joe A. If a property already exists, Joe B's property is discarded. If a property does not already exist, Joe B's property is added, merging the two Joes. If the two Joes don't refer to the same user, change login names before running NetSync so that the two Joes have distinct names, such as JSmith and JJones. Otherwise, the two users will be merged as in the above example---the difference being that both user's definitions are now corrupted, because the usernames did not refer to the same user. For example, the merged user Joe might have Joe A's email address and login restrictions but have Joe B's login script.RENDERAS="SECT3"Objects 
of Different TypesAvoid using the same name for different object types, such as a print queue named Joe and a user named Joe. Using duplicate names causes problems when the objects are uploaded by NetSync.When you run NetSync and multiple objects have identical names on NetWare 3.1x servers, only the first object to be uploaded will be converted to a Directory object. For example, if print queue Joe gets uploaded to the NetWare 4.1 bindery context before user Joe, print queue Joe will become a Print Queue object. User Joe, however, since his object type is different from Print Queue Joe, will become an object of type "bindery object," and will not show up as a User object. User Joe would not be able to access NetWare Directory Services but would be able to access bindery services.PAGENUM=13 ID="BP21"For more information on bindery objects, see "BOOK="cncptenu" COLLECTION="nw41"Bindery object" in Concepts.RENDERAS="SECT3"Objects in a Bindery Context PathSee IDREF="FM27459""Duplicate Names in a Bindery Context Path" on page 58.RENDERAS="SECT3"Object Names Containing Diacritic CharactersSee IDREF="FM93433""Usernames Containing European Diacritic Characters" on page 57.RENDERAS="SECT1"IDXID="w5004"BOOK="_idx" COLLECTION="nw41" TIDREF="i1680"
Home Directories in NetSyncWhen a user is created in the NetWare 4.1 bindery context and synchronized with the NetWare 3.1x servers, NetSync does not create a home directory for that user on each NetWare 3.1x server. Likewise, when users are copied from the NetWare 3.1x server into the NetWare 4.1 Directory, no home directory is created on the NetWare 4.1 server. You cannot create home directories automatically for users in a NetSync environment. If you need home directories on other than the original server, you must manually create them (and grant rights).RENDERAS="SECT1"Accounting and NetSyncIDXID="w5005"BOOK="_idx" COLLECTION="nw41" TIDREF="i620"
Charge rates and account balances are not synchronized. Charges made on a NetWare 3.1x or 4.1 server stay local to the server they are made on. For example, when a user uses time on a NetWare 3.1x server, the user's IDXID="w5006"BOOK="_idx" COLLECTION="nw41" TIDREF="i62"IDXID="w5007"BOOK="_idx" COLLECTION="nw41" TIDREF="i2326"
account balance is diminished on that 3.1x server only. You must still manage accounting and charge rates for the NetWare 3.1x servers through SYSCON, and for the NetWare 4.1 Directory through NETADMIN or NetWare Administrator.PAGENUM=14 ID="BP22"RENDERAS="SECT1"Login ConsiderationsRENDERAS="SECT2"How Users IDXID="w5008"BOOK="_idx" COLLECTION="nw41" TIDREF="i2192"IDXID="w5009"BOOK="_idx" COLLECTION="nw41" TIDREF="i2829"
Log InNetSync automatically copies the NetWare 4.1 LOGIN utility to the SYS:LOGIN and SYS:PUBLIC directories on the NetWare 3.1x server. The "old" NetWare 3.1x IDXID="w5010"BOOK="_idx" COLLECTION="nw41" TIDREF="i2220"
LOGIN utility is overwritten.However, users can still log in to NetWare 3.1x servers the same way they always have.Users can log in using Virtual Loadable ModuleTM (VLM) programs or NETX software. Workstations need to use VLM programs only if users want to access IDXID="w5011"BOOK="_idx" COLLECTION="nw41" TIDREF="i2728"
NetWare Directory Services on the NetWare 4.1 server. The older NETX client software cannot authenticate to NetWare Directory Services, but it can still be used for logging in to a NetWare 4.1 server through bindery services. (For more information on bindery services, see "BOOK="cncptenu" COLLECTION="nw41"Bindery services" in Concepts.)To log in to a IDXID="w5012"BOOK="_idx" COLLECTION="nw41" TIDREF="i2680"
NetWare 4.1 server through IDXID="w5013"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"
bindery services, use the following syntax:FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN servername/username MOREINFO="NONE"/BMOREINFO="NONE" <Enter>orFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN /B MOREINFO="NONE"<Enter>RENDERAS="SECT2"What Happens to IDXID="w5014"BOOK="_idx" COLLECTION="nw41" TIDREF="i3246"
PasswordsPasswords are the only pieces of information in NetSync that are synchronized in both directions. This means that users can change their passwords on any server in the NetSync cluster (even with NetWare 3.1x utilities on their 3.1x server), and the change is propagated throughout the cluster. In NetWare 3.1x, if users have accounts on more than one server, they will typically maintain the same password on all servers. PAGENUM=15 ID="BP23"When changing their password with 3.1x SETPASS or LOGIN, the utility will ask them if they want to synchronize password changes to all attached servers. With NetSync, passwords are synchronized automatically for servers that are in the same cluster, even if users say "No" to the "synchronize passwords" question.RENDERAS="SECT2"ID="FM64952"What Happens to Login 
ScriptsRENDERAS="SECT3"ID="FM49544"User IDXID="w5015"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
Login ScriptsOn a NetWare 3 server, a user login script is a file in each user's MAIL directory. On a NetWare 4 server, a user's login script is a property of the User object. NetSync synchronizes the MAIL directory login script on the NetWare 3.1x server with the NDS login script property. When you change the user's login script, use the NetWare 4.1 utilities to change the NDS login script property, and the change will be synchronized to the NetWare 3.1x MAIL directory.By default, NetSync also creates a login script file in the user's MAIL directory on the NetWare 4.1 server. (You can disable this parameter as one of the configuration options. See IDREF="FM42145""Disabling the Synchronization of 3.1x Login Scripts with 4.1 Login Scripts" on page 36.)If you allow this, the user login script will be synchronized in three places: the NDS login script property on the NetWare 4.1 server, the user's 3.1x MAIL directory, and the user's 4.1 MAIL directory.Creating a login script file in the user's 4.1 MAIL directory allows the user to log in to the NetWare 4.1 server and have the same user login script execute regardless of whether the user is using VLM programs and Directory Services software (which use the NDS login script property) or bindery services software and NETX or VLM programs (which use the MAIL directory file.)Login scripts are synchronized when uploaded from NetWare 3.1x servers to the NetWare 4.1 server, when downloaded from the NetWare 4.1 to the NetWare 3.1x server, or when an update event is detected.ID="FM90568"To prevent synchronization, see IDREF="FM42145""Disabling the Synchronization of 3.1x Login Scripts with 4.1 Login Scripts," page 36.PAGENUM=16 ID="BP24"If multiple NetWare 4.1 servers have the same bindery context and you want to keep the user's NetWare 3.1x login script in SYS:SYSTEM\MAIL synchronized with the Directory Services login script on all the 4.1 servers, run a copy of NETSYNC4 on each NetWare 4.1 server. This allows users to log in to the NetWare 4.1 servers with a bindery login.RENDERAS="SECT3"System IDXID="w5016"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
Login ScriptsSystem login scripts are not synchronized, because they are specific to each NetWare 3.1x server. When a user logs in to a NetWare 3.1x server, that server's system login script executes, giving the user server-specific drive mappings.When the user uses VLM programs and logs in to the NetWare 4.1 server, authenticating to NetWare Directory Services, the NDS container object's login script executes instead.RENDERAS="SECT1"ID="FM29172"NetWare Name Service (
NNS) ConsiderationsIf you use IDXID="w5017"BOOK="_idx" COLLECTION="nw41" TIDREF="i2768"
NNS, you can replace it with NetSync. NetSync will automatically convert most of the NNS configuration information to a form usable by NetWare 4.1. Then when you are ready to upgrade the 3.1x servers in the NetSync environment to NetWare 4.1, it will be a much easier process.To keep the servers in the NNS domain synchronized, you must migrate all NetWare 3.1x servers in the NNS domain to NetSync at the same time.Once you load NETSYNC3 on a NetWare 3.1x server, NNS is automatically uninstalled. The NETSYNC3 NLM checks for the presence of NNS on the server, and then removes the server from the NNS domain.When NetSync is installed, NNS profiles are converted to NetWare Directory Services (NDS) profiles. NNS profile login scripts are assigned to Profile objects and still available for use. The default profile property in NNS is converted to the profile property in NetWare Directory Services, so users who had default profiles in NNS still have them in NetWare 4.1 with NetSync.Although the NetWare 3.1x LOGIN utility does not allow profile login scripts, the new NetWare 4.1 LOGIN utility does. The 4.1 LOGIN utility is copied to each NetWare 3.1x server during NetSync installation.PAGENUM=17 ID="BP25"If you want to continue using the drive mappings that were defined in the profile login scripts, you must add an attach statement for each server to which you are mapping a drive in the system login script on each 3.1x server. This will allow users to continue using these mappings without logging in again.This means that NetSync users can use profile IDXID="w5018"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"IDXID="w5019"BOOK="_idx" COLLECTION="nw41" TIDREF="i2768"IDXID="w5020"BOOK="_idx" COLLECTION="nw41" TIDREF="i3566"
login scripts on 3.1x servers even if they weren't previously using NNS.To assign a profile login script to a NetSync user, use NETADMIN or NetWare Administrator to select that User object and assign it to the profile. You must manually grant rights to read the profile login script.The IDXID="w5021"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
login scripts execute in this order: system login script (specific to each 3.1x server), profile login script, and then user login script.NetSync will also upgrade NNS printing. See IDREF="FM70522""Upgrading NetWare Name Service (NNS) Printing" on page 52.RENDERAS="SECT1"Managing 
NetSync ProblemsRENDERAS="SECT2"If a NetWare 3.1x Server 
Goes DownIf a NetWare 3.1x server goes down, that server will IDXID="w5022"BOOK="_idx" COLLECTION="nw41" TIDREF="i2826"
miss synchronization information that occurs during the downtime. When the server is brought back up, the NetWare 4.1 bindery context is copied (downloaded) to the server again, to ensure that it has all updates that occurred while it was down.Don't delete or rename objects unless all servers in the NetSync cluster are running. If you delete or rename User or Group objects in the NetWare 4.1 bindery context during down time, the NetWare 3.1x server will be out of sync.  This occurs because deleted objects are not cleared after the connection is re-established. Then, if you manually upload the NetWare 3.1x server's bindery to the NetWare 4.1 side the deleted objects are re-created and again synchronized with the other NetWare 3.1x servers.RENDERAS="SECT2"If the NetWare 4.1 
Server Goes DownIf the IDXID="w5023"BOOK="_idx" COLLECTION="nw41" TIDREF="i2675"IDXID="w5024"BOOK="_idx" COLLECTION="nw41" TIDREF="i2826"
NetSync host goes down while the binderies of one or more NetWare 3.1xPAGENUM=18 ID="BP26" servers are being copied (uploaded), restart the synchronization when the server comes back up by recopying the bindery information of the affected NetWare 3.1x servers. (For more information, see IDREF="FM45212""Copying a NetWare 3.1x Server's Bindery to NetWare 4.1," page 38.)RENDERAS="SECT2"If the Server 
Runs Out of IDXID="w5025"BOOK="_idx" COLLECTION="nw41" TIDREF="i2675"IDXID="w5026"BOOK="_idx" COLLECTION="nw41" TIDREF="i2826"IDXID="w5027"BOOK="_idx" COLLECTION="nw41" TIDREF="i1131"
Disk SpaceIf a NetWare 3.1x or 4.1 server runs out of disk space for the bindery synchronization information, an error message is displayed on each server.Either add more disk space to the server or delete unnecessary files. Then reload NETSYNC3.NLM or NETSYNC4.NLM. LABEL="2"PAGENUM=19 ID="BP27"Installing NetSyncRENDERAS="SECT1"PrerequisitesIDXID="w5028"BOOK="_idx" COLLECTION="nw41" TIDREF="i1828"IDXID="w5029"BOOK="_idx" COLLECTION="nw41" TIDREF="i3381"RENDERAS="SECT2"HardwareMARK=BULLETAt least one 
NetWare® 4.1TM server. Up to twelve NetWare 3.1x servers per NetWare 4.1 server. No additional RAM and disk space should be required to run NetSync. However, note that running NetSync is memory- and CPU-intensive on the NetWare 4.1 server and CPU-intensive on the NetWare 3.1x servers.  With NetSync running, do not let the cache buffer count drop below 200 (on the 4.1 server) or server utilization rise above 80% (on both 4.1 and 3.1x servers.) You can see server usage of these with the MONITOR utility.RENDERAS="SECT2"SoftwareMARK=BULLETNetSync filesThe necessary files are already on the 4.1 server in the SYS:SYSTEM directory (NetWare 4.1 files) and the SYS:SYSTEM\NETSYNC directory (NetWare 3.1x files). The NetSync files needed by the 3.1x servers will be copied (downloaded) during the installation process.One free licensed connection on the NetWare 4.1 serverA licensed connection is temporarily required while each NetWare 3.1x server in the cluster is authenticated. Once the 3.1x server is authenticated, the licensed connection is freed.PAGENUM=20 ID="BP28"RENDERAS="SECT2"TasksMARK=BULLETClean up duplicate usernames on all NetWare servers that will be part of the NetSync cluster. (See IDREF="FM52736""Managing NetSync Users," page 11.)Make sure the IDXID="w5030"BOOK="_idx" COLLECTION="nw41" TIDREF="i439"
bindery context you want NetWare 3.1x servers to be synchronized with is set on the NetWare 4.1 host. The default bindery context on the NetWare 4.1 host is set to the context where the server is installed.If you have several containers in your bindery context path, any objects NetSync creates will be placed in the first container in the path. For more information about how NetSync deals with bindery context paths, see IDREF="FM27459""Duplicate Names in a Bindery Context Path" on page 58.During installation, NetWare adds the command MOREINFO="NONE"SET BINDERY CONTEXT= MOREINFO="NONE"default to the NetWare 4.1 server's AUTOEXEC.NCF file. Change this bindery context only before you run NetSync. Once NetSync is running, do not change the bindery context.Make sure you have a valid user account and rights to the SYS:SYSTEM directory on all servers you want to install NetSync on.RENDERAS="SECT1"ID="FM47913"Loading IDXID="w5031"BOOK="_idx" COLLECTION="nw41" TIDREF="i2683"IDXID="w5032"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"
NETSYNC4 IDXID="w5033"BOOK="_idx" COLLECTION="nw41" TIDREF="i1828"
on a NetWare 4.1 Server You must load NETSYNC4 on the NetWare 4.1 server and authorize the 3.1x servers before loading NETSYNC3 on the NetWare 3.1x servers. Otherwise, the NetWare 3.1x servers cannot connect to the NetSync cluster.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Load NETSYNC4 on the NetWare 4.1 server. At the NetWare 4.1 server's console, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD NETSYNC4 MOREINFO="NONE"<Enter>IDXID="w5034"BOOK="_idx" COLLECTION="nw41" TIDREF="i2683"
NETSYNC4 autoloads the following 

modules to run properly: CLIB, STREAMS, DSAPI, NWPSRV, and NWSNUT.The SYS:SYSTEM\NETSYNC directory is automatically created during NetWare 4.1 server installation. This directory contains 
PAGENUM=21 ID="BP29"MARK=BULLETNetSync log filesNetSync files that can be copied automatically to the NetWare 3.1x servers in the clusterRENDERAS="SECT1"ID="FM97813"Authorizing a IDXID="w5035"BOOK="_idx" COLLECTION="nw41" TIDREF="i353"IDXID="w5036"BOOK="_idx" COLLECTION="nw41" TIDREF="i2826"
NetWare IDXID="w5037"BOOK="_idx" COLLECTION="nw41" TIDREF="i1828"
3.1x ServerAfter you load NETSYNC4, you must authorize each NetWare 3.1x server that is to use NetSync. This allows these NetWare 3.1x servers to attach to the NetWare 4.1 host. After you load NETSYNC4, a screen similar to the following appears.LABEL="2-1" FLOAT="0"Screen when first load NETSYNC4FILEREF="n41ns05a.tif"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter>.The "Options" menu appears with the "Edit Server List" option selected.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to choose the "Edit Server List" option.
PAGENUM=22 ID="BP30"PERFORMANCE="REQUIRED" To start authorizing individual 3.1
x servers, on a blank line press 
MOREINFO="NONE"<Enter> or 
MOREINFO="NONE"<Ins>.A screen similar to the following appears.LABEL="2-2" FLOAT="0"Authorized Server Information screenFILEREF="n41ns08a.tif"PERFORMANCE="REQUIRED"Enter the name of the NetWare 3.1
x server whose bindery you want to synchronize with the NetWare 4.1 host.PERFORMANCE="REQUIRED"ID="FM26840"Set the NETSYNC 
IDXID="w5038"BOOK="_idx" COLLECTION="nw41" TIDREF="i3251"
password.This is not a user password, but a password that the NetWare 3.1
x server uses to connect to the NetWare 4.1 server. This password is used only for NetSync authorization purposes, to establish the initial NetSync attachment between the NetWare 4.1 host server and the NetWare 3.1
x servers. You specify this password two times:
MARK=BULLETOn this NetWare 4.1 server, you set the password to initially authorize the NetWare 3.1x server. On each NetWare 3.1x server, you specify the same password to initially attach to the NetWare 4.1 server's NetSync cluster. NetSync creates its own randomly generated password after that. (See IDREF="FM56532""Loading NETSYNC3 on a NetWare 3.1x Server," page 26.)You can specify a different NetSync password for each NetWare 3.1
x server. However, the password you set for the 3.1
x server has to match the one you will enter on the NetWare 3.1
x server to attach to the 4.1 server.Therefore, remember the password you are using in this step. If you should forget the password, you must remove this server from the "Authorized 3.1
x Servers" list and re-authorize it, giving it a new password. Once you enter the password on the 3.1
x server and it attaches to the 4.1 server, you won't use the password again. (For more information, see 
IDREF="FM32375""Adding to the List of Authorized Servers," page 37.)
PAGENUM=23 ID="BP31"Do not use the ADMIN or the SUPERVISOR password as the NETSYNC password. Doing this could pose a security risk.PERFORMANCE="REQUIRED"ID="FM96947"To 
IDXID="w5039"BOOK="_idx" COLLECTION="nw41" TIDREF="i2681"
copy NetSync 
IDXID="w5040"BOOK="_idx" COLLECTION="nw41" TIDREF="i848"
files to the NetWare 3.1
x server, press the Down arrow key. Otherwise, press 
MOREINFO="NONE"<Enter> and type "No."This option appears only when you initially authorize a NetWare 3.1x server. If you subsequently edit the server information, you do not receive the option to copy files.The default is Yes. If you are authorizing this NetWare 3.1
x server for the first time, accept the default.This option causes all files necessary for running NetSync to be copied from the NetWare 4.1 server's SYS:SYSTEM\NETSYNC directory to several directories on the NetWare 3.1
x server. For a complete list of files that are copied, look in the file INSTALL.DAT in the SYS:SYSTEM/NETSYNC directory on the 4.1 server.PERFORMANCE="REQUIRED"To copy (upload) 
IDXID="w5041"BOOK="_idx" COLLECTION="nw41" TIDREF="i2826"IDXID="w5042"BOOK="_idx" COLLECTION="nw41" TIDREF="i4691"
bindery 
IDXID="w5043"BOOK="_idx" COLLECTION="nw41" TIDREF="i848"
data 

from the NetWare 3.1
x server to the NetWare 4.1 server, press the Down arrow key. Otherwise, press 
MOREINFO="NONE"<Enter> and type "No."For the initial installation, the default is Yes. Subsequently, the default is No.The bindery data copied includes User and Group objects and their properties.In most cases, answer "Yes." Answer "No" only in two instances:
MARK=BULLETThis server is running NetWare Name Service® (NNS) and you already copied all the domain information to the NetWare 4.1 server when you authorized another NNS® server. (You can still answer "Yes," but the bindery data is discarded because it already exists.)You don't want to upload this server's user and group bindery objects, but you still want this server to be part of the NetSync cluster. In this case, the 3.1x server would be out of sync with the 4.1 server.PERFORMANCE="REQUIRED"To confirm your responses, press 
MOREINFO="NONE"<Esc> and then 
MOREINFO="NONE"<Enter>. PERFORMANCE="REQUIRED"Enter a 
IDXID="w5044"BOOK="_idx" COLLECTION="nw41" TIDREF="i4727"IDXID="w5045"BOOK="_idx" COLLECTION="nw41" TIDREF="i2598"
username for the NetWare 3.1
x server.This username is necessary so that NetSync can log in to the 3.1
x server to copy files to the SYS:SYSTEM and SYS:PUBLIC directories if you answered "Yes" in 
IDREF="FM96947"Step 6 on page 23.
PAGENUM=24 ID="BP32"This user has to have Read, Write, Modify, and Delete rights to the SYS:SYSTEM directory on the NetWare 3.1
x server. The username "SUPERVISOR" is a good choice, but you can choose another username that has these rights.PERFORMANCE="REQUIRED"Enter this user's 
IDXID="w5046"BOOK="_idx" COLLECTION="nw41" TIDREF="i3251"
password.If the files copied successfully, a message similar to the following appears:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Installation of NetSync was successful. NOTE: Some NLMs may have been replaced! It is therefore recommended that server servername be restarted before running NetSync on it. This will ensure that the current versions of the NLMs are loaded. Press <Enter> to continue.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter>. After a short while, the name of the NetWare 3.1
x server you just authorized appears in the "Authorized 3.1
x Servers" box.If this is the first server in the list you have authorized, you are also asked if you want to add commands to the AUTOEXEC.NCF file on the 4.1 server to automatically load NETSYNC4.For each 3.1
x server, you are also asked if you want to add commands to the AUTOEXEC.NCF file on the 3.1
x server to automatically load NETSYNC3.One 

of the following three symbols
IDXID="w5047"BOOK="_idx" COLLECTION="nw41" TIDREF="i11"IDXID="w5048"BOOK="_idx" COLLECTION="nw41" TIDREF="i16"IDXID="w5049"BOOK="_idx" COLLECTION="nw41" TIDREF="i34"IDXID="w5050"BOOK="_idx" COLLECTION="nw41" TIDREF="i307"IDXID="w5051"BOOK="_idx" COLLECTION="nw41" TIDREF="i1369"
 can appear next to the server name in the list.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="5*"COLNAME=2 COLWIDTH="20*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"SymbolCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"*COLNAME=2 ROTATE="0" MOREROWS="0"You are currently attached to this server.COLNAME=1 ROTATE="0" MOREROWS="0"@COLNAME=2 ROTATE="0" MOREROWS="0"This server is currently receiving downloaded bindery information from the NetWare 4.1 hostCOLNAME=1 ROTATE="0" MOREROWS="0"!COLNAME=2 ROTATE="0" MOREROWS="0"This server is currently copying (uploading) information to the NetWare 4.1 host.PERFORMANCE="REQUIRED"To authorize additional NetWare 3.1
x servers to be part of this NetSync cluster, repeat Steps 2 through 10 for each server.
PAGENUM=25 ID="BP33"PERFORMANCE="REQUIRED"(Optional) To configure the NetSync environment on this NetWare 4.1 server, press 
MOREINFO="NONE"<Esc> to activate the "Options" menu.After you have authorized at least one NetWare 3.1
x server, you can access the "Options" menu. For more information, see Chapter 3, 
IDREF="FM68379""Using the NetSync Options Menu," page 31.
PAGENUM=26 ID="BP34"RENDERAS="SECT1"ID="FM56532"Loading NETSYNC3 on a NetWare 3.1x ServerYou IDXID="w5052"BOOK="_idx" COLLECTION="nw41" TIDREF="i2681"IDXID="w5053"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"
must load IDXID="w5054"BOOK="_idx" COLLECTION="nw41" TIDREF="i1828"
NETSYNC3 on each NetWare 3.1x server that you want to synchronize with the NetWare 4.1 host. Make sure NETSYNC4 is already loaded on the NetWare 4.1 server.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Restart each 3.1x server from its console.You need to restart the server because NetWare 4.1 versions of some NetWare modules were copied to the NetWare 3.1
x servers when you ran NETSYNC4. These newer versions will execute, however, only if the old versions are no longer in memory.These modules are replaced by NetWare 4.1 versions:
TYPE="VERT"PSERVER.NLMCLIBSTREAMSNWSNUTAFTER311A3112PBURST (NetWare 3.11 only)Some utilities on the 3.1
x server are also replaced. You can see a list of replaced utilities in the file INSTALL.DAT in the directory SYS:SYSTEM/NETSYNC on the 3.1
x server.For more information on running RCONSOLE, see "
BOOK="superenu" COLLECTION="nw41"Using Remote Console to Manage a Server" in Chapter 7 of 
Supervising the Network.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"At the 3.1
x server, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"DOWN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"At the 3.1
x server, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EXIT MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"At the DOS prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"SERVER MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"At each NetWare 3.1
x server's console type 
PAGENUM=27 ID="BP35"FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD NETSYNC3 [/C] MOREINFO="NONE"<Enter>The /c option lets you load NETSYNC3 without attaching to the NetSync cluster. You can then modify the configuration options without the changes being uploaded to the 4.1 server. This option is useful if you want to delete the configuration options without the 4.1 server running.NETSYNC3 is loaded automatically if you added the command to the AUTOEXEC.NCF file on the 3.1
x server.NETSYNC3.NLM autoloads REMAPID.NLM if it isn't already loaded. IDXID="w5055"BOOK="_idx" COLLECTION="nw41" TIDREF="i2681"
NETSYNC3.NLM also autoloads the following modules: CLIB, STREAMS, NWPSRV3X, NWSNUT, AFTER311, A3112, and PBURST (NetWare 3.11 only).NETSYNC3.NLM and REMAPID.NLM must run continuously. If you had NetSync copy files to the NetWare 3.1x server, NetSync adds the commands to load these modules to the AUTOEXEC.NCF file. REMAPID should never be unloaded, even if you no longer run NetSync and NETSYNC3 is removed from the server.PERFORMANCE="REQUIRED"(Conditional: only if the NetWare 3.1
x server is part of an NNS domain) Select "Yes" and press 
MOREINFO="NONE"<Enter> to remove the server from the NNS domain and load NetSync on the server. Otherwise, select "No" and press 
MOREINFO="NONE"<Enter> to keep the server in the NNS domain and to exit the NETSYNC3 program.For more information on installing NetSync on NNS servers, see 
IDREF="FM29172""NetWare Name Service (NNS) Considerations," page 16.PERFORMANCE="REQUIRED"(Conditional: only if the NetWare 3.1
x server was part of an NNS domain) Select "Yes" and press 
MOREINFO="NONE"<Enter> to convert NNS replicated (fake) print queues to real queues. Select "No" and press 
MOREINFO="NONE"<Enter> to delete the fake queues.For more information on converting NNS print queues with NetSync, see 
IDREF="FM70522""Upgrading NetWare Name Service (NNS) Printing," page 52.PERFORMANCE="REQUIRED"(Conditional: only if the NetWare 3.1
x server was part of an NNS domain and you chose to convert fake print queues to real queues) Select "Yes" and press 
MOREINFO="NONE"<Enter> to rebuild NNS printing so it works in NetSync. Select "No" and press 
MOREINFO="NONE"<Enter> to leave NNS printing alone.For more information on upgrading NNS printing with NetSync, see 
IDREF="FM70522""Upgrading NetWare Name Service (NNS) Printing," page 52.
PAGENUM=28 ID="BP36"PERFORMANCE="REQUIRED"(Conditional: only when you first load NETSYNC3 on this server) 
IDXID="w5056"BOOK="_idx" COLLECTION="nw41" TIDREF="i2675"
Enter the name of the NetWare 4.1 host that you want this NetWare 3.1
x server to synchronize with at the following prompt:
FORMAT="LINESPECIFIC"MOREINFO="NONE"4.1 Server Name: PERFORMANCE="REQUIRED"(Conditional: only when you first load NETSYNC3 on this server) Enter the NETSYNC 
IDXID="w5057"BOOK="_idx" COLLECTION="nw41" TIDREF="i3251"
password.For more information on the NetSync password, see 
IDREF="FM26840"Step 5 on page 22.NetSync now copies (uploads) NetWare 3.1
x bindery information to the NetWare 4.1 bindery context and downloads that bindery context to this NetWare 3.1
x server.From this point on, do not use SYSCON to modify user and group information on NetWare 3.1x servers in the NetSync cluster. If you do, your servers will be out of sync. Use only NETADMIN or NetWare Administrator.The "Options" menu appears.PERFORMANCE="REQUIRED"(Optional) Configure the NetSync environment on the NetWare 3.1
x server.For more information, see Chapter 3, 
IDREF="FM68379""Using the NetSync Options Menu," page 31.PERFORMANCE="REQUIRED"(Optional) Verify that all information is synchronized.You can perform some spot checks with the NetWare administrative utilities. (NetWare Administrator or NETADMIN for NetWare 4.1; SYSCON for NetWare 3.1
x.)
MARK=BULLETLog in to a server in the NetSync cluster and verify that you can see all users in the cluster. Create a user from the NetWare 4.1 server and see how this user is synchronized across the cluster.For more information see "BOOK="utlrfenu" COLLECTION="nw41"NETADMIN" in Utilities Reference and "BOOK="utlrfenu" COLLECTION="nw41"NetWare Administrator" in Utilities Reference.PAGENUM=29 ID="BP37"RENDERAS="SECT1"Where to Go from HereCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"ReferenceVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Using the "Options" menu to view the log file, etc.COLNAME=2 ROTATE="0" MOREROWS="0"Chapter 3, IDREF="FM68379""Using the NetSync Options Menu," page 31"Using the NetSync Options Menu," page 31COLNAME=1 ROTATE="0" MOREROWS="0"Moving print services to the NetWare 4.1 serverCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 4, IDREF="FM47705""Printing Support for NetSync," page 41"Printing Support for NetSync," page 41COLNAME=1 ROTATE="0" MOREROWS="0"Technical issues concerning NetSyncCOLNAME=2 ROTATE="0" MOREROWS="0"Appendix A, IDREF="FM80893""NetSync Issues," page 57"NetSync Issues," page 57LABEL="3"PAGENUM=31 ID="BP38"ID="FM68379"Using the NetSync Options MenuThe "Options" menu of NETSYNC3 and NETSYNC4 lets you IDXID="w5058"BOOK="_idx" COLLECTION="nw41" TIDREF="i765"IDXID="w5059"BOOK="_idx" COLLECTION="nw41" TIDREF="i2680"
configure your NetSync environment in detail. You can perform most tasks on both NetWare 4.1 and 3.1x servers. Exceptions are noted under the task headings in this chapter.RENDERAS="SECT1"NETSYNC4 Menu OptionsAfter you authorize at least one NetWare 3.1x server (see IDREF="FM97813""Authorizing a NetWare 3.1x Server," page 21), you can access the NETSYNC4 "Options" menu by pressing MOREINFO="NONE"<Esc>. Subsequently, whenever you load NETSYNC4, the first thing you see is this menu.Following is the main "Options" menu on the NetWare 4.1 server:FILEREF="n41ns06a.tif"PAGENUM=32 ID="BP39"RENDERAS="SECT1"ID="FM63100"NETSYNC3 Menu OptionsAfter you initially attach to a NetWare 4.1 host, the NETSYNC3 "Options" menu appears. Subsequently, when you load NETSYNC3, the first thing you see is this menu.Following is the main "Options" menu on the NetWare 3.1x server:FILEREF="n41ns14a.tif"For more information on moving print servers, see Chapter 4, IDREF="FM47705""Printing Support for NetSync," page 41.RENDERAS="SECT1"Managing the NetSync 
Log FileOn each NetWare 4.1 and 3.1x server, the log file is called NETSYNC.LOG and is located in SYS:SYSTEM\NETSYNC. The NetSync log file can show all synchronization events that occur. Such events include the following:MARK=BULLETAdded, deleted, or changed users or groupsPassword changesLogins (attachments) to and logouts (detachments) from NetSync serversLogin script changesSuccess or failure of local modification attemptsItems queued to be sent to other serversThe following illustration shows a partial log file.PAGENUM=33 ID="BP40"LABEL="3-1" FLOAT="0"Sample NetSync log screenFILEREF="n41ns10a.tif"RENDERAS="SECT2"ID="FM20159"Viewing the Log FileOn a NetWare 3.1x server, you can view the IDXID="w5060"BOOK="_idx" COLLECTION="nw41" TIDREF="i2676"
log file only by using a workstation text editor.On a NetWare 4.1 server, you can use either a workstation text editor or the following procedure to view the log file. RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Options" menu, select "Log File Options."PERFORMANCE="REQUIRED"Select "View Log File History."This allows you to scroll the log file. You can go back and look at previous events that have occurred.
PAGENUM=34 ID="BP41"If there is not a large block of contiguous memory, this option might sometimes fail, even if you have a large amount of "free" memory. If this option fails, use a workstation editor to view the log file.PERFORMANCE="REQUIRED"To scroll through the file, use the arrow or paging keys.PERFORMANCE="REQUIRED"To exit the display, press 
MOREINFO="NONE"<Esc>.RENDERAS="SECT2"Viewing the Active Log DisplayPERFORMANCE="REQUIRED"From the "Options" menu, select "View Active Log."This allows you to view, but not scroll or edit, the 
IDXID="w5061"BOOK="_idx" COLLECTION="nw41" TIDREF="i2676"
log file. This screen scrolls as events occur, showing real-time updates.PERFORMANCE="REQUIRED"To exit the display, press 
MOREINFO="NONE"<Esc>.RENDERAS="SECT2"ID="FM69293"Changing the Size of the Log FileThe default IDXID="w5062"BOOK="_idx" COLLECTION="nw41" TIDREF="i2676"
size of the log file is 0.5 MB, the range is from 10 KB (10240 bytes) to 10 MB (10485760 bytes).You can make the log file smaller to have it take up less disk space. Or, if you want more events to be included in the current file, you can increase its size. If the file is too large, you might not be able to view it.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Options" menu, select "Log File Options."PERFORMANCE="REQUIRED"Select "Maximum Size of Log File."PERFORMANCE="REQUIRED"Type the new size of the log file in bytes and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"To exit "Log File Options," press 
MOREINFO="NONE"<Esc>.RENDERAS="SECT2"ShowingIDXID="w5063"BOOK="_idx" COLLECTION="nw41" TIDREF="i2680"IDXID="w5064"BOOK="_idx" COLLECTION="nw41" TIDREF="i3964"IDXID="w5065"BOOK="_idx" COLLECTION="nw41" TIDREF="i1364"IDXID="w5066"BOOK="_idx" COLLECTION="nw41" TIDREF="i1150"
 Events on the IDXID="w5067"BOOK="_idx" COLLECTION="nw41" TIDREF="i2184"
Log ScreenThe "Show All Events on Log Screen" option influences whether all events or only major events and failed operations show up on the active log screen. PAGENUM=35 ID="BP42"However, if the log file is enabled, all events are still recorded in the log file for history purposes.The default is "No" (don't show all events)."Expected" failures, such as adding a property to an object when that property already exists, are not shown on the log screen when the option is set to "No."RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Options" menu, select "Log File Options."PERFORMANCE="REQUIRED"Select "Show All Events on Log Screen."PERFORMANCE="REQUIRED"To show all events, type "Yes". Otherwise, type "No".Changing this option to "Yes" causes all events, instead of only major events and failed operations, to appear on the active log screen. PERFORMANCE="REQUIRED"To save your changes, press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"To exit the "Log File Options" menu, press 
MOREINFO="NONE"<Esc>.RENDERAS="SECT2"Deleting the Log File You can IDXID="w5068"BOOK="_idx" COLLECTION="nw41" TIDREF="i990"IDXID="w5069"BOOK="_idx" COLLECTION="nw41" TIDREF="i2676"
delete the log file when you MARK=BULLETRemove NetSync from the serverWant to delete old log information to be able to start with a new log fileIf you delete the log file, a new file is automatically created to log new NetSync data.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Options" menu, select "Log File Options."PERFORMANCE="REQUIRED"Select "Delete Current Log File."PERFORMANCE="REQUIRED"Delete the log file by typing "Y" and pressing 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"To exit the "Log File Options" menu, press 
MOREINFO="NONE"<Esc> 
PAGENUM=36 ID="BP43"PERFORMANCE="REQUIRED"Highlight "Yes" or "No" and press 
MOREINFO="NONE"<Enter> to confirm your choice.RENDERAS="SECT2"ID="FM13051"Disabling the Log FileThis option prevents a log file from being created. You could IDXID="w5070"BOOK="_idx" COLLECTION="nw41" TIDREF="i1103"IDXID="w5071"BOOK="_idx" COLLECTION="nw41" TIDREF="i2676"
disable the log file if MARK=BULLETNetSync has run smoothly for some timeYou want to make your system run a bit more efficiently by eliminating the overhead that a log file createsThe default is "Yes," meaning that the log file is enabled and gets created by default.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Options" menu, select "Log File Options."PERFORMANCE="REQUIRED"Select "Enable Log File."PERFORMANCE="REQUIRED"Disable the log file by typing "N" and pressing 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"To exit the "Log File Options" menu, press 
MOREINFO="NONE"<Esc>.RENDERAS="SECT2"ID="FM42145"Disabling the Synchronization of 3.1x Login Scripts with 4.1 Login ScriptsYou can IDXID="w5072"BOOK="_idx" COLLECTION="nw41" TIDREF="i2212"
perform this task only in NETSYNC4.Synchronization of 3.1x login scripts with 4.1 login scripts allows users logging in through bindery services to still have a login script on the NetWare 4.1 server. The default is "Yes." You can choose to not have this synchronization take place. For more information, see IDREF="FM49544""User Login Scripts," page 15.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Options" menu, select "Configuration Options."PERFORMANCE="REQUIRED"Select "Synchronize Login Script Updates to Mail Dir:."
PAGENUM=37 ID="BP44"PERFORMANCE="REQUIRED"Disable the synchronization of login scripts to the mail directory on the NetWare 4.1 server by typing "N" and pressing 
MOREINFO="NONE"<Enter>.Login scripts are always synchronized to the 3.1
x servers mail directory.PERFORMANCE="REQUIRED"To save your changes, press 
MOREINFO="NONE"<Enter>.RENDERAS="SECT2"Changing the Watchdog Delay IntervalIn NETSYNC4 (on the NetWare 4.1 host), the IDXID="w5073"BOOK="_idx" COLLECTION="nw41" TIDREF="i4817"
watchdog delay interval determines how often the NetWare 3.1x servers in the cluster are checked for proper operation.In NETSYNC3 (on the NetWare 3.1x servers in the cluster), the watchdog delay interval determines how often the NetWare 4.1 host is checked for proper operation.The default interval is five minutes, and the range is from 30 seconds to 64800 seconds (18 hours).RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Options" menu, select "Configuration Options."PERFORMANCE="REQUIRED"Select "Watchdog Delay Interval."PERFORMANCE="REQUIRED"Enter the interval in seconds.PERFORMANCE="REQUIRED"Press <Enter>.RENDERAS="SECT1"Managing the List of Authorized NetWare 3.1x ServersAuthorized NetWare servers are those NetWare 3.1x servers that are authorized to attach to the NetWare 4.1 host and, thus, are part of the NetSync cluster.RENDERAS="SECT2"ID="FM32375"Adding to the List of Authorized ServersYou can perform this task only in NETSYNC4.PAGENUM=38 ID="BP45"To replace a server on the list with another, first delete the server you are replacing. Then add the new server to the blank spot on the list. You IDXID="w5074"BOOK="_idx" COLLECTION="nw41" TIDREF="i2826"
authorize most servers during NetSync installation (see IDREF="FM97813""Authorizing a NetWare 3.1x Server," page 21.)Add servers to the NetSync cluster by following this procedure.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED" At the NetWare 4.1 server console, load NETSYNC4.PERFORMANCE="REQUIRED"From the "Options" menu, select "Edit Server List."PERFORMANCE="REQUIRED"Highlight an empty slot and type the servername, or press 
MOREINFO="NONE"<Ins> or 
MOREINFO="NONE"<Enter>.Do not change a server name in this list unless the name of the actual server has changed.PERFORMANCE="REQUIRED"Complete steps 3 through 9 under 
IDREF="FM97813""Authorizing a NetWare 3.1x Server," page 21.PERFORMANCE="REQUIRED"To confirm your changes, press 
MOREINFO="NONE"<Enter>.RENDERAS="SECT2"Deleting from the List of Authorized ServersYou can perform this task only in NETSYNC4.IDXID="w5075"BOOK="_idx" COLLECTION="nw41" TIDREF="i990"IDXID="w5076"BOOK="_idx" COLLECTION="nw41" TIDREF="i2826"
Deleting a 
server from the list of Authorized Servers removes the server from the NetSync cluster.You can remove servers only one at a time.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Options" menu, select "Edit Server List."PERFORMANCE="REQUIRED"Highlight the NetWare 3.1
x server you want to delete and press 
MOREINFO="NONE"<Delete>.RENDERAS="SECT2"ID="FM45212"Copying a IDXID="w5077"BOOK="_idx" COLLECTION="nw41" TIDREF="i848"
NetWare 3.1x Server's Bindery to NetWare 4.1You can perform this task only in NETSYNC4.PAGENUM=39 ID="BP46"You can IDXID="w5078"BOOK="_idx" COLLECTION="nw41" TIDREF="i4691"
manually 
copy (upload) a NetWare 3.1x server's bindery to the NetWare 4.1 bindery context if the NetWare 3.1x server is out of sync. This could happen under the following circumstances:MARK=BULLETYou made changes to user and group information on the NetWare 3.1x server using SYSCON. Changes made in SYSCON are not synchronized with the NetWare 4.1 server's bindery context.You ran a program on the NetWare 3.1x server that modified its bindery.You authorized a 3.1x server, but it never joined the NetSync cluster during the NETSYNC4 session you authorized it in. This could happen if you unload and reload NETSYNC4 before loading NETSYNC3 for the first time on an authorized 3.1x server.When NETSYNC4 is unloaded, it clears the "Copy 3.1x bindery to 4.1" setting for each 3.1x server. Therefore, you must turn on the "Copy 3.1x bindery to 4.1" setting again before you load NETSYNC3 on the 3.1x server so the bindery is copied to the 4.1 server.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Options" menu, select "Edit Server List."PERFORMANCE="REQUIRED"Highlight the NetWare 3.1
x server whose bindery you want to upload and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Highlight the "Copy 3.1
x bindery to 4.1" option and press 
MOREINFO="NONE"<Y> to toggle to "Yes."If you unload and reload NETSYNC4 for any reason, this option is cleared for all servers. You need to change this option to "Yes" for any 3.1
x servers that have not yet copied their binderies to the 4.1 server.PERFORMANCE="REQUIRED"To save the change, press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"To exit the "Edit Server List" menu, press 
MOREINFO="NONE"<Esc>.PERFORMANCE="REQUIRED"To confirm the change, highlight "Yes" and press 
MOREINFO="NONE"<Enter>.All bindery information is copied, but only new information is added to the NetWare 4.1 server's bindery context. Duplicate information is discarded.
PAGENUM=40 ID="BP47"RENDERAS="SECT1"Deleting NetSync Configuration Data IDXID="w5079"BOOK="_idx" COLLECTION="nw41" TIDREF="i740"IDXID="w5080"BOOK="_idx" COLLECTION="nw41" TIDREF="i990"IDXID="w5081"BOOK="_idx" COLLECTION="nw41" TIDREF="i2680"IDXID="w5082"BOOK="_idx" COLLECTION="nw41" TIDREF="i934"Configuration 
data includes the following:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"On the NetWare 4.1 hostCOLNAME=2 ROTATE="0" MOREROWS="0"On the NetWare 3.1x serverVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Names of authorized NetWare 3.1x servers and associated passwordsCOLNAME=2 ROTATE="0" MOREROWS="0"Name of NetWare 4.1 hostCOLNAME=1 ROTATE="0" MOREROWS="0"NetSync passwordCOLNAME=2 ROTATE="0" MOREROWS="0"NetSync passwordYou can delete NetSync configuration from a NetWare 3.1x server if the serverMARK=BULLETIs going to join a different NetSync clusterIs not going to run NetSync any moreThe default is to not delete the configuration data ("No").RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"From the "Options" menu, select "Configuration Options."PERFORMANCE="REQUIRED"Select "Delete NetSync Configuration Data."PERFORMANCE="REQUIRED"Delete the configuration data by typing "Y."PERFORMANCE="REQUIRED"To save the change, press
MOREINFO="NONE" <Enter>.PERFORMANCE="REQUIRED"To exit the "Configuration Options" menu, press 
MOREINFO="NONE"<Esc>.PERFORMANCE="REQUIRED"To confirm the change, highlight "Yes" and press 
MOREINFO="NONE"<Enter>.LABEL="4"PAGENUM=41 ID="BP48"ID="FM47705"Printing Support for NetSyncRENDERAS="SECT1"OverviewNetSync IDXID="w5083"BOOK="_idx" COLLECTION="nw41" TIDREF="i3553"IDXID="w5084"BOOK="_idx" COLLECTION="nw41" TIDREF="i2680"
printing support consists of two parts.MARK=BULLETAutomatic processes that happen when you run NETSYNC3 on your NetWare® 3.1x server (after you load NETSYNC4 on the NetWare 4.1 server):MARK=BULLETAll NetWare 4.1 workstation print utilities are copied to the NetWare 3.1x servers.IDXID="w5085"BOOK="_idx" COLLECTION="nw41" TIDREF="i3474"
PRINTCON and IDXID="w5086"BOOK="_idx" COLLECTION="nw41" TIDREF="i3486"
PRINTDEF databases are updated to NetWare 4.1 format and duplicated in the NetWare 4.1 database. Subsequent changes made in PRINTDEF and PRINTCON on the 4.1 server are copied to the 3.1x servers.NetWare Name Service® (NNS) printing is not fully supported by NetSync. If you attempt to upgrade an NNS® server using NetSync, certain printing configurations will not be upgraded completely. For more information on converting NNS printing to NetSync, see IDREF="FM70522""Upgrading NetWare Name Service (NNS) Printing" on page 52.Optional tasks you can perform in NetSync:You can move your NetWare 3.1x print servers by merging them into one print server on the NetWare 4.1 server. This process also places your printers into the NetWare 4.1 Directory where they can be managed from a single NetWare 4.1 print server.RENDERAS="SECT1"Upgrading of 
Utilities IDXID="w5087"BOOK="_idx" COLLECTION="nw41" TIDREF="i3393"IDXID="w5088"BOOK="_idx" COLLECTION="nw41" TIDREF="i3473"
and 
DatabasesWhen you run NETSYNC3 on your NetWare 3.1x server (after you load NETSYNC4 on the NetWare 4.1 server), your NetWare 3.1xPAGENUM=42 ID="BP49" print utilities and databases are upgraded automatically regardless of whether you move print servers. With NetSync, Directory Services-based print queues synchronize with NetWare 3.1x servers. This applies only to print queues that existed on 3.1x servers and were uploaded to the 4.1 server during the synchronization process. New queues created on the 4.1 server are not synchronized with the 3.1x servers.RENDERAS="SECT2"Using NetWare 4.1 Print IDXID="w5089"BOOK="_idx" COLLECTION="nw41" TIDREF="i3473"
Utilities in Your 3.1x EnvironmentYou can use the new NetWare 4.1 print utilities immediately in your NetWare 3.1x environment. All NetWare 4.1 print utilities copied to your NetWare 3.1x server are compatible with your NetWare 3.1x setup. The utilities copied are IDXID="w5090"BOOK="_idx" COLLECTION="nw41" TIDREF="i3473"
CAPTURE, NPRINT, NPRINTER (.NLM and .EXE), PCONSOLE, PRINTCON, PRINTDEF, and PSC. All support files needed for these utilities are copied as well.After running NetSync, load the NetWare 4.1 NPRINTER.EXE utility on all workstations that currently use RPRINTER. You should make this change even if you do not move print servers to the NetWare 4.1 server.To run printers attached to the 3.1x servers after moving print servers to the NetWare 4.1 server, unload PSERVER.NLM on the 3.1x servers, load PSERVER.NLM on the NetWare 4.1 host server, and load NPRINTER.NLM on the 3.1x servers. For more information, see "BOOK="printenu" COLLECTION="nw41"Using NPRINTER.NLM" in Chapter 7 of Print Services.RENDERAS="SECT2"Using NetWare 4.1 Print IDXID="w5091"BOOK="_idx" COLLECTION="nw41" TIDREF="i3393"
Databases on Your 3.1x EnvironmentNetWare 3.1x printing databases created using PRINTCON and PRINTDEF are synchronized with the NetWare 4.1 server. PRINTDEF databases are then copied back to all the NetWare 3.1x servers in the NetSync cluster.In the case of duplicate information from different servers, such as duplicate print job names or duplicate print device modes, only the information that is synchronized to the NetWare 4.1 server first will be retained.PAGENUM=43 ID="BP50"For example, if user JAMES has PRINTJOB1 defined in his PRINTCON.DAT file on two NetWare 3.1x servers in the NetSync cluster, PRINTJOB1 on the first synchronized server will be retained in the new printing configuration. PRINTJOB1 on the second server will be discarded.After synchronization has been completed, you should always make changes to the NetWare 4.1 print databases on the NetWare 4.1 server using NetWare 4.1 utilities. Changes made on a NetWare 3.1x server will not be synchronized with the NetWare 4.1 server and the other NetWare 3.1x servers. RENDERAS="SECT1"Moving IDXID="w5092"BOOK="_idx" COLLECTION="nw41" TIDREF="i3465"
Print ServersBy using NetSync to move your NetWare 3.1x print servers, you can merge the print resources of up to 12 NetWare 3.1x servers with the NetWare 4.1 Directory, allowing all printing to be administered from a single NetWare 4.1 host server. In some cases, NetSync does not fully upgrade printing configurations from NetWare Name Service (NNS) servers. You might need to complete additional steps to upgrade NNS printing. For more information on converting NNS printers to NetSync, see IDREF="FM70522""Upgrading NetWare Name Service (NNS) Printing" on page 52.When you move NetWare 3.1x print servers, configuration information for those print servers and their associated printers and queues is transferred to the NetWare 4.1 print server into which they are being merged.Since PSERVER.NLM can be loaded only once, and PSERVER.EXE no longer exists in NetWare 4TM software, all NetWare 3.1x print servers must be merged when you move them to the NetWare 4.1 server. This requires you to make configuration changes to your printing setup. For example, printer numbers might need to be reassigned.Under the new configuration, NPRINTER.EXE takes the place of both PSERVER.EXE and RPRINTER.EXE.RENDERAS="SECT2"When to Use NetSync to Move Print ServersMoving print servers with NetSync can be a useful process in relatively large or complex printing environments where the move from NetWare 3.1x to NetWare 4.1 must be implemented gradually. PAGENUM=44 ID="BP51"For example, if you have numerous print queue operators or lengthy lists of queue users, and you don't want to re-enter this information for a NetWare 4.1 configuration yet, using NetSync can be a valuable interim step in your move to NetWare 4.1. Some manual reconfiguration is required in your printing setup as part of the NetWare synchronization process. Even if your printing setup relies primarily on default settings, such as group EVERYONE, and you use a modest number of printers (perhaps a dozen or fewer), you might find it easier to use NetSync to move print servers than setting up printing manually on the NetWare 4.1 server.RENDERAS="SECT2"General Guidelines for Moving IDXID="w5093"BOOK="_idx" COLLECTION="nw41" TIDREF="i3465"
Print ServersWith NetSync, you move each NetWare 3.1x print server to the NetWare 4.1 server as needed. NetSync allows you to move multiple print servers that were previously in NetWare 3.1x and merge them into a single NetWare 4.1 print server. You specify the name of each NetWare 3.1x print server that you want to move, and then complete the process of moving it before you move the next print server. (The procedure for moving print servers is found on IDREF="FM19746"page 46.)When you move a NetWare 3.1x print server, all properties and associated printer configurations are moved intact; you cannot move them selectively. You can, however, change or delete these properties after they are moved. The first print server you move retains the configuration information it had in NetWare 3.1x, including printer numbers. But when you move additional print servers to the same NetWare 4.1 print server, the printer numbers might conflict with printer numbers assigned on that print server. In this case, NetSync assigns new numbers to these new printers. You can move multiple NetWare 3.1x print servers to multiple NetWare 4.1 print servers or incorporate them into a single print server. For example, you could move 11 NetWare 3.1x print servers to NetWare 4.1, incorporating six 3.1x print servers into print server SALES_PS on NetWare server SALES and the other five into print server ACCOUNTS_PS on NetWare server ACCOUNTS.PAGENUM=45 ID="BP52"IDXID="w5094"BOOK="_idx" COLLECTION="nw41" TIDREF="i3465"
This is illustrated in the following figure.LABEL="4-1" FLOAT="0"Merging multiple 3.1x print servers into one 4.1 print serverFILEREF="n41ns13a.tif"To move print servers from a single NetWare 3.1x server to multiple NetWare 4.1 servers contained in more than one container, you must load NETSYNC4 on a NetWare 4.1 server in each container.There is no limit to the IDXID="w5095"BOOK="_idx" COLLECTION="nw41" TIDREF="i3465"
number of NetWare 3.1x print servers you can move to a single NetWare 4.1 print server, provided the total number of printers administered through the NetWare 4.1 print server does not exceed 255.You can move print servers from the NetWare 3.1x servers to more than one NetWare 4.1 server. You can even move print servers from a single 3.1x server to more than one NetWare 4.1 server. However, you must load NETSYNC4 on each 4.1 server. PAGENUM=46 ID="BP53"NetWare 3.1x print servers that you do not move must be administered through PCONSOLE. (The NetWare 4.1 NetWare Administrator utility cannot be used for this purpose.) RENDERAS="SECT2"Procedure for 
Moving IDXID="w5096"BOOK="_idx" COLLECTION="nw41" TIDREF="i3465"
Print ServersNetSync files are loaded automatically in the AUTOEXEC.NCF file for your NetWare 3.1x and NetWare 4.1 servers to ensure normal operation.The following procedure explains how to move a NetWare 3.1x print server and its configuration information, including associated printers, to a NetWare 4.1 server.RENDERAS="SECT3"ID="FM19746"ProcedurePERFORMANCE="REQUIRED"Load NETSYNC4 on your NetWare 4.1 server.See 
IDREF="FM47913""Loading NETSYNC4 on a NetWare 4.1 Server" on page 20.PERFORMANCE="REQUIRED"Load NETSYNC3 on your NetWare 3.1
x server.See 
IDREF="FM56532""Loading NETSYNC3 on a NetWare 3.1x Server" on page 26.The following NetSync "Options" menu is displayed.

FILEREF="n41ns14a.tif"PERFORMANCE="REQUIRED"From the "Options" menu, choose "Move a Print Server."If two or more print servers are available, the following "Choose A Print Server to Move" window appears.PAGENUM=47 ID="BP54"FILEREF="n41ns04a.tif"If only one print server is available to be moved, that server is selected by default and the window does not appear. Continue with Step 5.PERFORMANCE="REQUIRED"Select the name of the print server you want to move to the NetWare 4.1 server.After a print server is moved to NetWare 4.1, it no longer exists as a candidate for synchronization, so it will not appear on the list of print servers to choose from.PERFORMANCE="REQUIRED"ID="FM63140"At the prompt, type the name you want to assign to the 
IDXID="w5097"BOOK="_idx" COLLECTION="nw41" TIDREF="i3458"
print server you are moving to the NetWare 4.1 server.You can use the name already assigned to the print server or assign a different name to it. The default is to use the name already assigned to the NetWare 3.1
x print server, with no merging of print servers occurring.
MARK=BULLETIf you assign a print server name that already exists on the NetWare 4.1 server, the 3.1x print server is merged into it.The 3.1x password is deleted. (The password for the NetWare 4.1 print server is not affected by incorporating additional NetWare 3.1x print servers into it.)If you assign a print server name that does not already exist on the NetWare 4.1 server, a NetWare 4.1 print server object is created with that name. The new NetWare 4.1 print server is not assigned a password. You should assign a password to the new NetWare 4.1 print server.RENDERAS="SECT2"Moving IDXID="w5098"BOOK="_idx" COLLECTION="nw41" TIDREF="i2529"IDXID="w5099"BOOK="_idx" COLLECTION="nw41" TIDREF="i3523"
Printers Printers are moved along with their associated print servers as part of the process of moving print servers.PAGENUM=48 ID="BP55"In NetWare 3.1x, printers exist as properties of print servers. In NetWare 4.1, printers exist as objects in the Directory Services database. A new Printer object is created automatically in the NetWare 4.1 Directory for each printer moved from a NetWare 3.1x print server.This allows you to manage each printer in your NetSync environment with the NetWare 4.1 utilities.RENDERAS="SECT3"Printer ConfigurationsIDXID="w5100"BOOK="_idx" COLLECTION="nw41" TIDREF="i3523"
Printer configurations are not changed while the print server is being moved.A printer servicing multiple queues is moved in the same way as is a printer servicing a single queue. It still services the same queues as before.Printers configured as local on the NetWare 3.1x print server are configured as "Manual Load" (remote) printers in NetWare 4.1.Printers you want to attach directly to a NetWare 4.1 print server can be reconfigured as "Auto Load (Local)" printers.Notification lists for each moved printer return to the default, which is the job owner. To add users to the notification list, use NetWare Administrator or PCONSOLE on the NetWare 4.1 server.RENDERAS="SECT3"ID="FM95455"Printer IDXID="w5101"BOOK="_idx" COLLECTION="nw41" TIDREF="i2598"
Name SynchronizationNetSync reconciles duplicate printer names when print servers are moved to NetWare 4.1.If the printer name duplicates a name that already exists in the NetWare 4.1 bindery context, the IDXID="w5102"BOOK="_idx" COLLECTION="nw41" TIDREF="i3523"
name assigned to the printer being synchronized (one being moved from the NetWare 3.1x bindery to NetWare 4.1 bindery services or the super-bindery) is modified. In this case, the synchronized printer has a numerical suffix assigned to its name to differentiate it from the first printer. For example, a duplicate printer "MY_PRINTER" would become "MY_PRINTER-001."RENDERAS="SECT3"New IDXID="w5103"BOOK="_idx" COLLECTION="nw41" TIDREF="i3523"
Printer NumbersDuplicate printer numbers are reconciled along with printer names during the NetSync process.PAGENUM=49 ID="BP56"The first print server you move retains the configuration information it had in NetWare 3.1x, including printer numbers. But when you move additional print servers to the same NetWare 4.1 print server, the printer numbers might conflict with printer numbers assigned on that print server. In this case, NetSync assigns new numbers to these new printers. To determine this new number, use PCONSOLE or NetWare Administrator. NPRINTER must use the new print server and printer number. You might need to change the printer number at workstations that will be loading NPRINTER.EXE.RENDERAS="SECT2"Status of 3.1x Queues during SynchronizationIn most cases, IDXID="w5104"BOOK="_idx" COLLECTION="nw41" TIDREF="i3390"IDXID="w5105"BOOK="_idx" COLLECTION="nw41" TIDREF="i2001"
print jobs remaining in a queue while the printer is being moved to NetWare 4.1 continue printing because they still have access to the queue and the print server is still running.However, if possible, avoid moving print servers when printing is going on.RENDERAS="SECT1"Managing IDXID="w5106"BOOK="_idx" COLLECTION="nw41" TIDREF="i3458"
Print Servers IDXID="w5107"BOOK="_idx" COLLECTION="nw41" TIDREF="i2326"
after SynchronizationAfter moving your NetWare 3.1x print servers to NetWare 4.1, you can manage your NetWare 4.1 print servers the same way as you did before. This section describes modifications that occur in your print server configurations following the NetSync process that can help you better manage your print services.After the NetSync process is completed, in most cases you should unload the NetWare 3.1x print servers whose configurations were moved to NetWare 4.1. RENDERAS="SECT2"Reference Print 
Servers Created to Service 3.1x Queues When you move a print server to NetWare 4.1 and, in the process, assign a new name to it, a reference print server by that name is simultaneously created on the NetWare 3.1x file server. This new reference print server is a bindery object through which the NetWare 4.1 print server attaches so it can service queues on the 3.1x server. PAGENUM=50 ID="BP57"This new reference print server on the NetWare 3.1x server has no assigned properties or resources (such as printers) and it does not need to be loaded. However, it is listed on the print server list in PCONSOLE and NetWare Administrator. Do not delete this reference print server from the NetWare 3.1x server for any reason. If there is no print server on the NetWare 3.1x server with a name matching the name of the NetWare 4.1 print server, the NetWare 4.1 print server cannot log in to the NetWare 3.1x server, and queues on the NetWare 3.1x server cannot be serviced.  If you delete this reference print server from the NetWare 3.1x server, you cannot recreate it by running NetSync again. Instead use NetWare 3.1x PCONSOLE to create it again and then reattach each queue to the print server.Because the new reference print server is created by NetSync and the NetWare 4.1 print server logs in to the NetWare 3.1x server automatically, none of this should require any action on your part. RENDERAS="SECT2"Print Server IDXID="w5108"BOOK="_idx" COLLECTION="nw41" TIDREF="i3458"IDXID="w5109"BOOK="_idx" COLLECTION="nw41" TIDREF="i3097"
OperatorsAll designated operators of NetWare 3.1x print servers moved to NetWare 4.1 are automatically made operators of the NetWare 4.1 print server after being moved. This can have security implications for your network. If you do not want many print server operators on your NetWare 4.1 network, change the operator assignments after synchronization is completed.RENDERAS="SECT2"Users and GroupsA IDXID="w5110"BOOK="_idx" COLLECTION="nw41" TIDREF="i3458"
user or group assigned as a member of the Users property of a NetWare 3.1x print server being moved to a NetWare 4.1 print server is automatically a user or group of the NetWare 4.1 print server. However, NetWare 4.1 users and groups do not synchronize with the 3.1x reference print server.RENDERAS="SECT1"ID="FM23132"Managing IDXID="w5111"BOOK="_idx" COLLECTION="nw41" TIDREF="i3442"IDXID="w5112"BOOK="_idx" COLLECTION="nw41" TIDREF="i3442"
Print 
Queues IDXID="w5113"BOOK="_idx" COLLECTION="nw41" TIDREF="i2326"
after SynchronizationYou can use NetWare Administrator and PCONSOLE from the NetWare 4.1 server to perform system administration on bindery queues existing on NetWare 3.1xPAGENUM=51 ID="BP58" servers. By making the changes on the NetWare 4.1 host server, the changes are also made in the corresponding print queues on the 3.1x servers. You can add or delete print queues on the 4.1 or the 3.1x servers, depending on the desired result.If you delete a print queue on the NetWare 4.1 server, the corresponding print queue on the 3.1x servers is also deleted. If you delete a print queue on a 3.1x server, however, only the queue on that server is deleted. The corresponding queue on the NetWare 4.1 server remains intact, as do the queues on the other 3.1x servers.If you add a print queue on the NetWare 4.1 server, that queue is created only on the 4.1 server. To access that print queue from the 3.1x servers in the NetSync cluster, use a bindery reference queue on the 4.1 server or add the server reference to your capture statement.Remember, to submit jobs to a queue on a particular NetWare 3.1x server, you must be designated as a user of that queue in the NetWare 4.1 Queue object. In most NetWare 3.1x print configurations, group IDXID="w5114"BOOK="_idx" COLLECTION="nw41" TIDREF="i1615"IDXID="w5115"BOOK="_idx" COLLECTION="nw41" TIDREF="i3442"
EVERYONE is included by default as a queue user. As a result, because NetSync merges all EVERYONE groups, all users are designated users of all queues.RENDERAS="SECT2"Bindery Reference IDXID="w5116"BOOK="_idx" COLLECTION="nw41" TIDREF="i3442"IDXID="w5117"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"
Queues After moving NetWare 3.1x print servers to the NetWare 4.1 Directory, bindery reference queues are created on the NetWare 4.1 server to represent the real queues on the NetWare 3.1x servers. These reference queues are actually pointers to the real NetWare 3.1x queues. Since they are just pointers, these reference queues differ from the real queues that are created and merged on the NetWare 4.1 server during the NetSync upgrade process. Altering these reference queues can make the real queues unusable, so these queues should not be accessed or configured in any way. They also should not be deleted for any reason.RENDERAS="SECT2"Reference IDXID="w5118"BOOK="_idx" COLLECTION="nw41" TIDREF="i2598"
Name SynchronizationThe IDXID="w5119"BOOK="_idx" COLLECTION="nw41" TIDREF="i3442"
names of NetWare 4.1 bindery reference queues are enclosed in brackets. These reference names have the name of the NetWare 3.1x queue appended to the original server name.PAGENUM=52 ID="BP59"For example, the reference name used on a NetWare 4.1 server for a NetWare 3.1x print queue named "Q1" on NetWare 3.1x server "SALES" would be "{SALES_Q1}."Bindery reference queues appear at the bottom of the queue list in the PCONSOLE and NetWare Administrator utilities.RENDERAS="SECT2"Queue IDXID="w5120"BOOK="_idx" COLLECTION="nw41" TIDREF="i3442"IDXID="w5121"BOOK="_idx" COLLECTION="nw41" TIDREF="i3097"
Operators, Users, and GroupsQueue operators, users, and groups are not changed when a NetWare 3.1x print server is moved to a NetWare 4.1 print server. Groups synchronize from NetWare 4.1 to NetWare 3.1x. If a user was originally in a group with queue rights on a NetWare 3.1x server, the user still can use the queue. (In Directory Services, a user must authenticate to the server on which the desired queue resides.)RENDERAS="SECT1"ID="FM70522"Upgrading NetWare Name Service (NNS) IDXID="w5122"BOOK="_idx" COLLECTION="nw41" TIDREF="i2768"
PrintingNetWare Name Server® (NNS) printing configurations differ from printing in other NetWare software, so NNS® printing will not work in other NetWare environments without some conversion. NetSync can convert most or all of your NNS printing configuration so it works in NetSync or NetWare 4.1. The completeness of the print conversion depends on the number of servers in the NNS domain.RENDERAS="SECT2"How NetSync Rebuilds NNS PrintingUnder NNS, a print queue is originally created on one of the servers in the NNS domain. A replicated print queue (a fake queue that references the real queue) with the same name is then automatically created on each of the other servers in the domain. This allows users to print to a queue no matter which server they use to log in to the domain.When NetSync is originally installed on servers in an NNS domain, it breaks the domain. Each server that was in the domain is now considered an individual server in the NetSync cluster. Since the domain is broken, the replicated queues lose their reference to their real counterparts.PAGENUM=53 ID="BP60"NetSync gives you several options to restore printing functionality. First, you can convert the fake print queues to real queues. NetSync can convert all the fake print queues on each 3.1x server into real queues that inherit the properties of the original real queues. NetSync can then use these converted queues to rebuild the print environment. If you choose not to convert the fake queues to real queues, the fake queues are deleted. You must either manually establish printing connections or change capture statements to access printing on these servers.If you choose to convert the fake queues, the installation program also asks if you want to rebuild the print environment. If you answer "Yes," NetSync tries to completely restore the printing functionality you had under NNS. If you answer "No," NetSync only converts replicated print queues to real print queues. Printing will not work again until you take additional steps.When NetSync rebuilds the print environment, it duplicates the print servers and their properties on all the 3.1x servers. It then connects all the print queues (the original real queues and the fake queues converted to real queues) to the original print server.RENDERAS="SECT2"Functionality of NetSync Printing Depends on Size of NNS DomainIf you choose to have NetSync rebuild the print environment, the functionality of the resulting print configuration depends on the size of your original NNS domain. To completely restore printing, you may also need to move the print server from each 3.1x server to the NetWare 4.1 host server, again depending on the size of your NNS domain. If your NNS domain had eight servers or fewer, printing continues to work as it did under NNS for users on the 3.1x servers in the NetSync cluster.If you have 9-12 servers in your NNS domain, your printing works as it did under NNS only if you also move printing to NetWare 4.1 after running NetSync. One limitation in rebuilding printing from NNS domains of this size is that each print server created on the 3.1x servers by NetSync can service only eight file servers.You could keep the print servers on the NetWare 3.1x servers if you plan on using print servers on eight or fewer of the servers in the NetSync cluster. In this case you could just choose which servers you want to print from and then add those servers to the NetSync cluster first. Then printing would continue to work without moving printing to NetWare 4.1. PAGENUM=54 ID="BP61"Printing information for more than eight servers is still retained, so when you do move printing to NetWare 4.1, that information is copied over and allows printing for as many as 12 servers in the NetSync cluster.If you have more than 12 servers in your NNS domain, you need to make some modifications to allow printing to all print queues from all the servers that were in the domain. However, you can restore printing for each NetSync cluster (with as many as 12 NetWare 3.1x servers) as described earlier. RENDERAS="SECT2"Considerations in Moving Printing to NetWare 4.1If you choose not to rebuild the print environment, one option to restore printing functionality is to manually set up printing on the NetWare 4.1 server. In this case, you would need to create a print server on the NetWare 4.1 server. Then delete any print queues on the 3.1x servers you won't use. As a final step, create a bindery reference queue on the NetWare 4.1 server (serviced by the print server there) for each queue you are using on the 3.1x servers.Be aware that there is a large storage overhead when NetSync moves printing to NetWare 4.1. When NetSync converts NNS printing, it must create real print queues for all the fake queues on every 3.1x server in the NetSync cluster. When you move printing to the NetWare 4.1 host server, bindery reference queues are created for every queue on every NetWare 3.1x server. If you had 20 print queues on 12 NetWare 3.1x servers in your NNS domain, 240 bindery reference queues (20 queues x 12 servers) would be created on the NetWare 4.1 server after you moved printing there.It is easy to modify print queues or print servers in NetSync. You might find it easier to let NetSync duplicate all the print queues, and then you can delete those you aren't using. For larger domains, you might find it easier to design your printing from scratch and set it up on the NetWare 4.1 server.While NetSync does not resolve all the printing incompatibilities with NNS and NetWare 4.1, it does allow you to easily convert printing for NNS domains with 12 or fewer servers. For larger domains, you probably need to go through the process of setting up printing in NetWare 4.1, a process you need to do anyway when you convert NNS to NetWare 4.1.PAGENUM=55 ID="BP62"RENDERAS="SECT1"Using Third-Party IDXID="w5123"BOOK="_idx" COLLECTION="nw41" TIDREF="i2893"IDXID="w5124"BOOK="_idx" COLLECTION="nw41" TIDREF="i3390"
Network-Direct IDXID="w5125"BOOK="_idx" COLLECTION="nw41" TIDREF="i4475"
Print IDXID="w5126"BOOK="_idx" COLLECTION="nw41" TIDREF="i1026"
Devices Network-directIDXID="w5127"BOOK="_idx" COLLECTION="nw41" TIDREF="i3523"
 printers and hardware queue servers produced by various manufacturers either connect to a printer and then to the network or are installed in a port at the printer.These print devices and their installation programs are designed to look in the NetWare 3.1x bindery for network printing information. Therefore, queue server configurations used by these printers should not be moved.For more information, see "BOOK="printenu" COLLECTION="nw41"Using Third-Party Network-Direct Print Devices with NetWare 4" in Chapter 6 of Print Services.LABEL="A"PAGENUM=57 ID="BP63"ID="FM80893"NetSync IssuesRENDERAS="SECT1"ID="FM93433"Usernames Containing European Diacritic IDXID="w5128"BOOK="_idx" COLLECTION="nw41" TIDREF="i618"
CharactersNetWare®
 3.1x utilities (such as SYSCON) automatically convert diacritic characters (such as umlaut, accents, cedilla, tilde, circumflex, etc.) IDXID="w5129"BOOK="_idx" COLLECTION="nw41" TIDREF="i1539"
to upper case. NetWare 4TM utilities do not. If, for example, a user logs in to a NetWare 3.1x server as "José," his username is converted to "JOSE." But the same user's login name stays "José" in the NetWare 4 environment. As a result, after you install NetSync on both NetWare 3.1x and NetWare 4.1 servers, user José could exist twice in the NetWare 4.1 server's super-bindery, as José and as JOSE. (The super-bindery includes all User and Group objects being synchronized.)NetSync tries to solve this problem by loosely matching the two usernames and assuming that they refer to the same user.To ensure consistent behavior of foreign language characters and usernames, take the following precautions:MARK=BULLETSpecify the same IDXID="w5130"BOOK="_idx" COLLECTION="nw41" TIDREF="i2047"IDXID="w5131"BOOK="_idx" COLLECTION="nw41" TIDREF="i670"
code page in the NetWare 4.1 server's LCONFIG.SYS file in INSTALL.NLM and in each NetWare client's CONFIG.SYS file (with the MOREINFO="NONE"COUNTRY= command).If your users use NetWare 4.1 LOGIN and SETPASS utilities to log in to or change their password on a NetWare 3.1x server, they should use the following syntax: FORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN servername/username /B MOREINFO="NONE"<Enter>orFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN username /B MOREINFO="NONE"<Enter>
PAGENUM=58 ID="BP64"FORMAT="LINESPECIFIC"MOREINFO="NONE"SETPASS servername/username /BMOREINFO="NONE" <Enter>orFORMAT="LINESPECIFIC"MOREINFO="NONE"SETPASS username /B MOREINFO="NONE"<Enter>RENDERAS="SECT1"ID="FM27459"Duplicate Names in a IDXID="w5132"BOOK="_idx" COLLECTION="nw41" TIDREF="i439"
Bindery Context PathNetWare 4.1 allows the 
bindery context to include up to 16 containers. (Previous versions of NetWare 4 allowed only one container in a bindery context.) This group of containers in the bindery context is called a bindery context path. (For more information, see "BOOK="cncptenu" COLLECTION="nw41"Bindery context path" in Concepts.)All NetWare 3.1x bindery objects are copied (uploaded) into the first container listed in the bindery context path. For example, assume that the bindery context has two containers as shown in the following bindery context path: OU=Sales.O=Novell;OU=Marketing.O=NovellIn this example, all NetWare 3.1x user and group bindery objects end up in the Sales container, the first container in the path, as shown in the following figure.FILEREF="n41ns20a.tif"Subsequently, however, all objects from all containers in a bindery context path are synchronized with each NetWare 3.1x server.PAGENUM=59 ID="BP65"For example, the following situation involving duplicate names can arise in a bindery context path scenario.When User object Joe is copied from a NetWare 3.1x server, NetSync tries to create this object in the first container of the context path (OU=Sales.) If an object by the name Joe already exists in this container, this NetWare Directory Services object takes precedence and the NetWare 3.1x User object is merged with it. If no object Joe exists anywhere in the bindery context, NetSync creates one for the NetWare 3.1x bindery object. If, after the original synchronization, an administrator creates another object Joe in a container also in the bindery context path, one of the Joe objects is "eclipsed" by the other. Both objects still exist in the Directory tree, but only one is visible to bindery services.If the newer object Joe is in a container further down the list, it is eclipsed by the original object Joe. It is not be visible to bindery services and, consequently, is also not visible to the NetWare 3.1x servers on NetSync.Alternatively, if the newer object Joe is in a container farther up the list than the original object Joe, the original object is eclipsed. RENDERAS="SECT1"IDXID="w5133"BOOK="_idx" COLLECTION="nw41" TIDREF="i4687"IDXID="w5134"BOOK="_idx" COLLECTION="nw41" TIDREF="i2826"
Upgrading NetSync Servers to NetWare 4.1You can independently upgrade each of the NetWare 3.1x servers in the NetSync cluster to NetWare 4.1. After you upgrade a 3.1x server, you can remove it from the NetSync cluster by deleting the server name from the "Authorized 3.1x Server" list in NETSYNC4 on the NetWare 4.1 host server.In the original synchronization process, NetSync created all the necessary NetWare Directory Services objects for the 3.1x server. Upgrading a 3.1x server to NetWare 4.1 is, therefore, a smooth process that should require little user intervention.There are two steps you should follow to make sure the upgrade process works properly:MARK=BULLETDo not unload NETSYNC3 on the NetWare 3.1x server until you are ready to upgrade to NetWare 4.1.NetSync keeps all changes to the objects synchronized so they upgrade properly.PAGENUM=60 ID="BP66"Upgrade all the NetWare 3.1x servers in the NetSync cluster to the same Directory tree.You do not need to upgrade all the 3.1x servers at the same time.