You have trouble 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 nonlocal segment that is bridged, routed or connected through a remote connection? File server is on a nonlocal segment 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 procedures for the particular device: bridge , router , modem . Are there any problems with the linking devices, specifically the bridge, router or communication (modem) devices or 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. Follow the troubleshooting steps as though the remote file server were actually located on the local segment. File server is on the local segment. 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 Ethernet station node 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 configurations. Are there any identifiable hardware or software confi guration setup problems with the network file server? Take the necessary action to resolve the configuration problem and retest the segment for proper operation. If the failure symptom is gone, record the problem in the network maintenance and service log. If the failure symptom is still present, 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 segment. Focus on the problem by capturing and viewing the high-layer communication processes. If after using these procedures and running a protocol analysis you cannot conclusively locate the problem, and you continue to find failure symptoms that point to the network file server problem, reference both the NOS software and the particular file server/hardware manufacturer's instructions. November 15, 1996 Print This Page E-mail this URL