Basics for Ethernet problems

Gather information before troubleshooting. As with any troubleshooting procedure, the first step when examining Ethernet problems should be a comprehensive collection of information. This process should result in a detailed description of the symptoms and usually delivers first clues to possible causes. Questions to ask at this stage include:Do the symptoms occur regularly or intermittently?Are the symptoms related to certain applications (running simultaneously with?), or do they affect all network operations?Behavior of similar applications?How many users are involved?Do the symptoms correlate to other activities in the network?When was the first occurrence of the symptom?Was there any change in any hardware or software network component?Has anyone connected or disconnected a PC (laptop or desktop) or any other component to or from the network?Has anyone installed an interface card in a computer?Has anyone stepped on a cable? - Has any maintenance work been performed in the building recently (by telephone company or building maintenance personnel, for example)?Has anyone (including cleaning personnel) moved any equipment or furniture?