Auto-negotiation speed wrong on NIC?

It appears my new 10/100 NIC is chosing the wrong speed
since the 100Mbps LED lights up instead of the 10Mbps LED:

NIC <- 10/100switch -> NIC = ping failure
(10/100) (10)
^ ^

Using a crossover instead of the switch works okay:
NIC <-crossover-> NIC = ping okay
(10/100) (10)
^ ^

When I use a 10Mbps NIC with the same switch there is
no problem either:
NIC <- 10/100switch -> NIC = ping okay
(10) (10)
^ ^

I don't know if there's something wrong with the NIC or
switch, or if auto negotiation simply doesn't work with
this setup.

In article <(E-Mail Removed)>, "Victor Martin"
(E-Mail Removed) says...
> It appears my new 10/100 NIC is chosing the wrong speed
> since the 100Mbps LED lights up instead of the 10Mbps LED:
>
> NIC <- 10/100switch -> NIC = ping failure
> (10/100) (10)
> ^ ^
>
> Using a crossover instead of the switch works okay:
> NIC <-crossover-> NIC = ping okay
> (10/100) (10)
> ^ ^
>

Those speeds are what you'd expect - the NIC is selecting 100 when it's
talking to a 100Mb/s device (the switch) and 10 when talking to a 10Mb/s
device (the old NIC).

> When I use a 10Mbps NIC with the same switch there is
> no problem either:
> NIC <- 10/100switch -> NIC = ping okay
> (10) (10)
> ^ ^
>
> I don't know if there's something wrong with the NIC or
> switch, or if auto negotiation simply doesn't work with
> this setup.
>
Is the old NIC set for simplex or duplex operation?

Okay then, I figured it out, the 10/100 NIC correctly chooses 100Mbps
which fails in this case because the network cable is too long,
crooked, and sub-standard for that speed. When 10Mbps is forced the
connection is successful because the cable can sustain the network at
those slower speeds. Too bad I can't force 10Mbsp.

> Those speeds are what you'd expect [..]

In article <(E-Mail Removed)>, "Victor Martin"
(E-Mail Removed) says...
> Okay then, I figured it out, the 10/100 NIC correctly chooses 100Mbps
> which fails in this case because the network cable is too long,
> crooked, and sub-standard for that speed. When 10Mbps is forced the
> connection is successful because the cable can sustain the network at
> those slower speeds. Too bad I can't force 10Mbsp.
>
Why not?

>> Okay then, I figured it out, the 10/100 NIC correctly chooses 100Mbps
>> which fails in this case because the network cable is too long,
>> crooked, and sub-standard for that speed. When 10Mbps is forced the
>> connection is successful because the cable can sustain the network at
>> those slower speeds.

A 10Mbps connect is possible here only with a 10Mbps NIC.

>>Too bad I can't force 10Mbsp.
>>
> Why not?

The new NIC has auto-negotiation so if the switch is also
auto-negotiation they will apparently default to 100Mbps even though the
line will only function properly at 10Mbps, and there's no manual switch
to select 10 or 100 Mbps.

Victor Martin wrote:
>>> Okay then, I figured it out, the 10/100 NIC correctly chooses
>>> 100Mbps which fails in this case because the network cable is too
>>> long, crooked, and sub-standard for that speed. When 10Mbps is
>>> forced the connection is successful because the cable can sustain
>>> the network at those slower speeds.
>
> A 10Mbps connect is possible here only with a 10Mbps NIC.
>
>>> Too bad I can't force 10Mbsp.
>>>
>> Why not?
>
> The new NIC has auto-negotiation so if the switch is also
> auto-negotiation they will apparently default to 100Mbps even though
> the line will only function properly at 10Mbps, and there's no manual
> switch to select 10 or 100 Mbps.

Are you sure?
I've never seen a NIC that won't let you select the speed manually.
--
Alex

"We are now up against live, hostile targets"

"So, if Little Red Riding Hood should show up with a bazooka and a bad
attitude, I expect you to chin the bitch! "

www.drzoidberg.co.uk
www.upce.org.uk

In article <(E-Mail Removed)>, "Victor Martin"
(E-Mail Removed) says...
> >> Okay then, I figured it out, the 10/100 NIC correctly chooses 100Mbps
> >> which fails in this case because the network cable is too long,
> >> crooked, and sub-standard for that speed. When 10Mbps is forced the
> >> connection is successful because the cable can sustain the network at
> >> those slower speeds.
>
> A 10Mbps connect is possible here only with a 10Mbps NIC.
>
> >>Too bad I can't force 10Mbsp.
> >>
> > Why not?
>
> The new NIC has auto-negotiation so if the switch is also
> auto-negotiation they will apparently default to 100Mbps even though the
> line will only function properly at 10Mbps, and there's no manual switch
> to select 10 or 100 Mbps.
>
I think you'll find any ethernet NIC has duplex and speed settings
selectable in the driver (unless it's a simplex 10Mb/s card of
course). Maybe you need a different driver.

I didn't know there were software selectable speed options in the
driver, after reading your replies I looked around and found them,
thanks.