Enterprise Software

Get IT Done: Make your Windows 2000 server mimic a NetWare server

Configure Windows 2000 to mimic a NetWare server


After years of trying, Microsoft still hasn’t displaced NetWare in the enterprise. Many network administrators continue to support this venerable yet capable network operating system in addition to Windows. In order to improve the interoperability between these disparate operating systems, Microsoft has released Windows Services For NetWare 5.0. Windows Services For NetWare runs on a Windows 2000 or Windows NT 4.0 server. It provides services essential to minimizing administrative effort in managing a mixed Windows/NetWare environment.

Windows Services For NetWare 5.0 includes two primary components, Microsoft Directory Synchronization Services and File And Print Services For NetWare. In this Daily Drill Down, I’ll focus on the File And Print Services For NetWare portion. I’ll explain how to install and configure this tool.

Author's Note
For my examples, I’ll be using a NetWare 6.0 server running Support Pack 2 and a Windows 2000 server with Service Pack 3 installed. The NDS tree is very simple and is named slowe, while the Windows 2000 server is a domain controller in the domain named lab.com. In addition, I have two Windows XP workstations. One is running Microsoft’s client Service For NetWare, while the other is running Novell’s Client32 4.83 SP1. For more information about what Windows Services For NetWare 5.0 can do, see the Daily Drill Down Go beyond GateWay Services for NetWare with Windows Services For NetWare 5.0.

File And Print Services For NetWare
File And Print Services For NetWare (FPNW) is designed to give your NetWare users seamless access to the shares and printers attached to a Windows 2000 Server. FPNW makes the Windows 2000 server appear to your clients to be a NetWare 3.12 server and thus able to make use of NetWare utilities to use the resources.

To install Print Services For NetWare, insert the Windows Services For NetWare CD into the Windows 2000 domain controller’s CD-ROM drive. At the server, click Start | Settings | Network and Dial-up Connections. Right-click the Local Area Network connection and choose Properties. When the Properties window appears, click Install. When the Select Network Component Type window appears, choose Service and click Add. When the Select Network Service window appears, click Have Disk, browse to the File And Print Services For NetWare folder on the Windows Services For NetWare CD-ROM, and click OK. Select File And Print Services For NetWare from the list of network components. Click OK to begin the installation.

During the installation, you’ll see the Install File And Print Services For NetWare screen seen in Figure A. Here you’ll specify several different options to configure the services. These options include:
  • Sysvol—By default, C:\sysvol is chosen as the location for the Sysvol directory. This directory is required, and it emulates the SYS: volume on a NetWare 3.12 server. A directory structure is created underneath it. This directory structure includes login, mail, public, and system folders, all of which are required on a NetWare 3.12 server. By default, NTFS and share permissions for this directory structure allow full access. You can restrict access to only those users that need to make use of the resources. I recommend this.
  • Server name—The server name field specifies the name by which the shared Windows resources will be known.
  • Supervisor Account password—NetWare 3.12 uses an administrative account named Supervisor, which is equivalent to a Windows Administrator user.
  • Tuning—The tuning options are fairly self descriptive and indicate how responsive the Windows resources will be for NetWare users.

Figure A
File And Print Services For NetWare configuration


You'll also be prompted to enter a password for the FPNW Service Account user, which is used to launch the services.

Once the components are installed, you'll be told that you need to restart your Windows 2000 Server, and you should do so. When the server reboots and the new service starts, you can make sure that it's running by trying to connect to it from an administrative workstation running a NetWare client.

After you’ve configured your server to support FPNW, you must make some changes to the users that you want to use the services. Start the Active Directory Users And Computers MMC, right-click a user, and select Properties. When the user's property sheet appears, click the NW Compatible tab, as shown in Figure B.

Figure B
Click the NW Compatible tab in the user’s property sheet.


When you want to enable a user to make use of resources using FPNW, you need to create a separate password. Select Maintain NetWare Compatible Login and click OK.

Creating new NetWare shares and printers
From this point, you can create new shares and printers on the Windows server and make them available to NetWare users. For this example, I'm going to create a directory called C:\Data.

