Now that your NetWare 4 servers are running, it is time to install the clients. This chapter shows you how to install the following:
You will also learn how to set up your NetWare 4 server so it can communicate with Macintosh and OS/2 clients.
NetWare 4.x provides an install program file (INSTALL.EXE) that you can run to set up the client software in the language of your choice. The language support includes English, French, German, Spanish, and Italian. As you learned in the preceding sections, the NETX shell has been replaced by the Virtual Memory Manager (VLM.EXE), which loads a number of VLMs. The installation program installs the VLMs in the appropriate workstation directories and creates the necessary batch files to load the ODI drivers and protocol stacks and run the VLM.EXE program.
You can install the NetWare DOS requester from either the CD-ROM or floppy disk distribution. If you are installing from the CD-ROM distribution, you need to go to the \CLIENT\DOSWIN directory on the CD-ROM distribution and type install. If installing from a floppy disk, you need the disks labeled WSDOS-1, WSWIN-1, and WSDRV-2.
NOTE: You needed WSDRV-1 in NetWare 4.0, but starting with NetWare 4.01, the files in the installation disks are kept in a compressed format, eliminating the need for an additional driver disk. As support for more network drivers is added, you might see other driver disks added as part of the installation.
TIP: If you have only the CD-ROM distribution and want to create the installation floppy disks for network client software, you must run the MAKEDISK command that you can find in the \CLIENT\DOSWIN directory. You must have three blank preformatted high-density disks. You also should have the DOS utilities on the search path. The MAKEDISK batch file uses the DOS LABEL command to label the disks that you produce. Use this command:
MAKEDISK A: language
Where language is one of the following:
FRENCH or FRANCAIS
ITALIAN or ITALIANO
GERMAN or DEUTSCH
SPANISH or ESPANOL
You also can create the client installation disks from the INSTALL.NLM options.
1. Load INSTALL.NLM.
2. Select Product Options.
3. Select Choose an item or product listed above.
4. Select Create DOS/MS Windows/OS2 Client Installation Disks.
The following steps describe the procedure for installing NetWare from floppy disks. Unless a CD-ROM drive is attached to a workstation, this method is perhaps the most common one used for a first-time installation. You also can copy the NetWare work- station client software to a network drive and run the installation program from that drive. The directory structure on the network drive is the same as that on the CD-ROM. You must make the directory (in which the client INSTALL program is located) your current drive, and then run the INSTALL command.
Follow these steps to install NetWare from floppy disks:
Volume in drive A is WSDOS_1 Directory of A:\ _RUN OVL 2,815 02-01-94 8:33a WSDOS_1 18,716 11-08-94 8:07p CMPQ_RUN OVL 2,815 02-01-94 8:33a IBM_RUN OVL 2,815 02-01-94 8:33a INSTALL CFG 6,564 10-21-94 11:36a INSTALL EXE 105,522 10-21-94 9:00a NWUNPACK EXE 38,818 06-15-94 8:34a TEXTUTIL IDX 9,170 12-10-90 1:37p NLS <DIR> 11-09-94 12:33a DOS <DIR> 11-09-94 12:34a 10 file(s) 187,235 bytes 528,896 bytes free
Figure 4.1 The NetWare Client Install screen.
VLM.EXE -NetWare virtual loadable module manager v1.20 (941108) (c) Copyright 1994 Novell, Inc. All Rights Reserved. Patent pending. The VLM.EXE file is pre-initializing the VLMs............. The VLM.EXE file is using extended memory (XMS). DOS is only configured for 24 drives, NETX.VLM requires 26 drives for full functionality. The NETX.VLM file will load with partial support. Add LASTDRIVE=Z to the CONFIG.SYS file, reboot the workstation; then load the NETX.VLM file. You are attached to server FS1.
NOTE: If you want to use the workstation for network administration, you should have MS Windows installed and select the option to install MS Windows support for your workstation.
TIP: One of the choices of drivers has the name "Dedicated (Non-ODI) IPX" driver. If ODI drivers are not available for your network board, you can select this choice. You must then manually copy the correct IPX.COM to the client directory (C:\NWCLIENT, by default).
Figure 4.2 NetWare 4.x Client Install: Network boards supported.
Figure 4.3 NetWare 4.x Client Install: Network board parameters.
TIP: Avoid using IO Base Port address 378 hex, which is used by the parallel printer port LPT1. Also avoid using IRQ 3, which is used by COM2, unless you have the COM2 port disabled.
Device Port Address LPT1 0378h LPT2 03BCh COM1 03F8h COM2 02F8h
Figure 4.4 NetWare 4.x Client Install: Ethernet frame types.
NOTE: If you are using the NetWare 4.x client software to access a NetWare 3.x server using an Ethernet board, select the frame type of ETHERNET_802.3 in addition to the default Ethernet_802.2 frame type. For Token Ring, select the frame type of TOKEN-RING. If you are running AppleTalk client software programs, select a frame type of ETHERNET_SNAP and TOKEN-RING_SNAP for Ethernet and Token Ring, respectively.
Figure 4.5 NetWare 4.x Client Install: Shows selected driver.
Figure 4.6 NetWare 4.x Client Install: Installation summary.
@CALL C:\NWCLIENT\STARTNET AUTOEXEC.NEW: @CALL C:\NWCLIENT\STARTNET @ECHO OFF PROMPT $P$G C:\WIN\SMARTDRV.EXE PATH C:\HJWIN;c:\hj2;c:\bin;c:\windows;c:\scsi doskey set FTP_ETC=c:\pctcp\etc set NSE_DOWNLOAD=D:\DOWNLOAD SET TEMP=C:\WINDOWS\TEMP CONFIG.NEW: DEVICE=C:\DOS\SETVER.exe DEVICE=C:\scsi\ASPI4DOS.SYS DEVICE=C:\scsi\ASWCDSNY.SYS /D:ASPICDO files=50 buffers=50 DEVICE=C:\WINDOWS\HIMEM.SYS shell=command.com /p /e:800 DEVICE=C:\WINDOWS\SMARTDRV.EXE /DOUBLE_BUFFER STACKS=9,256 LASTDRIVE=Z
NOTE: The client installation program places the @CALL C:\NWCLIENT\STARTNET at the beginning of the AUTOEXEC.BAT file. If you want your PATH and PROMPT statements in the AUTOEXEC.BAT file to be processed before the client software is loaded, edit your AUTOEXEC.BAT file to relocate the @CALL C:\NWCLIENT\STARTNET statement.
You might want to use the LOADHIGH commands to load some of the TSRs high. For instance, you might try the following sequence in the STARTNET.BAT file:
@ECHO OFF C: CD \NWCLIENT SET NWLANGUAGE=ENGLISH (Replace ENGLISH with the language of choice) LOADHIGH LSL LOADHIGH SMC8000 (Replace with name of your ODI driver) LOADHIGH IPXODI VLM CD \
You might also try running MEMAKER for MS-DOS 6.x and above to see how you can optimize memory.
In NetWare 4, the DOS requestor actually consists of a number of smaller components that are loaded only if a particular service is requested. These smaller components are called Virtual Loadable Modules (VLMs), and they are loaded and managed by the VLM manager (VLM.EXE). (See Chapter 1 for more on VLMs.)
You can load the VLM Manager with a number of interesting options. These options are reminiscent of the options that are used in the NETX shell program, but new options have been added also.
You can conveniently display the list of available options by typing this command:
The following listing shows the help messages displayed when you execute the VLM /? command:
VLM.EXE - NetWare virtual loadable module manager v1.20 (941108) (c) Copyright 1994 Novell, Inc. All Rights Reserved. Patent pending. Available command line options: /? Display this help screen. /U Unload the VLM.EXE file from memory /C=[path\]filename.ext Specify a configuration file to use (Default is NET.CFG). /Mx The memory type the VLM.EXE file uses where x is one of the following: C = Conventional memory. X = Extended memory (XMS). E = Expanded memory (EMS). /D Display the VLM.EXE file diagnostics. /PS=<server name> Preferred server name to attach to during load. /PT=<tree name> Preferred tree name to attach to during load. /Vx The detail level of message display where x is one of the following: 0 = Display copyright and critical errors only. 1 = Also display warning messages. 2 = Also display VLM module names. 3 = Also display configuration file parameters. 4 = Also display diagnostics messages.
If you do not have TSRs loaded after loading VLM.EXE, you can unload VLM.EXE by typing this command:
If the VLM Manager thinks it is unsafe to unload itself, it does not unload and displays a warning message instead.
When VLM.EXE loads, it looks for configuration information in the NET.CFG file. Specifically, it looks for the NetWare DOS Requester section of the NET.CFG file and processes configuration statements in that section. Earlier, you saw examples of the statements USE DEFAULTS=ON and USE DEFAULTS=OFF, which you can use to enable or disable the default load order.
You can use the /C option to specify another configuration file besides the default NET.CFG. If you want to specify the configuration file C:\CONFIG\STAND.CFG file, for example, use the command:
You can load the VLMs in conventional, extended, or expanded memory. To load in extended and expanded memory, you should have the appropriate extended and expanded memory drivers loaded.
To load in extended memory, use this command:
To load in expanded memory, use this command:
To load in conventional memory (default), use the command:
When the VLM loads, it attaches to the nearest server. It does this by issuing a GetNearestServer SAP (Service Advertising Protocol) request, and waiting for all NetWare servers to respond. The VLM then connects to the server that was returned in the first GiveNearestServer SAP response. Next, the VLM attaches the next available drive in the workstation's drive table to the SYS:LOGIN volume of this server (see fig. 4.24).
The SYS:LOGIN directory contains a number of programs that can be used to access the network. Some of the main programs are LOGIN.EXE, CX.EXE, and NLIST.EXE. Also, OS/2 workstations can use a subdirectory called OS2 in SYS:LOGIN to connect to the network. To maintain compatibility with the NETX behavior, you can specify the first network drive to be used in the NetWare DOS Requester section by adding the following statement under the NetWare DOS Requester section:
FIRST NETWORK DRIVE=F
Without this statement, the next available drive D is mapped to SYS:LOGIN. For instance, if the FIRST NETWORK DRIVE parameter is not specified, the next available drive depends on what devices are in use. If you have a hard drive set up as C and a CD-ROM unit set up as D, you would get E as the first network drive.
After the network drive attaches to SYS:LOGIN, you must change the current drive to the attached network drive and type the LOGIN command. Thus, the typical login sequence is this:
F: LOGIN SpecifyLoginName
You can place all these commands in a batch file for automation.
If you want to specify the server to which you will log in initially, you must use the preferred server (/PS) option. If you want to log in to the server FS1, for instance, you must use the following command:
The /PS option works in a similar manner to the preferred option for the NETX shell. You also can use the PREFERRED SERVER parameter in the NET.CFG file. This parameter is primarily meant for clients who use BIND.VLM rather than NDS.VLM. For a NetWare 4.x client, an initial connection is made to the preferred server. If this server happens to be a NetWare 4.x server, an attachment to the preferred tree is made.
In a NetWare 4.x network, multiple NetWare Directory Service trees are possible. Most organizations prefer having a single tree because of the difficulty in restructuring and merging trees; and also because a single tree meets the needs of complex organizational structures. In some situations, however, multiple NDS trees might be useful, perhaps for security reasons so that you can prohibit information exchange between two NDS trees. Another reason could be the establishment of an experimental NDS tree on a production network that already has an NDS tree in use. Many system administrators might want to work with an experimental network to learn about structuring an NDS tree before making these changes on a production network.
Using the preferred tree (/PT) option gives you a choice of connecting to a particular tree. If you want to connect to an experimental NDS tree called EXPNET, for instance, use the following command:
To connect to a production network called CNET, you might want to unload the VLM and reconnect. You thus would use these commands, the first to unload, and the second to connect to the CNET tree:
You also can use the PREFERRED TREE=treeName option in the NET.CFG file to specify a preferred tree option.
During the loading of the VLM you can obtain important messages relating to warning, error, and diagnostic information. These messages can provide a valuable diagnostic aid when you are trying to figure out the load order of the VLMs.
The general command for loading VLMs with different message verbosity levels is this:
Where x is a number from 0 to 4.
If you want to display copyright and critical error messages only, use the following command to load the VLMs:
If, in addition to copyright and critical error messages, you want to display warning messages, use the following command to load the VLMs:
If, in addition to copyright, critical error messages, and warning messages, you want to display the names of the VLM modules as they load, use the following command to load the VLMs:
If, in addition to copyright, critical error messages, warning messages, and names of the VLMs as they load, you want to display configuration file parameters, use the following command to load the VLMs:
The following sample listing shows the messages produced when you load the VLM with a /V3 option:
C:\NWCLIENT> VLM /V3 VLM.EXE - NetWare virtual loadable module manager v1.20 (941108) (C) Copyright 1994 Novell, Inc. All Rights Reserved. Patent pending. SET STATION TIME OFF USE DEFAULTS OFF VLM CONN.VLM VLM IPXNCP.VLM VLM TRAN.VLM VLM SECURITY.VLM VLM NDS.VLM VLM BIND.VLM VLM RSA.VLM VLM NWP.VLM VLM FIO.VLM VLM GENERAL.VLM VLM REDIR.VLM VLM PRINT.VLM VLM NETX.VLM VLM AUTO.VLM The VLM.EXE file is pre-initializing the VLMs............... The VLM.EXE file is using extended memory (XMS). CONN.VLM - NetWare connection table manager v1.20 (941108) AVERAGE NAME LENGTH 15 CONNECTIONS 5 IPXNCP.VLM - NetWare IPX transport module v1.20 (941108) PB BUFFERS 4 TRAN.VLM - NetWare transport multiplexor module v1.20 (941108) SECURITY.VLM - NetWare security enhancement module v1.20 (941108) CONNECTIONS 5 NAME CONTEXT "OU=CORP.O=ESL" CONNECTIONS 5 NDS.VLM - NetWare directory services protocol module v1.20 (941108) BIND.VLM - NetWare bindery protocol module v1.20 (941108) PREFERRED SERVER NW4CS RSA.VLM - NetWare RSA authentication module v1.20 (941108) NWP.VLM - NetWare protocol multiplexor module v1.20 (941108) MESSAGE TIMEOUT 180 FIO.VLM - NetWare file input-output module v1.20 (941108) PB BUFFERS 4 CONNECTIONS 5 GENERAL.VLM - NetWare general purpose function module v1.20 (941108) FIRST NETWORK DRIVE F REDIR.VLM - NetWare DOS redirector module v1.20 (941108) FIRST NETWORK DRIVE F SHOW DOTS OFF PRINT.VLM - NetWare printer redirection module v1.20 (941108) NETX.VLM - NetWare workstation shell module v4.20 (941108) FIRST NETWORK DRIVE F CONNECTIONS 5 AUTO.VLM - NetWare auto-reconnect module v1.20 (941108) You are attached to server NW4CS
If, in addition to copyright, critical error messages, warning messages, names of the VLMs as they load, and configuration file parameters, you want to display diagnostic information, use the following command to load the VLMs:
The following sample listing shows the messages produced when you load the VLM with a /V4 option:
C:\NWCLIENT> VLM /V4 VLM.EXE - NetWare virtual loadable module manager v1.20 (941108) (C) Copyright 1994 Novell, Inc. All Rights Reserved. Patent pending. SET STATION TIME OFF USE DEFAULTS OFF VLM CONN.VLM VLM IPXNCP.VLM VLM TRAN.VLM VLM SECURITY.VLM VLM NDS.VLM VLM BIND.VLM VLM RSA.VLM VLM NWP.VLM VLM FIO.VLM VLM GENERAL.VLM VLM REDIR.VLM VLM PRINT.VLM VLM NETX.VLM VLM AUTO.VLM The VLM.EXE file is pre-initializing the VLMs............... The VLM.EXE file is using extended memory (XMS). CONN.VLM - NetWare connection table manager v1.20 (941108) AVERAGE NAME LENGTH 15 CONNECTIONS 5 IPXNCP.VLM - NetWare IPX transport module v1.20 (941108) PB BUFFERS 4 TRAN.VLM - NetWare transport multiplexor module v1.20 (941108) SECURITY.VLM - NetWare security enhancement module v1.20 (941108) CONNECTIONS 5 NAME CONTEXT "OU=CORP.O=ESL" CONNECTIONS 5 NDS.VLM - NetWare directory services protocol module v1.20 (941108) BIND.VLM - NetWare bindery protocol module v1.20 (941108) PREFERRED SERVER NW4CS RSA.VLM - NetWare RSA authentication module v1.20 (941108) NWP.VLM - NetWare protocol multiplexor module v1.20 (941108) MESSAGE TIMEOUT 180 FIO.VLM - NetWare file input-output module v1.20 (941108) PB BUFFERS 4 CONNECTIONS 5 GENERAL.VLM - NetWare general purpose function module v1.20 (941108) FIRST NETWORK DRIVE F REDIR.VLM - NetWare DOS redirector module v1.20 (941108) FIRST NETWORK DRIVE F SHOW DOTS OFF PRINT.VLM - NetWare printer redirection module v1.20 (941108) NETX.VLM - NetWare workstation shell module v4.20 (941108) FIRST NETWORK DRIVE F CONNECTIONS 5 AUTO.VLM - NetWare auto-reconnect module v1.20 (941108) You are attached to server NW4CS
After you have loaded the VLM Manager, you can obtain diagnostic information on it by running VLM with the diagnose option (/D). Many of the numbers displayed (especially those in columns) are expressed as hexadecimal numbers, as you can see in the following example:
F:\> VLM /D VLM.EXE - NetWare virtual loadable module manager v1.02 (930510) (C) Copyright 1993 Novell, Inc. All Rights Reserved. Patent pending. The VLM.EXE file v1.2 is currently loaded VLM transient switch count : 0 VLM call count : 192 VLM current ID : 0000h VLM memory type : CON VLM modules loaded count : 12 VLM block ID (0 if CON) : 0000h VLM transient block :1EC3h VLM global seg (0 if CON) : 0000h VLM async queue (h, t, s) : 0000:0000, 1DDE:0030, 0 VLM busy queue (h, t, s) : 0000:0000, 1DDE:003C, 0 VLM re-entrance level : 1 VLM full map count : 0 VLM Control Block information Address TMemSize GMemSize SMemSize ID Flag Func Maps Call TSeg GSeg Low High Para K Para K Para K -------------------------------------------- 001 A000 0005 0000 0052 1DDE 1354 FFFF FFFF 00F4 0003 0000 0000 0000 0000 010 A000 0011 0000 0012 1EC3 1F7B FFFF FFFF 00B8 0002 0018 0000 0194 0006 021 A000 000B 0000 0005 1F93 2079 FFFF FFFF 00E6 0003 00A2 0002 0066 0001 020 E000 000B 0000 0009 1F93 2079 FFFF FFFF 00E6 0003 00A2 0002 0066 0001 061 A000 0005 0000 0005 211B 2221 FFFF FFFF 0106 0004 0000 0000 00CD 0003 032 A000 0010 0000 0007 2221 2392 FFFF FFFF 0171 0005 00B9 0002 003E 0000 031 A000 0010 0000 0006 244B 2503 FFFF FFFF 00B8 0002 001C 0000 002D 0000 030 A000 0011 0000 0007 251F 25D0 FFFF FFFF 00B1 0002 0071 0001 004A 0001 041 A000 000B 0000 0005 2641 27E3 FFFF FFFF 01A2 0006 0283 0010 0021 0000 043 A000 000A 0000 0006 2A66 2AD2 FFFF FFFF 006C 0001 001E 0000 0050 0001 040 A000 0009 0000 001E 2AF0 2D2B FFFF FFFF 023B 0008 005F 0001 004B 0001 042 A000 000E 0000 0006 2D8A 2E64 FFFF FFFF 00DA 0003 00AC 0002 0059 0001 050 A000 0007 0000 0007 2F10 3125 FFFF FFFF 0215 0008 00F2 0003 007D 0001 Total 0DAA 069E Maximum 023B 0283 0194
Explanations of the diagnostic information are beyond the scope of this book.
NET.CFG is a text file that contains configuration statements dealing with configuring the ODI driver, and providing the binding among the communication protocol, the ODI driver, and the NetWare requester. A new section called the NetWare DOS Requester has been defined for the NetWare 4.x clients. You need to indent the configuration statements under the NetWare DOS Requester heading at least two spaces. The more important of these statements are discussed next.
In this section, you will only learn about the NET.CFG parameters that are different from NetWare 3.x and that are important for NetWare 3.x to 4.x migration. For further details, refer to New Riders' companion volume NetWare Training Guide: NetWare 4 Administration.
You use the NAME CONTEXT statement to establish the context of the workstation on attachment to the NDS tree. The statement's syntax is the following:
NAME CONTEXT = "complete name path"
Replace complete name path with the complete name of the context to be set initially. You should set the initial name context for users to the container that contains most of the resources they are likely to use. You must include the complete name in the quotation marks.
An example of the use of NAME CONTEXT follows:
NetWare DOS Requester NAME CONTEXT = "OU=CORP.O=ESL"
Use the PREFERRED TREE option to specify the NDS tree to which the VLMs are to attach initially when they are loaded. The PREFERRED TREE option has meaning when the NDS.VLM is loaded because the option refers to an NDS tree. The syntax for using the PREFERRED TREE option follows:
PREFERRED TREE = tree name
Replace tree name with the name of the NDS tree.
An example of the use of PREFERRED TREE is this:
NetWare DOS Requester PREFERRED TREE = CNET
In the NetWare 4.x client, the DOS drive table is shared between DOS and the DOS Requester. When the VLMs load, the redirector assigns the first available DOS drive letter to the network drive. If the workstation has a single hard disk partition (drive C), drive D becomes the first network drive. To maintain compatibility with applications and batch/script files that might require the first network drive to be F (the default with the NETX shell programs), a new statement called FIRST NETWORK DRIVE has been provided.
The syntax for using the FIRST NETWORK DRIVE option is this:
FIRST NETWORK DRIVE = drive letter
Replace drive letter with a drive letter that is not in local use.
An example of the use of FIRST NETWORK DRIVE follows:
NetWare DOS Requester FIRST NETWORK DRIVE = F
The packet burst capability can be configured with the PB BUFFERS statement in the NetWare DOS Requester section. The default value is PB BUFFERS = 3. This capability also exists with NetWare 3.x. In NetWare 4.x, however, a formalized requirement insists that you place this statement in the NetWare DOS Requester section.
The syntax for using the PB BUFFERS option is this:
PB BUFFERS = n
Replace n with a number from 0 to 10. A value of 0 disables the packet burst option. Any other value from 1 to 10 enables the packet burst and also specifies the number of buffers for the packet burst.
The following sample command enables the PB BUFFERS option and specifies 3 buffers for the burst mode:
NetWare DOS Requester PB BUFFERS = 3
The VLMs are loaded by default in the load sequence described previously in this chapter. To disable the default load sequence, you must use this command:
If the default load sequence is disabled, you must specify the VLMs to load, using the this VLM statement:
Replace nameOfVLM with the name of the VLM to load.
An example of the use of these statements follows:
NetWare DOS Requester USE DEFAULTS=OFF VLM=CONN.VLM VLM=IPXNCP.VLM : : (and other VLMs)
You also can use the VLM statement with the default load order to specify optional VLMs to be loaded. To load the AUTO.VLM after the default load sequence, for example, use these commands:
NetWare DOS Requester USE DEFAULTS=ON VLM=AUTO.VLM
The default frame type for NetWare 4.x has been changed to ETHERNET_802.2. You need to specify this frame type in the Link Driver section. If you have on the network NetWare 3.x servers that use their default frame type of ETHERNET_802.3, you must additionally specify the ETHERNET_802.3 frame type. If you are using TCP/IP protocol stack software such as LAN WorkPlace or FTP Software's PC/TCP (running on top of ODI drivers), you must additionally specify the ETHERNET_II frame type.
The following lines show an example of the frame type for SMC8000 boards for NetWare 3.x server compatibility:
Link Driver SMC8000 int 3 port 280 mem D0000 frame ETHERNET_802.2 frame ETHERNET_802.3
The following lines show an example of the frame type for SMC8000 boards for NetWare 3.x server and TCP/IP compatibility:
Link Driver SMC8000 int 3 port 280 mem D0000 frame ETHERNET_802.2 frame ETHERNET_802.3 frame ETHERNET_II
For MS Windows workstations, you should set the SHOW DOTS=ON parameter in the NET.CFG file.
If you allow the client INSTALL program to install Windows support, the PROGRAM.INI and SYSTEM.INI files are modified, with the originals kept in PROGRAM.BNW and SYSTEM.BNW.
NOTE: The BNW extension indicates "Before NetWare."
In the PROGRAM.INI file, a new group file NWUTILS.GRP is added under the section [Groups]. The SYSTEM.INI file is modified to contain the line NETWORK.DRV=Novell NetWare (4.0) in the [Boot.Description] section. The [386enh] section is also modified, to load the virtual drivers VNETBIOS, VNETWARE.386, VIPX.386, and VCLIENT.386, and statements for enhanced support are added.
NetWare 4 includes support for a number of non-DOS clients such as OS/2, Macintosh, Unix, Windows 95, and Windows NT. To all of these different clients, NetWare 4 can provide communication, file, and print services. This section will discuss NetWare 4 support for Macintosh and OS/2 clients. Discussion of support for other types of clients is beyond the scope of this book.
NetWare 4 comes bundled with a copy of the NetWare for Macintosh product. This product contains a number of NLMs that support the Macintosh file sharing and communication protocols. For example, the NLMs support the Apple Filing Protocol (AFP), which enables the NetWare 4 server to emulate an Apple Share server for Macintosh clients. Other protocols such as the Printer Access Protocol (PAP), Apple Transaction Protocol (ATP), Apple Data Stream Protocol (ADSP), and Datagram Delivery Protocol (DDP) are also supported.
To configure the NetWare 4 server for Macintosh, you'll need to perform the following tasks:
The following steps are a guided tour for installing NetWare for Macintosh services on a NetWare 4 server.
Figure 4.7 Selecting the Install NetWare for Macintosh client option.
Figure 4.8 The CD-ROM source from which the files are installed.
Figure 4.9 The Install NetWare for Macintosh menu option.
Figure 4.10 The Final Installation Options form.
Figure 4.11 Selecting volumes to which name space is to be added.
After the NetWare for Macintosh files are installed, the NetWare for Macintosh services must be configured. You must perform the following configuration tasks:
These tasks can be configured from the NetWare for Macintosh Configuration menu (see fig. 4.12), that is displayed at the end of the procedure for the NetWare for Macintosh installation.
Figure 4.12 NetWare for Macintosh Configuration menu.
When you make a selection from the Macintosh Configuration menu, an NLM is loaded to perform the task. Table 4.1 shows the NLMs that are loaded for the options in the NetWare for Macintosh Configuration menu. These NLMs can be loaded directly from the server console or from the NetWare for Macintosh Configuration menu. After the initial installation of NetWare for Macintosh, you can access the NetWare for Macintosh Configuration menu by performing the following:
TABLE 4.1 NetWare for Macintosh Configuration NLMs
|Configure AppleTalk Stack||INETCFG.NLM|
|Configure File Services||AFPCON.NLM|
|Configure Print Services||ATPSCON.NLM|
|Configure CD-ROM Services||HFSCDCON.NLM|
To configure the AppleTalk stack, you must run the INETCFG.NLM (or select the Configure AppleTalk Stack option). Configuring the AppleTalk stack involves the following tasks:
The following is an outline of the procedure for performing AppleTalk configuration:
Figure 4.13 The INETCFG main menu.
Figure 4.14 Unconfigured AppleTalk protocol.
Figure 4.15 An AppleTalk Configuration form.
Figure 4.16 Configured AppleTalk protocol.
Figure 4.17 Protocol bindings.
Figure 4.18 Protocol choices for binding.
Figure 4.19 Network interfaces for binding.
Figure 4.20 Choice of AppleTalk networks.
Figure 4.21 Binding NetWare AppleTalk to a Network Interface form.
Figure 4.22 Configured AppleTalk protocol.
After the AppleTalk protocol stack is configured, you must configure AppleTalk File Services. You can use AFPCON to configure AppleTalk File services. The following is a partial list of file services that can be configured using AFPCON:
The following is an outline of the procedure for configuring AppleTalk File services:
Figure 4.23 Configured AppleTalk protocol.
Figure 4.24 The default configuration settings for AFP.
Figure 4.25 The Detailed Configuration menu.
Figure 4.26 The General Server Information Configuration form.
Figure 4.27 The Access Methods Configuration form.
Figure 4.28 The Performance Enhancements Configuration form.
Figure 4.29 The Maintenance and Status menu.
Figure 4.30 The Shut Down Server menu.
Figure 4.31 The Shut Down Server message.
Figure 4.32 Set Shut Down Time.
Figure 4.33 The Volume Status option.
Figure 4.34 The Volume Status menu.
During installation, all the files needed for NetWare for Macintosh services are copied. NetWare for Macintosh print services are bi-directional. To use these print services, you must configure them. The following is a partial list of configuration options that can be performed using ATPSCON:
The following is an outline of the procedure for configuring AppleTalk file print services:
Figure 4.35 Print services Configuration options.
Figure 4.36 Print services Quick Configuration.
Figure 4.37 Configured printer servers.
Figure 4.38 Configured print spoolers.
Figure 4.39 Completed print spooler form.
Figure 4.40 The Log Options menu.
Figure 4.41 The Management Options menu.
With the NetWare for Macintosh product installed and configured on the NetWare server, you can log on to the NetWare server from a Macintosh workstation using AppleShare because the NetWare server emulates an AppleTalk file server. To take full advantage of the NetWare 4 network, however, you must install the MacNDS client on the Macintosh workstations. The MacNDS client software provides access to the NDS for Macintosh workstations running under the System 7 operating system.
The following is a guided tour on installing the MacNDS client software:
TIP: If the Guest login is not enabled through AFPCON.NLM at the NetWare server, or if you do not allow the use of clear text passwords, the login could fail. In this case, use AFPCON to enable the use of clear text passwords, and repeat the login sequence. You can enable the use of clear text passwords by doing the following:
1. Start AFPCON.
2. Select Detailed Configuration.
3. Select User Access Information.
4. Set the Allow Clear Text Login field to Yes.
5. Go to the main AFPCON menu and select Maintenance and Status.
6. Select Restart AFP Server.
You are permitted to use an up-to-eight-character password for logging in as a user. If the Supervisor account uses passwords longer than eight characters, you will not be able to log in. In this case, and also because the passwords will be transmitted as clear text (not encrypted), you can create a temporary user in the bindery context using NETADMIN or NWADMIN (see Chapter 6), and assign this user a password that does not exceed the eight-character limit. Next, give this user explicit Supervisor file system rights to the root of the SYS: volume where the Macintosh client files have been placed as part of the NetWare for Macintosh installation. Now you can log in as this temporary user. Because the password is transmitted as clear text, using a temporary user whose password is distinct from the Supervisor user account has the further advantage of ensuring that the Supervisor password is not compromised.
Configuring OS/2 clients involves preparing the server to optionally provide OS/2 long filename support and installing the OS/2 client software.
OS/2 clients use the same IPX/SPX protocol for communicating with the NetWare 4 server as do the DOS clients. So no additional communication settings need to be done at the NetWare server for OS/2 clients. OS/2 clients can make use of the file and print services used by DOS clients.
However, OS/2 clients have the option of using the High Performance File System (HPFS), which supports long names and extended attributes. OS/2 long filenames can be up to 255 characters. Extended attributes are additional names and values describing the filename that can be attached to the long filenames.
To add support for HPFS to the NetWare file system, you need to add this name space support using explicit commands. You need to first load the OS/2 name space on the NetWare file server. This is done using the following server console command, which can be placed in the STARTUP.NCF file:
The LOAD OS2 command identifies the name space and loads the protocols and algorithms needed to understand the HPFS file system structure.
Next, you need to add the OS/2 name space to the NetWare volume that will support HPFS. You can do this using the following command:
ADD NAME SPACE OS2 TO volumename
Replace volumename with the physical volume name such as SYS or VOL1. The ADD NAME SPACE command creates additional directory entries in the directory entry table (DET) for the volume. These additional directory entries contain the long file- names for the OS/2 volume and other OS/2 file-name related information.
Because the OS/2 directory entries need to be created only once for a given volume, you need to execute the ADD NAME SPACE command only once during the initial OS/2 configuration for that volume. After the OS/2 name space has been added to the volume, you need only to load the OS2.NAM module. The OS2.NAM module is loaded from the STARTUP.NCF file, and the OS2.NAM file is kept in the server boot directory (C:\NWSERVER). Actually, after you add the name space to a volume, the name space module is autoloaded before the volume is mounted, even if the LOAD namespace statement is missing from the STARTUP.NCF file. If the namespace file cannot be found in the server boot directory, the corresponding NetWare volume to which the namespace is added will not mount.
The NetWare Client for OS/2 can be found on the NetWare 4 installation CD-ROM in the SYS:PUBLIC\CLIENT directory. You can create OS/2 client installation disks by running the MAKEDISK batch file that can be found in the OS/2 client subdirectory on the CD-ROM or the SYS:PUBLIC\CLIENT.
After you create these OS/2 client installation disks, you run the INSTALL program in the first installation disk from an OS/2 workstation connected to a NetWare 4 network.
In this chapter you learned how to install NetWare 4 clients. You looked at:
© Copyright, Macmillan Computer Publishing. All rights reserved.