м Windows Server R2 2003, м м м м : Source: Userenv ID: 1054 Windows cannot obtain the domain controller name for your computer network. (An unexpected network error occurred. ). Group Policy processing aborted. - , м ?

Hi MikAnder , Seems this most often occurs when the network connection fails or has not completed before Windows tries to contact the domain controller. I see you have tried the GPO "fix". A couple of other ideas as food for thought; http://support.microsoft.com/default.aspx?scid=kb;en-us;840669#E6ADAAA assuming there is more than one network adapter (wired and wireless) check the network adapter binding order in advanced Network Connections, and make sure your adapter is at the top of the list It is possible a software firewall, if one is installed, might be blocking RPC or other network services. Disable any at least for testing purposes. Regards. Shafaquat Ali. M.C.I.T.P Exchange 2007 M.C.I.T.P Windows Server 2008 M.C.T.S OCS Server 2007 R2

Hello, sorry but this forum is in english language, so either switch complete to english or use one in your language, thank you for understanding. The error you see often belongs to misconfigured DNS settings, so make sure to use only the domain DNS servers on the machines NIC and not the ISPs.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Hi, According to your description, I understand that you received an Event ID 1054 error on the DC. This behavior may occur if the address for the configured preferred DNS server unreachable. To narrow down this issue, please run the nslookup command to isolate the DNS issue. (1) Type nslookup, and then press ENTER. (2) Type set type=all, and then press ENTER. (3) Type _ldap._tcp.dc._msdcs.domain.com and then press ENTER. In addition, These errors can occur because link status fluctuates as the network adapter (also known as the network interface card, or NIC) driver initializes and as the network adapter hardware negotiates a link with the network infrastructure. The Group Policy application stack executes before the negotiation process is completed and can fail because of the absence of a valid link. Resolution 1: To resolve problem related to link status fluctuation use the steps in 239924 - "How to disable Media Sensing for TCP/IP in Windows" at http://support.microsoft.com/?id=239924 . To prevent your network adapter from detecting the link state: 1. Open Registry Editor (Regedt32.exe). 2. Go to the following key in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters 3. Add the following registry value: Value Name: DisableDHCPMediaSense Data Type: REG_DWORD -Boolean Value Data Range: 0, 1 (False, True) Default: 0 (False) Resolution 2: Contact the vendor of the network card or visit their web site to obtain updated drivers for the Gigabit NIC. Examples of NICs known to exhibit this issue: - Broadcom Gigabit Adapter - Intel Gigabit Ethernet PRO Adapter, Intel Pro/1000 - Intel 82544EI-based XT Gigabit Adapter (82540EM chipse) - Compaq/HP NIC dual interface 10/100/1000 doing teaming (HP NC7170) - Dell Inspiron laptops using an on-board Broadcom BCM4401 NIC Resolution 3: A sever may have a Dual Port NIC or multiple NIC's with one port or NIC set to Disabled. The disabled port or NIC should not be at the top of the binding order in the Network Advance Properties. 1. Click Start, point to Settings, and then click "Network and Dial-up Connection". 2. On the Advanced menu, click "Advanced Settings". 3. On the "Adapters and Bindings" tab, in the connections list, select the NIC that the clients use to connect to the server and move it to the top of the list. Resolution 4: Disabling spanning tree on the switches (Cisco Catalyst) Note: STP=Spanning Tree Protocol. Turning off STP can cause issues in your network if a loop ever develops. If you are running a Cisco Series switch or any other switch that runs Spanning Tree, it is best to leave spanning tree turned on, but enable PORTFAST on all the ports except uplink and fiber trunks. (I.E any ports that aren't connected to a workstation directly should not have it enabled, ports that do go directly to a workstation or computer should have it turned on.) PORTFAST eliminates the 50 second waiting period that STP has, but allows you to keep the functionality of STP. For more References, you can refer to: 326152 PRB: Cannot Connect to Domain Controller and Cannot Apply Group Policy http://support.microsoft.com/kb/326152 298656 Event ID 1054 Is Logged in the Application Event Log http://support.microsoft.com/kb/324174/en-us 239924 How to Disable Media Sense for TCP/IP in Windows http://support.microsoft.com/kb/239924 Sincerely, Wilson Jia This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

This all not help me. Michael