TR Troubleshooting - File Server Problems 

Is there a problem on the network file server with a ring station, group of ring stations, the complete network, or a network peripheral accessing or using a particular application/group of applications, or certain directories/files?
Go to page 14.1. 

Is a particular network operating system (NOS) feature or set of NOS features on the network file server not working?
Go to page 14.2. 

Is there a problem accessing or using an extra network server other than the main network file server (for example, database, fax, communication, print server)?
Go to page 14.3. 

 Does there appear to be a problem with abnormal network bandwidth between a particular ring station/group of ring stations and the network file server, or between a network peripheral and the network file server?
Go to page 14.4. 

This procedure is generic as to the network operating system (such as Novell, IBM LAN Server, Microsoft LAN Manager, and Banyan VINES). When you reference some of the troubleshooting steps on this page, you should also reference the NOS manufacturer's documentation for any special predefined methods for checking NOS configuration, hardware/software requirements, and for NOS diagnostics and testing. 



14.1 There is a problem with a ring station, a group of ring stations, the entire network, or a network peripheral accessing or using a particular application/group of applications, or certain directories/files on the network file server.

First, check the network file server and any symptomatic ring stations for the following software and hardware configuration setup parameters and requirements:

    * Make sure that the NOS network shell software, NOS NIC drivers, CONFIG.SYS, AUTOEXEC.BAT, and all the necessary network operating system files are set up for the respective NOS specialized configuration and NOS hierarchical directory structure.
    * Check the NOS directory structure as it relates to the ring station and any respective network peripheral access.
    * Check all the NOS security rights configurations.
    * Make sure that all the necessary directories/files for all NOS applications on the network drive and ring station drives are set up correctly.
    * Make sure that all the necessary hardware is installed in the file server/ring stations, configured correctly, and functioning properly. 

Check the respective NOS manuals for file server setup concerning network-software-vendor requirements for both software and hardware prerequisites and their respective configurations.

Are any identifiable hardware or software configuration setup problems with the network file server?

Take the necessary action to resolve the configuration problem and retest the ring for proper operation. If the failure symptom is gone, record the problem in the network maintenance and service log. If the failure symptom still exists, go to the next step .

If there appears to be no problem with the file server or its setup, attempt to gather more conclusive fault-isolation data by running a protocol analysis session on the ring. Go to page 15 and focus on the problem by capturing and viewing the high-layer communication processes.
If after using this page you cannot conclusively locate the problem and continue to find failure symptoms that point to the network file server problem, reference both the NOS software and the particular file server/hardware manufacturers' instructions.



14.2 A particular network operating system (NOS) feature or set of NOS features on the network file server is not working.

First, fully reference the respective NOS manuals for operation of the NOS feature or features.

In checking the NOS manuals, did you find any operational instructions to resolve your problem?

Take the necessary action to resolve the problem and retest the NOS feature for proper operation. If the failure symptom is gone, record the problem in the network maintenance and service log. If the failure symptom still exists, go to the next step .

Check the NOS manuals for file server setup concerning network-software-vendor requirements for both software and hardware prerequisites and their respective con figurations.

Are there any identifiable hardware or software configuration setup problems with the network file server?

Take the necessary action to resolve the configuration problem and retest the NOS feature for proper operation. If the failure symptom is gone, record the problem in the network maintenance and service log. If the failure symptom still exists, go to the next step .

Contact your NOS support channel for assistance in using and configuring this particular NOS feature.



14.3 There is a problem accessing or using an extra network server other than the main network file server (for example, database, fax, communication, or print server).

Is the file server involved on a non-local ring that is bridged, routed, or connected through a remote connection?

Go to S1.

Go to S2.

S1
File server is on a nonlocal ring that is bridged, routed, or connected through a remote connection.

First, verify that the particular bridge, router, or remote connection link is functioning properly. If necessary, go to the respective page for the particular device: pages 7 Bridge ; 8 Router ; 11 Modem .

Are there any problems with the linking devices, specifically the bridge, router, or communication (modem) devices/links?

