Microsoft KB Archive/931067

= Error message on a computer that uses Gigabit Ethernet devices and does not apply Group Policy or PolicyMaker CSEs: &quot;The specified domain either does not exist or exist or could not be contacted&quot; =

Article ID: 931067

Article Last Modified on 2/7/2007

-

APPLIES TO


 * PolicyMaker Standard Edition 2.0
 * PolicyMaker Standard Edition 1.0

-



SYMPTOMS
On a computer that uses Gigabit Ethernet devices, the system does not run Group Policy or Desktop Standard PolicyMaker client-side extensions (CSEs). Additionally, one of the following error messages may be written to the event log:
 * Windows cannot obtain the domain controller name for the computer network. (The specified domain either does not exist or exist and could not be contacted). Group Policy processing aborted
 * 0x8007054b -The specified domain either does not exist or could not be contacted.

Notes
 * You may also receive this error in the Policy Maker Standard Edition trace reports.
 * The wording that is listed here for the first message is the actual wording of the message. This includes the phrase &quot;either does not exist or exist.&quot;



CAUSE
This issue occurs because the link status fluctuates when the network adapter driver initializes. This issue also occurs because the network adapter hardware negotiates a link with the network infrastructure.

Note The network adapter driver is also known as the network interface card, or NIC.

The Group Policy application stack executes before the negotiation process is complete. The application stack can fail because a valid link is missing.



WORKAROUND
To work around this issue, disable the Media Sense feature in Windows. For more information about how to disable Media Sense, click the following article number to view the article in the Microsoft Knowledge Base:

239924 How to disable Media Sense for TCP/IP in Windows

If the computer still does not apply Group Policy or PolicyMaker Standard Edition CSEs after you disable Media Sense, make sure that you are running the most current drivers for the network adapter. If you are already running the most current drivers for the network adapter, the only other workaround that is currently available is to switch to a different network adapter.

Keywords: kbtshoot kbexpertiseinter kbprb KB931067

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.