You can't right-click the directory to be shared and click Sharing to create a new directory share under FPNW. Instead, click Start | Programs | Administrative Tools | Computer Management. Inside that utility, navigate to and expand Computer Management (Local) | System Tools | Shared Folders. Right-click the Shared Folders option and choose New File Share from the shortcut menu, as shown in Figure C.

Figure C
Starting the process of creating a new Windows/NetWare file share.


This starts the Create Shared Folder wizard, in which you'll provide the details about the new directory share. The details that you need to provide are the directory to be shared, the name that the new share will be known by on the network, a description of the share, and a choice as to what types of clients are allowed to use the new share—Windows clients, NetWare clients, or both, as shown in Figure D.

Figure D
Sharing the C:\Data folder on my Windows 2000 Server


The next step of the Create Shared Folder wizard asks for the permission level to be assigned to the new folder, as you can see in Figure E. For the purposes of this example, I'll be allowing all users full control. I wouldn't recommend this in a production environment, however.

Figure E
Assigning permissions for your new shares


Clicking Finish completes the wizard. You’ll then see a dialog box notifying you that the folder was successfully shared with both Windows and NetWare clients. Notice in Figure C that there's a small red box above the drive icon in the list of shares. This is a way to quickly identify which folders are accessible by NetWare clients.

To test the new share, you can browse to it from any computer that has an IPX-enabled version of a NetWare client installed. Browsing to the FPNW NetWare server in my example from a Windows XP workstation yields the results shown in Figure F. On workstations using an IPX-enabled NetWare client from Novell, you can use native NetWare utilities to connect to remote volumes and directories to attach to these shares.

Figure F
The data directory is clearly shown in the list of available shares as an additional accessible volume.


Sharing printers
Sharing printers on a Windows 2000 server with NetWare users is extremely simple and involves no additional steps beyond using Control Panel to create and share a printer. But before you can share a printer with NetWare users from your Windows 2000 server, you need to have a printer to share. For this example, I have an HP LaserJet 4 printer attached to LPT1 on my Windows 2000 server, and I've installed the drivers for it. I'm also going to assume that most administrators are interested in making printers installed on the Windows 2000 Server available to their NetWare users and aren't planning to use older DOS-based NetWare print servers.

If you use the Microsoft Client Services For NetWare from a Windows XP machine, your users can browse to the newly created NetWare server for the shared printers. Any printers that have been created are made available to users automatically, with no further configuration needed.

When connecting to shared printers from workstations using Novell’s client, the print queues created in FPNW are directly accessible by simply browsing to the server and using one of the listed print queues. You'll have to be able to log in as a NetWare-enabled user in order for this to work. You'll be able to make use of client utilities, such as Capture.

Managing FPNW after installation
I’ve gone over some of the ways to create shares and make use of Windows 2000 printers, but there are other ways to manage FPNW.

During installation, an FPNW icon is placed in the Control Panel. You can access it by clicking Start | Settings | Control Panel and choosing the FPNW icon. When you do, you’ll see the screen shown in Figure G.

Figure G
The File And Print Services For NetWare Control Panel


On this screen, you’ll see statistics on how many users are making use of the services. It also lets you change the services' configuration. The three buttons at the bottom of the window—Users, Volumes, and Files—allow you to manage these resources. For example, the Users button shows you a list of all of the users attached through the service. It allows you to disconnect them one by one or all at once or send them a console message, as shown in Figure H.

Figure H
You can view all of the users attached to FPNW.


Doing things the NT way
You can also manage FPNW via Server Manager in Windows NT. To do so, click Start | Run and type svrmgr.exe in the run dialog box. Because this method doesn't provide additional functionality, I don't recommend it. If, however, you need to attach to DOS-based print servers, you'll need to use this method to add NetWare print servers.

Make Windows and NetWare play nice
The File And Print Services For NetWare component of the Windows Services For NetWare 5 utility can help ease an administrator’s workload. Using FPNW, an administrator can use native NetWare utilities to manage both volumes and printers and continue to make use of Client32 and NetWare login scripts. The drawback to this method is that accounts need to be created twice—once in NDS and once in Active Directory. To fix this problem, Windows Services For NetWare includes a second component, the Microsoft Directory Synchronization Service, which I’ll cover in an upcoming Daily Drill Down.

Editor's Picks

Free Newsletters, In your Inbox