Boot the intended server system and enter the BIOS Setup and press [F5] to load BIOS defaults. Change to the Boot Menu and set the system to boot to the CD-ROM drive first. Save these changes and Exit. Insert the Student CD-ROM labeled Room 6359. Proceed to use Norton GHOST to image the drive with DOS 6.22. Be sure that to specify the partition size of 60MB rather than allow it to be the default of 2047MB. Restart the computer and allow it to boot to the CD-ROM again. Cancel the anti-virus scan and change to the Q:\BIN folder. Copy the file OAKCDROM.SYS to the DOS directory of the C: drive. Change to the root of the C: drive and add the following line to the C:\CONFIG.SYS file:

device=c:\dos\oakcdrom.sys /d:CD01

Remark the line that loads HIMEM.SYS in the CONFIG.SYS file by placing a semicolon at the beginning of the line so that it looks like this:

;DEVICE=C:\DOS\HIMEM.SYS

While you are at it you can put a semicolon in front of the "DOS=HIGH" line also. Save the changes and open AUTOEXEC.BAT. Remark the line that loads SMARTDRV.EXE by putting the REM command at the beginning of the line like this:

rem C:\DOS\SMARTDRV.EXE /X

Add the line to load DOS CD-ROM support like this:

C:\DOS\MSCDEX.EXE /D:CD01

Save the changes to the AUTOEXEC.BAT file and remove the CD-ROM and reboot the system.

Watch the boot up screens and make sure that the CD-ROM is issued drive letter D: If so insert the Novell Netware 4.11 2-user demo Server installation CD-ROM and change to the D: drive. Type in the command "install" (no quotes!) and press [Enter]. This screen appears:

Press [Enter] with English selected and the NOVELL TERMS AND CONDITIONS appear on screen. Press any key until the installation screen reappears and with NetWare Server Installation highlighted press [Enter]:

With Novell's NetWare 4.11 product two machines can be set up to run similar to a cluster server which they call SFT III for level 3 system fault tolerance. The goal of this exercise is to install the first NetWare 4.11 server on a new network. With the choice NetWare 4.11 highlighted press [Enter]:

On this next screen asking which type of installation is being performed. The simple installation prerequisites and installation tasks are:

• Hard drive must have an existing DOS partition of at least 40MB. This is a minumum size requirement, it can be larger if necessary. In the preparations it was set up at 60MB. This partition should be bootable to DOS. Additionally CD-ROM support should be set up in the DOS partition if the installation will be run from the install CD.
• Hard drives cannot be mirrored or duplexed during the simple installation.
• All available space on the hard drive not allocated to the DOS partition will be allocated to a new NetWare partition. This cannot be changed after the installation.
• A single NetWare volume will be created occupying the entire NetWare partition on each hard drive detected.
• The installation process will issue a randomly generated IPX internal network number to the server.
• The installation will created a default Novell® Directory Services® hierarchy with a single container for all objects.

The custom installation prerequisites and tasks are essentially the same as for the simple installation except that the administrator can:

• Assign a specific IPX internal network number
• Perform exact partitioning on all hard drives
• Set up disk mirroring/duplexing on hard drives
• Allocate specific sizes to all volumes including SYS and create additional volumes
• Create volumes that span across multiple hard drives.
• Modify the time zone parameters in NDS.
• Add custom additional commands to the AUTOEXEC.NCF and STARTUP.NCF files.
• Add additional network protocols including TCP/IP and AppleTalk in addition to the default IPX.

Be sure to select the middle choice for a custom installation and then press [Enter]:

The server name must be unique in the NetWare network. Furthermore, NetWare implements NetBIOS services over IPX which means that it will have to be unique across Microsoft based systems as well and for full NetBIOS compatibility the name should not exceed 15 characters. Since the room already has a NetWare server named FS1, name this one FSx where x is the station number. then press [Enter]:

On this next screen the server requires an internal IPX number. External IPX numbers are different and are assigned to the adapters when their drivers are launched at startup and are equivalent to the IPX network number. The internal number is required due to the internal architecture of the server and must be unique. Assign the internal network number for this server to be 6359000x where x is the station number. If the station number is two digits such as "Station 11" then make the internal IPX number: 63590011. Once assigned press [Enter] to continue:

At this point the installation program will copy the necessary files to the DOS partition that was first created that will allow the server to be launched. Once this is done then the server will launch and immediately start a program that will continue the installation process. So far everything that has been happening has been a program running in DOS. The installer should be indicating a path on the CD-ROM as the source and the destination should be C:\NWSERVER. If this is the case, press [Enter]:

