|
#1
|
|||
|
|||
|
How to test a Ethernet connection?
I have two PCs connected to a switch, the switch is connected to ADSL modem/router, all works OK.
I cannot use the 100 Mbits speed between PCs, only 10 MBits. In Windows XP SP2, I saw a test of Ethernet cable, it shows "you have a problem at one meter of distance" or some by the style, your signal/noise rate is xx dB, etc. But I don't know what Windows XP service did the test, I cannot reproduce it. Can anybody help me? Thanks. |
|
#2
|
||||
|
||||
|
I believe you were looking at a wireless diagnostic, not an ethenet.
What is the switch you are using (try to find a make and model)?
__________________
NETWORKING FORUM: If you haven't already done so, please goto this topic and post the requested information. And yes, it is all relavent. "Yea though I walk through the valley of the shadow of death... I will fear no evil." -Psalms 23 K8N Diamond Plus (BIOS v1.2) AMD Athlon 64 X2 4400+ Antec TruControl 550W NVidia GeForce 7900GT (NGO v1.8466 BETA) OCZ Platinum 2x1GB (2-3-2-5) SATA: 2xWD740 PATA: 2xWD2500, WD1200, NEC DVD/RW |
|
#3
|
||||
|
||||
|
It may be that your network card came with some diagnostic software. Sometimes you can access the diagnostic software from the properties of the network connections. I don't remember exactly where I've seen it, but I can check a system that has it and post back later today or tomorrow.
__________________
cmd /k ipconfig/all [use to start ipconfig from 'Run'] cmd /k ping <some website, like google or yahoo> [use to ping 'www.google.com' from 'Run'] |
|
#4
|
|||
|
|||
|
Quote:
Thanks you by any help. |
|
#5
|
||||
|
||||
|
That chipset does support onboard diagnostics, even so, I've never seen a line test use SNR... although, I suppose it would be useful.
The diagnostics software you have is probably in the Intel Pro Set Configuration Utility.
__________________
NETWORKING FORUM: If you haven't already done so, please goto this topic and post the requested information. And yes, it is all relavent. "Yea though I walk through the valley of the shadow of death... I will fear no evil." -Psalms 23 K8N Diamond Plus (BIOS v1.2) AMD Athlon 64 X2 4400+ Antec TruControl 550W NVidia GeForce 7900GT (NGO v1.8466 BETA) OCZ Platinum 2x1GB (2-3-2-5) SATA: 2xWD740 PATA: 2xWD2500, WD1200, NEC DVD/RW |
|
#6
|
||||
|
||||
|
I"m not sure what software it came with, but I can access my diagnostic software by going to the device manager and opening the properties for the NIC. In the dialog that comes up I have a diagnostics tab.
__________________
cmd /k ipconfig/all [use to start ipconfig from 'Run'] cmd /k ping <some website, like google or yahoo> [use to ping 'www.google.com' from 'Run'] |
|
#7
|
|||
|
|||
|
Quote:
Thanks you. Well, I found this in a INTEL subdirectory. I repaired the installation of drivers and the test is done as before. --------- Test signal quality and show cable status: This is an online test. This means that the adapter does not lose link during the test. If a result is not displayed, it is unavailable for the selected adapter. The results from this test include: Cable Length: Displays the approximate length of the cable between the adapter and its link partner. If the reported cable length is different from the actual cable length, this could indicate a break in the cable. Accuracy can vary by up to 9 meters. The cable length will only be displayed when the adapter is connected to a network operating at 1000 Mbps. Polarity: Identifies the +/- properties of the send and receive twisted pair wires found in an Ethernet cable. If these properties are not correctly set up, the adapter will auto-correct and report the error. Local Receiver Status: Identifies whether the cable connector attached to the adapter is capable of handling traffic. If the local status test fails, check the connector for breaks or mis-wirings. Remote Receiver Status: The cable connector attached to the link partner passes or fails the set of operability tests. If the remote status test fails, check the connector for breaks or mis-wirings. Receive Error Count: Receive Errors occur when the adapter detects an unrecognizable transmission on the wire. Receive Error counts naturally increment when the adapter establishes communication with the network, connecting the cable to the adapter or restarting the computer, or when the adapter restarts after auto-negotiation. If the Idle Error count reaches approximately 65,000 within five minutes, there is a link quality issue. To resolve link quality issues, try re-connecting the cable or using a different cable. Idle Error Count: Idle Errors increment when the adapter receives an unrecognizable transmission on the wire. Unlike Receive Errors, Idle Errors are detected when the adapter is not actively receiving packets. Idle Error counts naturally occur when the adapter establishes communication with the network, connecting the cable to the adapter or restarting the computer, or when the adapter restarts after auto-negotiation. If the Idle Error count increases by 255 within one minute, there is a link quality issue. To resolve link quality issues, try re-connecting the cable or use a different cable. Signal quality: The adapter must be connected at 1000 Mbps for the signal quality test to run. Test cable connections and frequency response: The time domain reflectometry (TDR) test shows shorts, opens, and impedance mismatch in the cable. The insertion loss test shows whether there is excessive insertion loss. This is an offline test. WARNING: The offline test will disable the adapter's network connectivity. --------- Not all is lost. I repaired the installation and it works now. Last edited by oph; September 14th, 2007 at 02:25 PM. |
![]() |
| Bookmarks |
«
Previous Topic
|
Next Topic
»
| Topic Tools | |
|
|
All times are GMT +1. The time now is 05:49 PM.
[
RSS ]









