Originally Posted By: Volvohead
A single bend exceeding spec, or laying a run in the wrong location (too near a magnetic field or parallel to a mains line), or a sloppy termination is enough to blow it for the entire LAN. All the TCP tweaking in the world won't fix a sloppy punchdown.
If you're tweaking TCP to fix the cause of a network speed issue and you haven't checked for frame errors, collisions and crc errors, you're wasting your time. (My experience is that many network speed issues are caused by duplex mismatches, which usually show as ridiculously high numbers of collisions in relation to the number of packets transmitted).
On the other hand I still haven't found anyone who can tell me how, with Windows XP, to find out how many collisions the network card has seen. My solution is to boot the PC with Knoppix and use a real OS to find out.
BTW I run gig on cat5. No "e".