Take the necessary action to resolve the problem and retest the respective network file server for proper operation. If the failure symptom is gone, record the problem in the network maintenance and service log. If the problem still exists after retesting, go to the next step .

Go to S2 and follow the troubleshooting steps as though the remote file server were actually located on the local ring.

S2
File server is on the local ring.

First, check the network file server for the following software and hardware configuration setup parameters and requirements:

    * Make sure that the NOS network shell software, NOS NIC drivers, CONFIG.SYS, AUTOEXEC.BAT, and all the necessary network operating system files are set up for the respective NOS specialized configuration and NOS hierarchical directory structure.
    * Check the NOS directory structure as it relates to the ring station and any respective network peripheral access.
    * Check all the NOS security rights configurations.
    * Make sure that all the necessary directories/files for any NOS applications on the network drive are set up correctly.
    * Make sure that all the necessary hardware is installed in the file server, configured correctly, and functioning properly. 

Check the respective NOS and software application manuals for file server setup concerning network-software-vendor requirements for both software and hardware prerequisites and their respective configurati ons.

Are there any identifiable hardware or software configuration setup problems with the network file server?

Take the necessary action to resolve the configuration problem and retest the ring for proper operation. If the failure symptom is gone, record the problem in the network maintenance and service log. If the failure symptom still exists, go to the next step .

If no problem appears to be with the file server or its setup, attempt to gather more conclusive fault-isolation data by running a protocol analysis session on the ring. Go to page 15 and focus on the problem by capturing and viewing the high-layer communication processes.
If after using this procedure you cannot conclusively locate the problem and continue to find failure symptoms that point to the network file server problem, reference both the NOS software and the particular file server/hardware manufacturers' instructions. 



14.4 There appears to be a problem with abnormal network bandwidth between a particular ring station/group of ring stations, or network peripheral, and the network file server.

First, check the network file server for the following software and hardware configuration setup parameters and requirements:

    * Make sure that the NOS network shell software, NOS NIC drivers, CONFIG.SYS, AUTOEXEC.BAT, and all the necessary network operating system files are set up for the respective NOS specialized configuration and NOS hierarchical directory structure.
    * Check the NOS directory structure as it relates to the ring station and any respective network peripheral access.
    * Check all the NOS security rights configurations.
    * Make sure that all the necessary directories/files for all NOS applications on the network drive are set up correctly.
    * Make sure that all the necessary hardware is installed in the file server, is configured correctly, and is functioning properly. 

Check the respective NOS and software application manuals for file server setup concerning network-software-vendor requirements for both software and hardware prerequisites and their respective configuration.

Are there any identifiable hardware or software configuration setup problems with the network file server?

Take the necessary action to resolve the configuration problem and retest the ring for proper operation. If the failure symptom is gone, record the problem in the network maintenance and service log. If the failure symptom still exists, go to the next step .

Check the file server NIC buffer space specifications to see if they meet the NOS and software application manufacturers' requirements for the ring user population and access.

Is the file server's NIC low on required buffer space for the NOS or particular application's operation?

Take the necessary action to resolve the problem and retest the ring for proper operation. If the failure symptom is gone, record the problem in the network maintenance and service log. If the failure symptom still exists, go to the next step .

Attempt to gather more conclusive fault-isolation data by running a protocol analysis session on the ring. Go to page 15 and focus on the problem by capturing and viewing the high-layer communication processes and the baseline network bandwidth.
If after using this procedure you cannot conclusively locate the problem and continue to find failure symptoms that point to a network file server problem, reference both the NOS software and the particular file server/hardware manufacturers' instructions. 

 November 15, 1996 

Content created and/or collected by:
Louis Ohland, Peter Wendt, William Walsh, David Beem, Tatsuo Sunagawa, Jim Shorney, Tim Clarke, Kevin Bowling, Tomáš Slavotínek, and many others.

Ardent Tool of Capitalism - MAD Edition! is maintained by Tomáš Slavotínek.
Last update: 19 Nov 2021 - Changes & Credits | Legal Info & Contact