Procurve Errors, Can't force N IC speed on PC's.
Posted on 2007-07-26
We purchased a Procurve 2900 about half a year ago. Recently I started checking it for errors as we experience delays at times writing or reading data from the file server ( This office about 20 users, 40 systems, W2K AD Domain, 98% XP Pro clients ). Under status I discovered half a dozen systems were throwing errors stating either 'High collision or drop rate on port ...' or 'Excessive broadcasts detected on port ...'. The High collision errors are far more common.
I started troubleshooting thinking these might be the cause of the intermittent delays. My first thought was to force both ends of the connection to Gig instead of leaving them on 'Auto' however I found that NONE of the NIC's involved would allow you to force them to a speed above 100 megs. Also discovered that when I forced a client to 100 or 10 Megs that client would lose connectivity with the LAN. Running IPCONFIG would return 'media disconnected'. Rebooting did not resolve it, only going back to 'Auto' would get the system to admit it ( all of our systems ) have a static IP and then allow connectivity to the LAN.
The other thoughts on tracking the problem down include trying other ports on the switch, trying a 3rd party NIC in the PC's involved, and trying other patch cables.
I'm a little puzzled about not being able to force a speed on the connection. Many years ago that was how we ensured the auto settings were not screwing up.
Might anyone have a work around, or other ideas on identifying the cause of these few systems continuing errors?