On this next screen just be sure that the Country code is 001 - (United States), the code page is 437 - (United States English) and the keyboard mapping is none. If so the highlight should be situated on the "Press <Enter> here to continue" and do so.

This next screen allows the installer to make custom entries in the server's STARTUP.NCF file. This file is roughly equivalent to the CONFIG.SYS file of DOS and is used to set environmental parameters for the server as well as to load drivers and so on. The installation process on the lab's P4 systems makes an automatic modification to the STARTUP.NCF file and in this case another modification should be made. Move the highlight with the down arrow to the "Yes" and press [Enter]. This will open the screen so that the modification to the file can be made. Press the [End] key to position the cursor at the end of the existing line and press [Enter] to move to the next line. Enter the command: SET AUTO REGISTER MEMORY ABOVE 16 MEGABYTES=ON and press [Enter] again. The reason this command is being added is because NetWare 4.x servers will not attaempt to scan or use RAM above 16MB unless they are given explicit permission to do it. If the server crashes with this command in the STARTUP.NCF, then it can be changed to register the exact amount of RAM in the system. The situation should look something like this:

Verify that the command is exactly as shown above and then press [F10] to save the changes and continue. After the changes are written to the STARTUP.NCF file a dialog box appears asking: Add commands to AUTOEXEC.BAT to load SERVER.EXE? Be sure that "No" is highlighted and press [Enter]. Otherwise, the DOS bootup of the system will automatically launch the server which may not always be desired. Since it is easy enough to launch manually and should not be starting up and shutting down often anyway, this choice should be left out and the server can be manually launched when necessary. At this point the NetWare 4.11 Server itself is launched and automatically loads the Netware executable, called a NetWare Loadable Module or NLM, to continue the installation process. It will scan the system for devices that it recognizes and load the appropriate drivers. The appropriate commands to load these drivers in the future will automatically be added to the startup files. When this process is complete the screen should look like this:

This is talking about the SiS NIC on the motherboard which will be disabled on the next reboot so this can be ignored. Later, how this was determined will be demonstrated. In the meantime press [F3] to continue.

The next screen entitled "Choose the Server Drivers - Summary should indicate that the Disk and CD-ROM Drivers name is IDEATA and that the network (LAN) Drivers name is 3C90X. If this is the case then press [Enter] to continue.

At this point the system loads the drivers that it has listed. With the network interface driver up nd running the system begins a detection process on the network. Once complete the system stops at the "Protocol Selection" screen. It indicates that the driver 3C90X_1 will use IPX by default, indicated by the asterisk because IPX activity was not encountered on the network as expected. This system will be started with only its native IPX protocol. IP can be added later anyway. Press [Enter] to continue with the installation.

This screen will be used to create the partitions for the operating system and is the NetWare equivalent of FDISK. It is just as powerful and just as miserable to use. It is also just as bad if the partitioning is messed up at any point along the way so pay careful attention to detail here. Choose "Manually" and then press [Enter]:

On this screen select the "Create, delete, and modify..." choice and press [Enter]:

An "Available Disk Drives" box appears. In the lab exercise there is only one physical disk, but on a system with multiple drives you could select the disk on which to create/delete/or modify NetWare partitions. Press [Enter]

On this screen the current partition table of the drive is listed in the upper box and the actions that can be taken are listed in the lower yellow bordered box. Select the "Create NetWare disk partition" with the arrow keys and press [Enter]:

In the resulting box the system displays the planned NetWare partition. If the entire drive is going to be used by NetWare, then accept the default which wants to take the entire available free space. Even if you plan to create multiple volumes do this because the volumes are created within the NetWare partition much like logical drives are created within an Extended DOS partition. NetWare will not create more than one NetWare Partition on a physical disk so if the entire disk is not taken now, and the installation continues and later this must be changed then the entire installation must be performed again. Accept the entire drive by pressing [F10] A confirmation box opens asking "Create NetWare partition?" with "Yes" highlighted, press [Enter] to accept the creation of the partition.

This returns to this screen which now lists a NetWare Partition where the free space used to be listed:

Press [Esc] to return to the previous screen now. This returns to the "Disk Partition and Mirroring Options" menu. Highlight "Continue with installation" and press [Enter]:

