A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Networking and the Internet with Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Broadcom cards continually re-negotiating, showing short?



 
 
Thread Tools Display Modes
  #1  
Old July 25th 09, 05:50 PM posted to microsoft.public.windowsxp.network_web
Mike
external usenet poster
 
Posts: 6
Default Broadcom cards continually re-negotiating, showing short?

I have a network with 13 HP DC5750 desktops. Almost all of them are
exhibiting a strange behaviour. They drop the network connection for a
few seconds, and then reconnect. In the event log, I see this event
repeatedly:

'Broadcom NetXtreme Gigabit Ethernet: Network controller configured
for 100Mb full-duplex link'

On some machines, it does not happen too often, once every week or so.
But on some, it is happening once an hour, and even once every few
minutes sometimes. Also, when I run the Broadcom Diags, and run cable
test, it shows that 2 of the 4 pairs have a short. At first, I
thought, AHA!, that's the problem. But now it seems suspicious,
because all my computers are showing 2 shorted pairs. While it is
possible, I doubt that they are all shorted.

Has anyone else seen this happen? I'm going to try new cables to make
sure, but beyond that, this seems pretty weird to me. Maybe it's the
cheapo Linksys switch they are plugged into? Or maybe there are
Gremlins chewing on my cables at night? Many of the events are
registering after midnight....
Ads
  #2  
Old July 27th 09, 03:36 PM posted to microsoft.public.windowsxp.network_web
smlunatick
external usenet poster
 
Posts: 4,866
Default Broadcom cards continually re-negotiating, showing short?

On Jul 25, 5:50*pm, Mike wrote:
I have a network with 13 HP DC5750 desktops. Almost all of them are
exhibiting a strange behaviour. They drop the network connection for a
few seconds, and then reconnect. In the event log, I see this event
repeatedly:

'Broadcom NetXtreme Gigabit Ethernet: Network controller configured
for 100Mb full-duplex link'

On some machines, it does not happen too often, once every week or so.
But on some, it is happening once an hour, and even once every few
minutes sometimes. Also, when I run the Broadcom Diags, and run cable
test, it shows that 2 of the 4 pairs have a short. At first, I
thought, AHA!, that's the problem. But now it seems suspicious,
because all my computers are showing 2 shorted pairs. While it is
possible, I doubt that they are all shorted.

Has anyone else seen this happen? I'm going to try new cables to make
sure, but beyond that, this seems pretty weird to me. Maybe it's the
cheapo Linksys switch they are plugged into? Or maybe there are
Gremlins chewing on my cables at night? Many of the events are
registering after midnight....


Have you considered checking for updated drivers?

Also, are these cables passed through walls / ceilings ?
  #3  
Old July 27th 09, 03:36 PM posted to microsoft.public.windowsxp.network_web
smlunatick
external usenet poster
 
Posts: 4,866
Default Broadcom cards continually re-negotiating, showing short?

On Jul 25, 5:50*pm, Mike wrote:
I have a network with 13 HP DC5750 desktops. Almost all of them are
exhibiting a strange behaviour. They drop the network connection for a
few seconds, and then reconnect. In the event log, I see this event
repeatedly:

'Broadcom NetXtreme Gigabit Ethernet: Network controller configured
for 100Mb full-duplex link'

On some machines, it does not happen too often, once every week or so.
But on some, it is happening once an hour, and even once every few
minutes sometimes. Also, when I run the Broadcom Diags, and run cable
test, it shows that 2 of the 4 pairs have a short. At first, I
thought, AHA!, that's the problem. But now it seems suspicious,
because all my computers are showing 2 shorted pairs. While it is
possible, I doubt that they are all shorted.

Has anyone else seen this happen? I'm going to try new cables to make
sure, but beyond that, this seems pretty weird to me. Maybe it's the
cheapo Linksys switch they are plugged into? Or maybe there are
Gremlins chewing on my cables at night? Many of the events are
registering after midnight....


Have you considered checking for updated drivers?

Also, are these cables passed through walls / ceilings ?
  #4  
Old July 27th 09, 10:20 PM posted to microsoft.public.windowsxp.network_web
Mike
external usenet poster
 
Posts: 6
Default Broadcom cards continually re-negotiating, showing short?

On Jul 27, 9:36*am, smlunatick wrote:
On Jul 25, 5:50*pm, Mike wrote:





I have a network with 13 HP DC5750 desktops. Almost all of them are
exhibiting a strange behaviour. They drop the network connection for a
few seconds, and then reconnect. In the event log, I see this event
repeatedly:


'Broadcom NetXtreme Gigabit Ethernet: Network controller configured
for 100Mb full-duplex link'


On some machines, it does not happen too often, once every week or so.
But on some, it is happening once an hour, and even once every few
minutes sometimes. Also, when I run the Broadcom Diags, and run cable
test, it shows that 2 of the 4 pairs have a short. At first, I
thought, AHA!, that's the problem. But now it seems suspicious,
because all my computers are showing 2 shorted pairs. While it is
possible, I doubt that they are all shorted.


