Follow Up After File Server Software Installation

Once the STARTUP.NCF and AUTOEXEC.NCF files have been created, complete the following tasks that apply to your network configuration.


Procedure

  1. Add name space support to the volume.

    If your network includes workstations that use an operating system that supports long filenames, use the ADD NAME SPACE command to add the name space to the volume. At the console prompt, type

    ADD NAME SPACE name_support TO VOLUME volume_name <Enter>

    Use this command for every volume that stores files using non-DOS naming conventions.

    For example, if you have a volume named MAC for Macintosh files, type

    ADD NAME SPACE MACINTOSH TO VOLUME MAC <Enter>

    Then add the command to your AUTOEXEC.NCF file.

  2. Add Macintosh support.

    To store Macintosh files and folders on a NetWare v3.12 file server, install NetWare for Macintosh (a separate Novell product) on your file server.

    This product provides native-mode support for Macintosh workstations that connect to the server.

  3. Lock your file server keyboard.

    To prevent others from tampering with the file server, load MONITOR and select "Lock file server console" from the "Available Options" menu.

    For additional security tips, see "Secure Console" in System Administration.

  4. Prepare for power fluctuations.

    If you do not have a UPS attached to your file server, be prepared to

    • Run VREPAIR from either the DOS partition on the hard disk or diskette. Power outages can corrupt File Allocation Tables and directory tables.
    • Make at least daily backups to protect your data. Power outages can destroy a volume.
    • Make an additional backup of the bindery on a diskette. Sometimes third-party backup devices do not back up the bindery.
    • Run BINDFIX. Power outages can corrupt the bindery. Restore the bindery from a backup if BINDFIX doesn't work.

  5. Update all workstation shells or VLMs.

    See Workstation Basics and Installation.

  6. Further customize the configuration.

    Read about the following commands in System Administration:

    "INSTALL"

    Performs installation tasks, including creating disk partitions, creating volumes, formatting a hard disk, etc.

    "MONITOR"

    Locks the file server console and shows how efficiently your network is operating.

    "SET"

    Displays operating system parameters and configures the operating system to fit your situation.

    "SPEED"

    Displays the processor speed rating (see "Speed" in System Administration).

    "SPOOL"

    Creates, changes, or displays spooler mappings.


Copy NetWare v3.12 Utilities to NetWare v2.x Servers

This ensures compatibility between NetWare v3.12 servers and NetWare v2.1x servers on the same network.


Procedure

  1. Log in to the NetWare v2.x file server.

  2. Flag the NetWare v2.x utilities Normal. In the SYS:LOGIN and SYS:PUBLIC directories, type

    FLAG *.* N <Enter>

  3. Map a drive to volume SYS: on the NetWare v3.12 file server by typing

    MAP Q:=fileserver/SYS:PUBLIC <Enter>

    Replace Q with a letter not being used and fileserver with the name of the NetWare v3.12 file server.

  4. Enter your username and password for the NetWare v3.12 file server.

  5. Copy the NetWare v3.12 utilities from the SYS:PUBLIC and SYS:LOGIN directories to the same directories on the NetWare v2.x file server.

  6. Flag the new utilities on the NetWare 2.x file server Shareable, Read Only by typing

    FLAG *.* S RO <Enter>

  7. (Conditional) If all workstations are running the latest requestors (VLMs) or shells (NETX), remove the SET parameter allowing for unencrypted passwords from the AUTOEXEC.NCF file.

    You created this SET parameter in Step 5.

    NOTE:  The SET parameter to allow unencrypted passwords will not take effect until the server has been rebooted.

    To avoid rebooting, you may want to enter the SET command at the console prompt.


Troubleshooting


Hard disk

If you cannot access a hard disk, check


Volume errors

If you get disk errors when mounting a volume, check the memory in the file server by loading MONITOR. You should have 20% or more available cache buffers.


Communication problems

If the file server can't communicate with the rest of the network, check to see that

For more help, see "Troubleshooting Guide" in System Administration.