This indicates that the entire partition was used to create the default volume named SYS in which the operating system itself will be installed. Contrary to the advice on this screen you cannot proceed to install the operating system without a SYS partition, but it will be reduced in size and another volume named DATA wil be created. Press [Enter] and the following screen appears in which volumes can be created, deleted or modified:

Press [F3] and this new screen appears that will allow the volume to be modified (as well as be deleted):

Press [Enter] to make a change on the volume segment. Notice the "N" under the Status column indicating that this is a new volume which is why it can be changed at this point. If it were a previously existing one then its size could not be changed, just like with FDISK. The "disk segment parameters" dialog box has appeared with the segment size highlighted. Change the size to 1500 and press [Enter] and then press [F10] to save the changes. This returns to the main volume segment screen that now indicates the existence of free space in the partition.

Highlight the free space and press [Enter] A dialog box opens asking you: "What would you like to do with this free segment?" and the choices are "Make this segment a new volume" (highlighted) or "Make this segment part of another volume". Press [Enter] to create a new volume. This opens the "Disk segment parameters" dialog box again, with the empty name field highlighted. Type in "DATA" (no quotes!) and press [Enter] then [F10]. This returns to the Modify Volume Disk Segments screen again and the situation should look like this:

The set of volumes are what are desired at this point so press [F10] to save the changes. This returns to the previous "Manage NetWare Volumes" screen. Press [F10] again. At this point a confirmation dialog box appears asking "Save volume changes?" Highlight "Yes" and press [Enter]. The system builds the volumes, mounts them (making them immediately available upon creation) and begins copying system files to the SYS volume. A message screen appears indicating that if the source path is different it can be changed at this point. Press [Enter] to accept the indicated path. The preliminary file copy begins that copies all of the major NetWare 4.11 Server files to the SYS volume.

Once the preliminary file copy is complete, the system asks whether NetWare Directory Services will be installed, whether the system will connect to another NDS tree or whether the NDS database should be repaired on the current system.

Be sure to highlight "Yes, this is the first NetWare 4 server" and press [Enter] This begins the process of building the first NDS tree. The name of your tree must be unique so name it LABx where x is the number of your station:

Press [Enter] to save the new NDS tree name. The next screen appears which needs the correct time zone. NetWare networks definitely depend on a well synchronized time system between all computers on the network even more so than a Windows based network. Press the letter [U] then use the down arrow to move the selection to "United States of Amnerica, Eastern Time" then press [Enter]. The next screen allows the time zone configuration settings to be modified. Everything should be correct so press [F10] to continue.

On this next screen the NDS tree structure needs to be built. Enter the organization name as "RM6359" (no quotes!) and press [Enter]. You do not need any of the Sub-Organizational Units at this point. Press the down arrow until the Administrator's password field is highlighted:

Type in "admin" as the password and press [Enter]. A dialog box prompts you to type it again. Do so and press [Enter]. A dialog box appears prompting you to save the directory information and continue, be sure "Yes" is highlighted and press [Enter]. The system proceeds to install NDS on the server. When done a summary report is displayed on screen. You must write down the Directory tree name, Directory context and the Administrator names exactly as they are displayed. If you forget this information you will not be able to access the server (and that means you will be reinstalling all over again). After writing this information down press [Enter] to continue the installation.

This screen asks for the server's license. This is normally a diskette included with the OEM product package. Novell servers are sold by the number of concurrent users that can be logged in to them. A 5-user server would allow up to a maximum of five users to be logged onto it at the same time. A 50-user server would allow up to 50 users to be logged on simultaneously. Obviously the 50-user server costs more (exactly 10 times more) than the 5-user server. All of the installation CD-ROMs are identical, the diskette provided at this point provides the server with its unique product key and the number of concurrent logged on users that it will allow. The server will refuse to allow the sixth user to log on if five are already logged on with a 5-user license. This is completely different from the behavior and licensing scheme developed by Microsoft for the Windows NT family of operating systems. Since this is the 2-user demo version included with the Novell press book "Novell's Guide to NetWare 4.11 Networks" no license diskette is provided, press [F9] to proceed with the installation without a license diskette:

The next screen displays the final version of the STARTUP.NCF that the installation process plans to leave on the server for it to use on the next start up. Record the commands exactly as they are displayed on screen and then press [F10] to save the file to disk. Should the system give problems due to loading incorrect drivers the lines you write down will be needed in order to determine which one is incorrect. upon pressing [F10] a confirmation dialog box appears, be sure "Yes" is highlighted and press [Enter].

