a network cable is unplugged

[Max]

a network cable is unplugged

I just booted up two of my computers and both of them are giving me this
over and over. It's been happening for some time, but not this bad! Bad
router you think?

And switches between:
Local Area Connection is now connected Speed 100.Mps and
Local Area Connection is now connected Speed 10.Mps

 

[Skeleton Man]

a network cable is unplugged

I just booted up two of my computers and both of them are giving me this
over and over. It's been happening for some time, but not this bad! Bad
router you think?

And switches between:
Local Area Connection is now connected Speed 100.Mps and
Local Area Connection is now connected Speed 10.Mps

Try different cables, and check that:

a) They're straight not crossover (ie. the order of the wire colors at both ends
is the same)
b) You're not plugged into an uplink port (used for connecting switches, etc to
one another)

Regards,
Chris

 

[JANA]

First try to check to see if the router is functioning properly. It may have
failed, or require to be reset. This can be a task, if all the entries have
to be redone. I have had routers having to be reset, or fail.

It is rare that Ethernet cables will go defective, unless they are in an
area where they can be disturbed, or users are un-plugging and re-plugging
them all the time, or people are able to walk on the cables.

--

JANA
_____


a network cable is unplugged

I just booted up two of my computers and both of them are giving me this
over and over. It's been happening for some time, but not this bad! Bad
router you think?

And switches between:
Local Area Connection is now connected Speed 100.Mps and
Local Area Connection is now connected Speed 10.Mps

 

[kony]

a network cable is unplugged

I just booted up two of my computers and both of them are giving me this
over and over. It's been happening for some time, but not this bad! Bad
router you think?

And switches between:
Local Area Connection is now connected Speed 100.Mps and
Local Area Connection is now connected Speed 10.Mps

Check the cables, their plugs, the socket, etc. Rarely I
find systems that have rear case slots off-spec a little
such that the RJ45 connector's locking tab doesn't seat
fully due to being depressed a little by the slot
cross-member. In such a case an adjustment of the NIC,
motherboard on the standoffs, or a different NIC might help.

Check the switch Link and 10/100 connection LEDs. Do they
change? Do they change if you wiggle the cable slowly?

Check for dirty contacts, if you had a spare switch it
wouldnt' hurt to try it. Some of the passive switches have
capacitors that get really hot and might not last very
long... how long can only be seen in retruspect, IF/when
someone has theirs fail.

You haven't menitoned what you HAVE done so far to try and
troubleshoot this though, it would be good to know so we
don't redundantly cover basics that you've already tried.

Some NICs have software that can give you cable
length/signal-strength/etc feedback. 3Com, Intel (can't
remember) and some Via chipset NICs come to mind as those
that do... and probably others.

 

[MF]

Do a search on google and have a look at some of the results. You will be
disheartened by the number of things that can cause this.

I had two recent same errors. Cable was good, switch ports were good. One,
I fixed by reversing the ends of the of the cable (Win 2000 Pro). The other
(Win 2003 Server) wouldn't fix till I plopped the NIC into another PCI slot.
This was an Asus mobo and a Farallon NIC that emulated a Realtek. 10 100
autosensing, very straightforward basic NIC

Meanwhile, you should provide info to the group on your OS(s), NICs,
motherboards and what was done prior to the errors.

Commonalities, when I was researching this, seemed to be: XP after certain
updates (sometimes fixed by later updates or Service Packs) Intel embedded
adapters (forget the model number) and Realtek RTL 1389 or 1839 (or
something like that) NICs.

It may be true as one person said that cables rarely go bad. But when they
go, it can be a complete surprise with absolutely no perceptible cause, so
don't fail to check em out. I once wasted two hours checking every possible
DNS error in a Win 2K network - when the cause was a cable that went bad
overnight - a cable that - we thought - couldn't _possibly_ have gone bad.
hehheheh, it did .

Mike