What can cause auto-negotiation to fail on network?

6

1

Imagine you have both computer with a NIC that do gigabit with a router that do gigabit. What can cause auto-negotiation to fail on network ? (with proof if possible)

Rushino

Posted 2011-10-14T11:52:54.213

Reputation: 574

Are you sure both ends actually have autoneg enabled? Sometimes one is statically configured for gigabit, which disables autonegotiation. – user1686 – 2011-10-14T12:58:49.280

I am sure i have verified.. one are set to Auto detect.. the other one to auto nego. – Rushino – 2011-10-14T12:59:39.217

Answers

5

There are two possible reasons:

  1. Bad or incorrect (not CAT5e) cables or connectors, or cables that are either too short or too long according to the standard.

  2. Incompatible hardware. Here's what Wikipedia says:

    The first version of the autonegotiation specification, IEEE 802.3u, was open to different interpretations. Although most manufacturers implemented this standard in one way, some others, including network giant Cisco, implemented it in a different way. Autonegotiation between devices that implemented it differently failed.

    I don't believe there are any new devices that still use 802.3u, however crappy incompatible hardware is still common.

    802.3ab specified that copper gigabit Ethernet requires autonegotiation, if you can disable auto-negotiation and "force" gigabit connection in the settings, it most probably means that your hardware still uses the older, no-so-compatible standard.

    Clarification: Some network cards allow to set speed to 1Gbps. However, this does not disable auto-negotiation. According to IEEE Interpretation:

    Although operating speed is allowed to be manually selected by disabling Auto-Negotiation in Control Register 0, selecting 1000BASE-T mode of operation still requires that Auto-Negotiation be used. This can be accomplished by continuing to use Auto-Negotiation while limiting the advertising to 1000BASE-T capabilities.

    Essentially, network cards says "I will auto-negotiate, but I can do only 1Gbps, nothing else." This is not the same as just disabling auto-negotiation and setting speed & duplex manually.

haimg

Posted 2011-10-14T11:52:54.213

Reputation: 19 503

+1 for mentioning cable type/length. That resolved my issue. Thanks! – Mike B – 2015-09-19T20:30:56.707

Nice answer, but i can't agree with the last sentence. I have a recent motherboard and i can still set the speed if i would.. that doesnt mean it use the older standard since its a very recent motherboard with a gigabit port. – Rushino – 2011-10-14T15:08:17.353

1I added clarification about my claim about auto-negotiation. Unfortunately, NIC config GUIs are often too vague about what they actually do/change. – haimg – 2011-10-14T15:36:36.650

You actually saying that setting the speed to 1 Gbps actually doesn't disable Auto-negotiation ? – Rushino – 2011-10-14T16:09:24.907

1Yes. Auto-neg is mandatory for 1Gbps per 802.3ab. – haimg – 2011-10-14T16:15:46.180

1Alright, alway nice to know. Ive heard that changing the speed can actually disable auto-neg. But i might be wrong. Anyway i guess we shouldnt be changing thoses settings. I will check my network tonight and post an update. Thanks for your help. – Rushino – 2011-10-14T16:36:27.743

5

Dodgy cables: I've just replaced a 3m patch lead to a laptop docking station that was causing problems - the gigabit connection was either working, very slow or connecting (and not working) at 100 or 10Mbit

Linker3000

Posted 2011-10-14T11:52:54.213

Reputation: 25 670

Asked: 2011-10-14T11:52:54.213

Viewed: 18 684 times

Active: 2011-10-14T15:35:21.050