The next screen displays the proposed AUTOEXEC.NCF for the server. Scroll the screen down by pressing the down arrow to move the cursor downward. Note that the 3C90X driver is loaded twice. Once to set it up using the "802.2 Ethernet frame type and then again to set it up using the 802.3 Ethernet frame type. The BIND command after each driver launch loads the IPX/SPX proocol drivers and binds them to that copy of the driver in RAM. Copy these four lines as they identify the NIC drivers, protocols, and IPX network numbers that the server will be using. Then press [F10] to save the file and agree to the confirmation dialog box.

At this point the server has all information that it needs to complete the installation and the main file copy begins. Note the source path of the main file copy is: NW411:\PRODUCTS\... The NetWare CD-ROM driver loaded earlier and the server has been using it to access the CD-ROM. The server fully understands the DOS kernels drive letters that were created in the DOS boot up of the C: drive prior to launching it and DOS paths can be used to load modules from the floppy, hard drive or CD-ROM. If the CD-ROM is removed while the server is accessing it using its own driver, the server can lock up so this should definitely be avoided. Also, remember that the NetWare operating system is a full 32-bit protected mode operating system. As usch it is very capable of being damaged if it is not properly shut down, just like Windows. Because of the server's extremely large and efficient file caching in RAM, it is almost certain that on large networks a power outage or turning the server off improperly will result in damaged files including the OS kernel files. Since the NetWare File System is an industry secret this could cause a total catastrophe in a business environment.

When the main file copy ends the installation program offers the user to select any additional components or even third party products to be installed. No other OEM or third party products will be installed at this time so be sure that the "Continue installation" choice is highlighted and press [Enter]

This screen indicates that the installation process is complete. Novell recommends that when the special installation program or NetWare Loadable Module ends and control returns to the server console that the server should be properly shut down and that the computer should be rebooted. Press [Enter] to exit the installation program and return to the server console now.

At the server console prompt type the command "DOWN" to bring the server down (to stop it from serving on the network) and then type the command "EXIT" to unload the server from RAM and return control to DOS:

     The time exchange was ignored!
2-09-05   1:58:44 pm:     DS-5.73-28
    Bindery open requested by the SERVER
2-09-05   1:58:44 pm:     DS-5.73-50
    Established communication with server FS2.RM6359
2-09-05   1:58:44 pm:     DS-5.73-26
    Directory Services:  Local database is open
Novell NetWare 4.11 August 22, 1996
(C) Copyright 1983-1996 Novell Inc.
All Rights Reserved
Patent Pending - Novell Inc.
2-09-05   1:59:07 pm:     SERVER-4.11-3537
    The Main Server License file (MLS.000) could not be found.
    Maximum connections has been reduced to ONE.
FS2:down
Notifying stations that file server is down
Downing the router...
Dismounting volume DATA
2-09-05   3:12:30 pm:     DS-5.73-30
    Bindery close requested by the SERVER
2-09-05   3:12:30 pm:     DS-5.73-27
    Directory Services:  Local database has been closed
Dismounting volume SYS
2-09-05   3:12:35 pm:     SERVER-4.11-2009
    FS2 TTS shut down
    because backout volume SYS was dismounted.
Type EXIT to return to DOS.
FS2:exit

At this point the screen clears and the DOS prompt returns. Press [Ctrl]+[Alt]+[Delete] to reboot the system. At the DOS prompt, notice the PCI device listing will indicate a device with manufacturer ID of 1039 and a device ID of 0900. the device description (or class) is network controller. Check these numbers against the ones that the server install reported when it displayed the message that it could not find a driver for a PCI device. The number that the server used to identify it started with 1039.0900... and this screen reports it as one of two PCI NIC's on the machine. The other one with manufacturer 10B7 and device ID 9050 must therefore be the 3COM 3C905 that the installation detected and found drivers for and this other one is the SiS 900 NIC built into the motherboard. Reboot the machine and disable the onboard NIC in the BIOS and restart the machine again.

Once the system is back at the C:\> prompt, change to the NWSERVER directory and then type SERVER and press [Enter] to restart the server. Once the console prompt reappears with the server's name followed by a colon and the cursor then the server is up and running again. Now proceed to the next portion of this exercise to install the Novell Client32 for Windows on a Windows 98 machine in the lab.

