Jaa

Active Directory: In Windows 2008 R2, the dcdiag.exe fails with the error 0x621

  • Artikkeli

 

In Windows 2008 R2, the dcdiag.exe tool adds a new feature which checks if the
network interface is a physical network card. Dcdiag does this by querying the flag
ConnectorPresent. This flag seems to be not set on the HP teaming network
interface. Therefore the dcdiag determined that no network was found and returned
the error 0x621. The error code 0x621 translates to "Both IPV4 and IPV6 channels
are disabled on all adapter cards of the local server. Hence no connectivity to the
server".

This seems to be a compatibility issue between the new dcdiag tool in Windows 2008
R2 and the teaming network interface, because the ConnectorPresent flag seems to
be set to 0 on the teaming network interface.

Based on RFC 1573, the teaming network interface should set it to true (1).
ifConnectorPresent OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object has the value 'true(1)' if the interface sublayer has a physical
connector and the value 'false(2)' otherwise." ::= { ifXEntry 17 }

Read more: <https://www.faqs.org/rfcs/rfc1573.html>

Based on current situation, you have the following choices:
1). Ignore the error message as it's only an issue when running dcdiag from the
Windows 2008 R2. It doesn't affect the DC's normal functionality. For dcdiag, it
can be run from other machines remotely.
2). Try to update the teaming network interface driver to see if that makes any
difference. If not, consult HW support to see if they make the driver to set the
flag to true on the teaming interface.

Comments

  • Anonymous
    January 01, 2003
    worst case you can remov eteaming for testing and rebuild it later again

  • Anonymous
    July 11, 2010
    It doesn't seem to be much of a problem. There are other options to explore in testing connectivity and replication till the issue is resolved like manually doing the checks, there are areas in the OS that are pointers that. Nice.