GLOBALNET SPPORT
 
 

GLOBALNET™ Frequently Asked Questions

 

  • What should I do if GLOBALNET locks during autoconfiguration?
    1. Turn off all power to the unit and attached devices. Wait a few minutes, then power on the devices, followed by the GLOBALNET unit itself.
    2. Check all cable connections for proper contact.
    3. Check the network for possible problems that could affect servers and clients.
    4. If the problem persists, call Optisys Technical Support.

  • What if GLOBALNET fails to successfully identify and configure the SCSI device(s) attached?
    1. Make sure each device is properly terminated and turned on.
    2. Check all cable connections for proper contact.
    3. Make sure the total SCSI cable length does not exceed 9 feet.
    4. You may have an unsupported device. Call Optisys Technical Support for assistance.

  • What if GLOBALNET does not appear on Novell's S-LIST?
    1. It is possible that GLOBALNET has not completed autoconfiguration. Try again in a few minutes.
    2. Are the physical network links good? Verify that a client attached to the same cable as the GLOBALNET server can see other network servers. Simply unplug the network cable from the GLOBALNET server and plug it into the client workstation instead. Can the client workstation attach to the network? If not, the physical connection might be the problem. If the server still does not advertise, and the devices stop or fail to inventory, disconnect the devices and reset the server.
    3. There may have been a failure during autoconfiguration. Turn off all power to the unit and attached devices. Wait a few minutes, then power on the devices, followed by the GLOBALNET unit.
    4. If the server still does not advertise, and the devices stop or fail to inventory, disconnect the devices from the server and reset the server. As soon as the server advertises, attach the devices to the SCSI port. Using the GLOBALNET server's Console utility, select the Device Configuration utility from the Server Management menu to manually configure the devices.

  • GLOBALNET does not appear on the RCONSOLE list.  Now what?
    1. Refresh RCONSOLE's server list by pressing X twice.
    2. If RCONSOLE still fails to list the GLOBALNET server due to too much network traffic, create a private LAN with the GLOBALNET server, a client workstation and a NetWare server that has the RCONSOLE utility installed.

  • What do I do if I get an error message "OptiDriver is not loaded" while in the Media Management menu?
    1. Check the SCSI devices for the proper SCSI ID settings. The robotics SCSI IDs must be set prior to the drive IDs in jukeboxes.
    2. If you are attaching multiple devices on the GloBalnet server, try a stand-alone device first, i.e., a CD-ROM drive, an optical drive.
    3. The attached SCSI devices must be turned on and in the ready state before the GloBalnet Server is turned on.

  • Why is the system getting slower and slower?
    1. Check to see if the SCSI log file is turned on. Use the Console utility. Select the Server Management menu, and check the Turn On/Off SCSI Log option. It should read Turn On SCSI Log.
    2. If the menu option is listed as Turn Off SCSI Log, move the highlight to the option and press E. The menu option should now read Turn On SCSI Log. SCSI requests will no longer be logged in the SYS$LOG.ERR file.
    3. You may need to go to the SYS:SYSTEM directory and delete the SYS$LOG.ERR file to free up space on the hard drive.

  • When I'm doing a server module upgrade, the upgrade fails and I'm returned to a DOS prompt. What's wrong?
    1. Check to see that the COMMAND.COM file is present in the C:\ root directory.
    - or  -
    2. If you're running the upgrade from Windows, check to see that the COMMAND.COM file is located in the Windows directory, where the upgrade looks for it.   Make sure the Windows directory is included in your path statement.
    - or -
    3. Edit the install B.BAT file, modifying the line that looks for the COMMAND.COM file.

  • My network clients are attaching to the GloBalnet server as the primary server. How can I remedy this?
    1. In the SYS:SYSTEM directory, open the file SERVER.CFG. Change the line

NEAR QUERY = AUTO

to

NEAR QUERY = NO

  • The Windows 3.1 File Manager and Windows 95 Explorer report media Free Space incorrectly. If I check Free Space at the DOS level I get an accurate accounting. How can I resolve the discrepancy?
    1. From the GloBalnet SYS:SYSTEM directory, copy the file GNAPI.VXD into the Windows directory.
    2. Edit the SYSTEM.INI file. In the [386 Enh] section, add the following line in lowercase:

device=c:\windows\gnapi.vxd

  • I have an NSM jukebox. Every time I turn the GloBalnet server off, then on, the jukebox does a re-inventory. How can I stop this?
    1. Log in as Supervisor.
    2. Map a drive to the SYS volume.
    3. Change to the OPTISYS\OPTIDRVR directory.
    4. Open the OPTIDRVR.CFG file.
    5. Add the following to the end of the Robotics statement line:

noreinventory

 
 
 

Back To Top

HOME