A–Troubleshooting
Possible Problems and Solutions
277
83840-546-00 N
Problem:
A system containing an 802.3ad team causes a Netlogon service
failure in the system event log and prevents it from communicating
with the domain controller during boot up.
Solution:
Microsoft Knowledge Base Article 326152
(
http://support.microsoft.com/kb/326152/en-us
) indicates that Gigabit
Ethernet adapters may experience problems with connectivity to a
domain controller due to link fluctuation while the driver initializes and
negotiates the link with the network infrastructure. The link negotiation
is further affected when the Gigabit adapters are participating in an
802.3ad team due to the additional negotiation with a switch required
for this team type. As suggested in the Knowledge Base Article
326152, disabling media sense as described in a separate Knowledge
Base Article 938449 (
http://support.microsoft.com/kb/938449
shown to be a valid workaround when this problem occurs.
Problem:
A Generic Trunking (GEC/FEC) 802.3ad-Draft Static type of team may
lose some network connectivity if the driver to a team member is
disabled.
Solution:
If a team member supports underlying management software (ASF or
UMP), the link may be maintained on the switch for the adapter
despite its driver being disabled. This situation may result in the
switch continuing to pass traffic to the attached port rather than route
the traffic to an active team member port. Disconnecting the disabled
adapter from the switch will allow traffic to resume to the other active
team members.
Problem:
Large Send Offload (LSO) and Checksum Offload are not working on
my team.
Solution:
If one of the adapters on a team does not support LSO, LSO does not
function for the team. Remove the adapter that does not support LSO
from the team, or replace it with one that does. The same applies to
Checksum Offload.
Problem:
The advanced properties of a team do not change after changing the
advanced properties of an adapter that is a member of the team.
Solution:
If an adapter is included as a member of a team and you change any
advanced property, then you must rebuild the team to ensure that the
team’s advanced properties are properly set.
Problem:
QLASP NIC teaming driver does not install on Windows Server 2016.
Solution:
QLASP NIC teaming driver is not supported on Windows Server 2016
and will not install. Use the in-OS Windows NIC teaming load
balancing and failover (LBFO) service instead. Microsoft recommends
using their in-OS LBFO service (instead of vendor-specific NIC
teaming utilities) on Windows Server 2012/2012 R2/2016.
