Upcoming Events

Cloud Connect
Santa Clara
Feb 13-16, 2012

Cloud Connect brings together the entire cloud eco-system to better understand the transformation we're experiencing and promises to be the defining event of the cloud computing industry. Learn about the latest cloud technologies and platforms from thought leaders in Cloud Connect’s comprehensive conference.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up

A failure symptom appears to be directly related to a problem with a specific network peripheral.


Is the network peripheral involved in some network communications with a particular application, or is it using the same directory or file on a particular file server when the symptom occurs?

Troubleshoot a possible file server application or directory/file problem that may be related to the network peripheral operation.

Move the network peripheral to another port on the repeater or wiring hub and recheck the network peripheral operation.

Did moving the network peripheral to another port resolve the problem?

Troubleshoot a possible repeater or wiring hub problem.

Troubleshoot the respective node segment cable-drop area involved. First, check and replace any external transceivers and then test again. If problems still exist, check the cable drop. If troubleshooting the segment cable does not identify any problems with the segment cable, come back to this page and go to the next step.

Next , test the respective network peripheral for proper software and hardware configuration setup and requirements.

If the network peripheral has local disk storage, make sure that all the necessary directories and files for the network peripheral are set up correctly.

Make sure that all the necessary hardware is installed in the network peripheral and is configured correctly.

Check the network operating system manuals for network peripheral setup concerning both software and hardware prerequisites.

Did rechecking the network peripheral software and hardware requirements find any incorrect configuration setup problems?

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

Attempt to run any available network peripheral diagnostics. Also try to troubleshoot the network peripheral for any I/O board conflicts.

Did running the diagnostics or troubleshooting the network peripheral find any problems?

Take the necessary action to resolve the problem and retest the network peripheral 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.

Has the NIC in the assigned network peripheral been troubleshot?

There may be a network file server-to-network peripheral-related problem as to network access or protocol communication. Perform a protocol analysis session and focus closely on the communication between the network file server and the assigned network peripheral.

Troubleshoot the respective network peripheral station for an NIC problem.

Many network peripherals are being manufactured with internal NICs within the respective logic board hardware architecture. If the network peripheral you are troubleshooting has this configuration, just attempt to replace the motherboard rather than troubleshooting the NIC.

If after using these procedures you cannot conclusively locate the problem and continue to find failure symptoms that point to a network peripheral problem, refer to the manufacturer's instructions.

November 15, 1996

Print This Page


e-mail E-mail this URL

Research and Reports

Hypervisor Derby
August 2011

Network Computing: August 2011

TechWeb Careers