Has anyone else seen this happen? I'm going to try new cables to make
sure, but beyond that, this seems pretty weird to me. Maybe it's the
cheapo Linksys switch they are plugged into? Or maybe there are
Gremlins chewing on my cables at night? Many of the events are
registering after midnight....


Have you considered checking for updated drivers?

Also, are these cables passed through walls / ceilings ?- Hide quoted text -

- Show quoted text -


Yep, the NIC drivers (as well as bios and all other drivers on the
systems) are up to date.

I went on-site on Sunday to work on this problem, and I found that the
systems going into Standby every night seems to be related. I disabled
Standby on all the systems, rebooted them, and now NONE of them are
having any issue. I'm hoping there is a way to still use Standby but
not cause NIC issues.
  #5  
Old July 27th 09, 10:20 PM posted to microsoft.public.windowsxp.network_web
Mike
external usenet poster
 
Posts: 6
Default Broadcom cards continually re-negotiating, showing short?

On Jul 27, 9:36*am, smlunatick wrote:
On Jul 25, 5:50*pm, Mike wrote:





I have a network with 13 HP DC5750 desktops. Almost all of them are
exhibiting a strange behaviour. They drop the network connection for a
few seconds, and then reconnect. In the event log, I see this event
repeatedly:


'Broadcom NetXtreme Gigabit Ethernet: Network controller configured
for 100Mb full-duplex link'


On some machines, it does not happen too often, once every week or so.
But on some, it is happening once an hour, and even once every few
minutes sometimes. Also, when I run the Broadcom Diags, and run cable
test, it shows that 2 of the 4 pairs have a short. At first, I
thought, AHA!, that's the problem. But now it seems suspicious,
because all my computers are showing 2 shorted pairs. While it is
possible, I doubt that they are all shorted.


Has anyone else seen this happen? I'm going to try new cables to make
sure, but beyond that, this seems pretty weird to me. Maybe it's the
cheapo Linksys switch they are plugged into? Or maybe there are
Gremlins chewing on my cables at night? Many of the events are
registering after midnight....


Have you considered checking for updated drivers?

Also, are these cables passed through walls / ceilings ?- Hide quoted text -

- Show quoted text -


Yep, the NIC drivers (as well as bios and all other drivers on the
systems) are up to date.

I went on-site on Sunday to work on this problem, and I found that the
systems going into Standby every night seems to be related. I disabled
Standby on all the systems, rebooted them, and now NONE of them are
having any issue. I'm hoping there is a way to still use Standby but
not cause NIC issues.
  #6  
Old July 28th 09, 02:31 PM posted to microsoft.public.windowsxp.network_web
Anteaus
external usenet poster
 
Posts: 1,330
Default Broadcom cards continually re-negotiating, showing short?


"Mike" wrote:

I have a network with 13 HP DC5750 desktops. Almost all of them are
exhibiting a strange behaviour. They drop the network connection for a
few seconds, and then reconnect. In the event log, I see this event
repeatedly:

Has anyone else seen this happen?


Yes. On every computer with these LAN chips. Plus a few other makes.

http://mylogon.net/support/psave


  #7  
Old July 28th 09, 02:31 PM posted to microsoft.public.windowsxp.network_web
Anteaus
external usenet poster
 
Posts: 1,330
Default Broadcom cards continually re-negotiating, showing short?


"Mike" wrote:

I have a network with 13 HP DC5750 desktops. Almost all of them are
exhibiting a strange behaviour. They drop the network connection for a
few seconds, and then reconnect. In the event log, I see this event
repeatedly:

Has anyone else seen this happen?


Yes. On every computer with these LAN chips. Plus a few other makes.

http://mylogon.net/support/psave


  #8  
Old July 28th 09, 02:54 PM posted to microsoft.public.windowsxp.network_web
Anteaus
external usenet poster
 
Posts: 1,330
Default Broadcom cards continually re-negotiating, showing short?

"Mike" wrote:

Also, when I run the Broadcom Diags, and run cable
test, it shows that 2 of the 4 pairs have a short. At first, I
thought, AHA!, that's the problem. But now it seems suspicious,
because all my computers are showing 2 shorted pairs. While it is
possible, I doubt that they are all shorted.


10/100 Ethernet uses the red and green pairs only, and a signal transformer
is connected across each pair. Thus a healthy connection shows:

No connection (infinite resistance) between any two pairs.
Low resistance across the two wires of the red or green pair.
No connection between the wires of blue or brown pairs.

On 1000MHz cables, all four pairs are used.

A common mistake in Ethernet wiring is to use a nonstandard wiring-order
such that transmit and receive signals are split across pairs. When you
understand that the twisted pairs are there to segregate the signals, it will
be obvious that this will give rise to all sorts of intermittent troubles
through crosstalk. Thus, unlike most other electrical installs, you MUST
follow the official wiring scheme or it won't work.

Just thought I'd mention this as it's another frequent cause of LAN troubles.

Looking at the side of the plug without the clip:
White/Orange
Orange/White
White/Green
Blue/White
White/Blue
Green/White
White/Brown
Brown/While

-and yeah this may look totally wacko but it's right!

  #9  
Old July 28th 09, 02:54 PM posted to microsoft.public.windowsxp.network_web
Anteaus
external usenet poster
 
Posts: 1,330
Default Broadcom cards continually re-negotiating, showing short?

"Mike" wrote:

Also, when I run the Broadcom Diags, and run cable
test, it shows that 2 of the 4 pairs have a short. At first, I
thought, AHA!, that's the problem. But now it seems suspicious,
because all my computers are showing 2 shorted pairs. While it is
possible, I doubt that they are all shorted.


10/100 Ethernet uses the red and green pairs only, and a signal transformer
is connected across each pair. Thus a healthy connection shows:

No connection (infinite resistance) between any two pairs.
Low resistance across the two wires of the red or green pair.
No connection between the wires of blue or brown pairs.

On 1000MHz cables, all four pairs are used.

A common mistake in Ethernet wiring is to use a nonstandard wiring-order
such that transmit and receive signals are split across pairs. When you
understand that the twisted pairs are there to segregate the signals, it will
be obvious that this will give rise to all sorts of intermittent troubles
through crosstalk. Thus, unlike most other electrical installs, you MUST
follow the official wiring scheme or it won't work.

Just thought I'd mention this as it's another frequent cause of LAN troubles.

Looking at the side of the plug without the clip:
White/Orange
Orange/White
White/Green
Blue/White
White/Blue
Green/White
White/Brown
Brown/While

-and yeah this may look totally wacko but it's right!

  #10  
Old July 30th 09, 06:40 PM posted to microsoft.public.windowsxp.network_web
Mike
external usenet poster
 
Posts: 6
Default Broadcom cards continually re-negotiating, showing short?

On Jul 28, 8:54*am, Anteaus wrote:
"Mike" wrote:

*Also, when I run the Broadcom Diags, and run cable

test, it shows that 2 of the 4 pairs have a short. At first, I
thought, AHA!, that's the problem. But now it seems suspicious,
because all my computers are showing 2 shorted pairs. While it is
possible, I doubt that they are all shorted.


10/100 Ethernet uses the red and green pairs only, and a signal transformer
is connected across each pair. Thus a healthy connection shows:

No connection (infinite resistance) between any two pairs.
Low resistance across the two wires of the red or green pair.
No connection between the wires of blue or brown pairs.

On 1000MHz cables, all four pairs are used.

A common mistake in Ethernet wiring is to use a nonstandard wiring-order
such that transmit and receive signals are split across pairs. When you
understand that the twisted pairs are there to segregate the signals, it will
be obvious that *this will give rise to all sorts of intermittent troubles
through crosstalk. Thus, unlike most other electrical installs, you MUST
follow the official wiring scheme or it won't work. *

Just thought I'd mention this as it's another frequent cause of LAN troubles.

Looking at the side of the plug without the clip:
White/Orange
Orange/White
White/Green
Blue/White
White/Blue
Green/White
White/Brown
Brown/While

-and yeah this may look totally wacko but it's right!


Oh yes, trust me the cable pairs are in the correct color order. I
made that mistake a long time ago and had to re-do a lot of cables so
I always check that. After that happened, I've been known to recite
the color order in my sleep!
  #11  
Old July 30th 09, 06:40 PM posted to microsoft.public.windowsxp.network_web
Mike
external usenet poster
 
Posts: 6
Default Broadcom cards continually re-negotiating, showing short?

On Jul 28, 8:54*am, Anteaus wrote:
"Mike" wrote:

*Also, when I run the Broadcom Diags, and run cable

test, it shows that 2 of the 4 pairs have a short. At first, I
thought, AHA!, that's the problem. But now it seems suspicious,
because all my computers are showing 2 shorted pairs. While it is
possible, I doubt that they are all shorted.


10/100 Ethernet uses the red and green pairs only, and a signal transformer
is connected across each pair. Thus a healthy connection shows:

No connection (infinite resistance) between any two pairs.
Low resistance across the two wires of the red or green pair.
No connection between the wires of blue or brown pairs.

On 1000MHz cables, all four pairs are used.

A common mistake in Ethernet wiring is to use a nonstandard wiring-order
such that transmit and receive signals are split across pairs. When you
understand that the twisted pairs are there to segregate the signals, it will
be obvious that *this will give rise to all sorts of intermittent troubles
through crosstalk. Thus, unlike most other electrical installs, you MUST
follow the official wiring scheme or it won't work. *

Just thought I'd mention this as it's another frequent cause of LAN troubles.

Looking at the side of the plug without the clip:
White/Orange
Orange/White
White/Green
Blue/White
White/Blue
Green/White
White/Brown
Brown/While

-and yeah this may look totally wacko but it's right!


Oh yes, trust me the cable pairs are in the correct color order. I
made that mistake a long time ago and had to re-do a lot of cables so
I always check that. After that happened, I've been known to recite
the color order in my sleep!
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 01:04 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.