10-08-2006 04:09 PM - last edited on 11-03-2013 08:50 PM by Lisa198503
We have a mix of HP dx2000 and dc7100 machines with Broadcom NetXtreme Gigabit Ethernet cards in them.
We run a 2003AD domain and use GPO for software installation. however, we have found that if the Broadcoms are set to Auto on duplex/speed then the GPO will be applied but the software does not aftually install.
However, if we hard set workstation to 100Full and then hard set the server NIC (another broadcom Gigabit on a ML350) the GPo applies and software rolls out. However, the data transfer rate then becomes very slow across the network.
So then I realised that the switch ports need to be hard set too. However, i'm thinking that maybe there is an easier way to do this other than just hard setting evey available NIC/port to 100Full and going from there-because I'm worried that laptop users who access web from hotels will then have problems when accessing things as they are hard set and the network they are connecting to is Auto.
Any non Broadcom cards are better at handling the Auto option and there are no GPO application problems.
P.S. This thread has been moved from Archived Desktops and Workstations Boards-Windows based to Business PCs - Compaq, Elite, Pro. -HP Forum Moderator
10-09-2006 12:50 PM
A bit of boiler-plate about Autoneg: (link == cable)
How 100Base-T Autoneg is supposed to work:
When both sides of the link are set to autoneg, they will "negotiate"
the duplex setting and select full-duplex if both sides can do
If one side is hardcoded and not using autoneg, the autoneg process
will "fail" and the side trying to autoneg is required by spec to use
If one side is using half-duplex, and the other is using full-duplex,
sorrow and woe is the usual result.
So, the following table shows what will happen given various settings
on each side:
Auto Half Full
Auto Happiness Lucky Sorrow
Half Lucky Happiness Sorrow
Full Sorrow Sorrow Happiness
Happiness means that there is a good shot of everything going well.
Lucky means that things will likely go well, but not because you did
anything correctly :) Sorrow means that there _will_ be a duplex
When there is a duplex mismatch, on the side running half-duplex you
will see various errors and probably a number of _LATE_ collisions
("normal" collisions don't count here). On the side running
full-duplex you will see things like FCS errors. Note that those
errors are not necessarily conclusive, they are simply indicators.
Further, it is important to keep in mind that a "clean" ping (or the
like - eg "linkloop" or default netperf TCP_RR) test result is
inconclusive here - a duplex mismatch causes lost traffic _only_ when
both sides of the link try to speak at the same time. A typical ping
test, being synchronous, one at a time request/response, never tries
to have both sides talking at the same time.
Finally, when/if you migrate to 1000Base-T, everything has to be set
to auto-neg anyway.
10-09-2006 02:19 PM
Maybe a driver update might help, maybe not. I will most likely have to write a script to hardset machines on shutdown and then hard set all ports on the switch and finally hardset the nics on the servers.
Or maybe go the gigabit option-though I think that one of our older switches can't handle gigabit. Luckily we have just moved to new offices and have cat 6 everywhere.