Once upon a time autonegotiation wasn't standardized. Then it was.
But we still have non-standard gear in service here and there so it
still bites people once in a while and it gets a bad rap. 3COM gear has
been the biggest thorn in my side from this problem - they put out
10/100 managed swit
>
> "Ken D'Ambrosio" <[EMAIL PROTECTED]> writes:
>
>> is the fact that autonegotiation is an imperfect science.
>
> In what way are the autonegotiation specs. deficient? Just curious.
While I've never read the RFC, to the best of my knowledge, there's no
problem with the specs, themselves. Once
Hi, Greg -
My, this brings back memories!
Back when our shop still used Microsoft software (but Netscape, never
OutBack!) we saw this same problem. What a pain - even on a Windows
system you couldn't read the attachments!
There were solutions (although not from Microsoft). Here's a URL for
ano
The rapid flashing of the port the 100Mbit link is connected to is
quite possibly the port (in 10 Mbit mode) interpreting 100 Mbit link
pulses as data, which is not an uncommon occurrence. Use the excuse
to get yourself a WRT54G. ;-) (Yes, it runs Linux.)
--Drew
On Wed, 08 Dec 2004 11:36:46 -
Thanks for all the responses. It seems like the router is having a 100Mbs
problem, since a few of you have also experienced that kind of problem.
Although I do have some suggestions to follow up on just to make sure.
I guess I'll just move my 10Mbs hub directly in front of the router and put
e
Dan,
Thanks for your repsonse.
In one case it was a bad patch cable. The cable worked at 10Mbps but not
100Mbps. I didn't try to determine why. Just replaced it.
I've tried three different cables directly connecting computer #2 and the
router. No difference.
In some cheap 10/100 switches, the en
Ken,
One thing to contemplate -- though if it had been working
before, it's not terribly likely to be the problem -- is the fact that
autonegotiation is an imperfect science.
This router has been working for a year and half with computer #1 (10Mbs) and
#2 (100Mbs) connected to it. The 100Mbs sw
Brian,
Thanks for your response.
Every 10/100 device I've seen in the last 10 years has used 1 chip to handle
the 10/100 PHY. This means that it would be (IMO) HIGHLY unlikely that only
the 100Mbs portion could/would fail, I would expect all or nothing.
One thing I did notice is that when a 100Mbs
Travis,
Thanks for your response.
It could be a duplex mismatch but I doubt it.
I have had this happen to myself personally, where the 100mb part didn't
work and the 10mb part did.
Okay, so it is a possibility.
I assume by router you mean broadband router, not a "real" router.
Yes, it is an Action
On Tue, 2004-12-07 at 11:24, Cole Tuininga wrote:
...
> DSL -- firewall/NAT -- switch -- wired ethernet boxes
> |
> WAP -- wireless devices
>
> (hope the ASCII "art" comes through ok)
Yep.
This represents my home setup pretty much -- just replace
If the crystal on the router that feeds the 10/100 PHYs drifts out of
spec, 100 would stop working, 10 would probably be more forgiving. Is
this likely? No, but it is possible. Just my $0.01999
--DTVZ
___
gnhlug-discuss mailing list
[EMAIL PROT
[EMAIL PROTECTED] writes:
> problem with the specs, themselves. Once again, it's a case of "the Devil is
> in the details." I think it's the implementation -- especially cross-vendor
> issues -- that's the biggie.
FYI: autonegotiation is specified by IEEE specs, not RFCs.
It is also my per
"Ken D'Ambrosio" <[EMAIL PROTECTED]> writes:
> is the fact that autonegotiation is an imperfect science.
In what way are the autonegotiation specs. deficient? Just curious.
Thanks,
--kevin
--
GnuPG ID: B280F24E And the madness of the crowd
I'm having a network problem that appears to be that the 10/100Mbs
ports on my router are no longer working at 100Mbs, but are
working at 10Mbs. Is it possible that just the 100Mbs part could
fail?
I've seen this problem a few times.
In one case it was a bad patch cable. The cable worked at 10Mbps
Hey, Larry! One thing to contemplate -- though if it had been working
before, it's not terribly likely to be the problem -- is the fact that
autonegotiation is an imperfect science. As an example, at Cisco, we
always had to peg our server connections at 100MBit on the not-so off
chance that t
Every 10/100 device I've seen in the last 10 years has used 1 chip to handle
the 10/100 PHY. This means that it would be (IMO) HIGHLY unlikely that only
the 100Mbs portion could/would fail, I would expect all or nothing.
Based on past experience (is there such a thing as *future* experience?) I
w
It could be a duplex mismatch but I doubt it.
I have had this happen to myself personally, where the 100mb part didn't
work and the 10mb part did.
I assume by router you mean broadband router, not a "real" router.
Most consumer level 10/100 "switches" or "routers" are switching hubs.
That is the
Solution found, thank you. the following is a summery of the problem
and the solution
Situation
-
I found(got, received) a Macintosh dual g3 workstation that was not
powering on (ram was forced in to the slot the wrong way)
once i fixed it
I'm having a network problem that appears to be that the 10/100Mbs ports on my
router are no longer working at 100Mbs, but are working at 10Mbs. Is it
possible that just the 100Mbs part could fail?
Here's my scenario if anyone is interested. Connected to the router are the
following:
Computer
19 matches
Mail list logo