Attach the CAT5 UTP patch cable to the 3COM NIC (it occupies an expansion slot and it is NOT the one on the motherboard near the keyboard connectors) and attach the other end of the cable to the wall jack that the instructor indicates. At this point the system should be attached to the interface to the college network. As such the student must abide by MDC's network rules, regulations and policies. If the following steps are performed without visiting any other websites or performing any other activities on the system, then the student should not violate any MDC Network rules, regulations, or policies.

Start up the system and check to be sure that the TCP/IP protocol has received a valid IP address from the network's DHCP server(s). Click Start > Run > "winipcfg" (no quotes!) > OK. Select the 3COM NIC from the drop down box and the IP address should NOT be an APIPA address which starts with 169.254.???.??? If it is different then it has received an address from the network DHCP servers. Close winipcfg.

Right click on the "Connect to the Internet" shortcut on the desktop and select Properties. In the properties sheet change the executable's name from:

...\Icwconn1.exe" /oobe

to instead read:

...\Inetwiz.exe" 

Note: the /oobe switch should be deleted but NOT the double quote character. Apply the change and close the properties sheet.

The icon will change to reflect that the shortcut points to a different Internet Connection Wizard. This one is the one capable of configuring Internet Explorer to connect to the Internet through a the NIC on the system over a LAN which is the case in the lab. The original one assumes that IE will be configured to connect over a modem installed on the system which is NOT the case. Hence the need to change to the other Wizard.

Now double click the shortcut's icon to start the Wizard. Select the choice that mentions connecting using a LAN and then click Next.

Click next on the screen offering the checkbox to use Automatic discovery of the Proxy settings.

On the screen offering to set up Internet Mail be sure to select "No" and then click Next again. Click Finish on this last screen and the Wizard closes. Now double click on the Internet Explorer icon on the desktop and IE should connect to Microsoft's website looking to install an update. Say "No" to everything until it stays quiet.

The system is now on the Internet. Type in the following address into the address bar and then hit enter:

http://download.novell.com/index.jsp

Click the link on the page to Novell Client 3.4 English and on the resulting page Click the download button to the far right on the row with the file's name. You may need to scroll right to see it. In the file download box click save file to disk and then the OK button. In the Save As dialog box direct it to be saved in My Documents.

The file is over 15MB but will not take long on the college backbone. When the down load is complete properly shutdown the system and unplug the patch cable from the wall jack for the college backbone and reconnect it to the isolated room network jack as directed by your instructor and then restart the PC.

Once the system is at the desktop, open My Documents and double click on the downloaded file. This opens the Winzip Self Extractor. Click the Unzip button and notice that it plans to extract the files into the C:\WINDOWS\TEMP folder. When done it indicates that 494 files were extracted successfully. Click OK and open the Windows\Temp folder. Now open the WIN95 folder. Now open the ibm_enu folder. Scroll down to the setup program icon and double click it:

The license agreement opens. Agree to it and then the setup wizard begins. On the Welcome screen select the custom radio button and then click Next:

On the "Protocol Preference" screen select the IPX (only) checkbox and click Next:

On the "Login Authenticator" screen select NDS. This is the method that Netware 4.x servers use which is completely different from the bindery method used by Netware 3.x servers. Since the above exercise established a Netware 4.11 server, NDS will be the authenticator for this client. Click Next:

On the Optional components screen do not select any other items for this exercise and click the Install button:

Windows drivers from the installation CAB's are needed by the Novell Client32 and it will request them. Insert the student CD-ROM and when the path dialog box appears, type in the path as D:\WIN98SE and press [Enter] Several operations ensue including the removal of the existing client then the addition of the new client. This is followed by the message on how to configure the client with recommendations based on which type of authentication server is on the network. Click Yes:

This opens the Client32 Properties sheet to the main tab that is needed. Fill in the preferred server as the name of the server created in the server installation exercise above (that should be up and running on the network), the NDS tree as LABx (the one created in the server install above) and the name context as O=RM5359 (that is the letter "oh" for organization in the NDS tree nomenclature), and leave the first network drive letter as "F" and click OK:

Now the main client installation takes place followed by the installation wizard's final screen:

At the desktop, open the Network Neighborhood and the server and the NDS tree objects will be visible:

Close the Network Neighborhood window and right click on the desktop and select New > Shortcut. In the commandline window click the browse button and open the F: drive. Now open the public folder, then scroll to the file named NwAdmn3x.exe and double click it. Name the shortcut Nwadmin and finish the shortcut. Once it appears complete on the desktop double click it and it will open the Netware Administration Utility. This program can be used by the Admin of the network to manage the entire network. The view should look very similar to this: