Windows cannot obtain domain controller name for your network

Hello...I have read the past posts in regards to this specific issue, but the resolution didn't work. I have tried adding the Reghack and updated the NIC drivers. Our client OS is Windows XP. I am able to authenticate with the DC's, but when you look in the event logs the following is tagged:
  • Remove From My Forums

  • General discussion

  • Hello…I have read the past posts in regards to this specific issue, but the resolution didn’t work. I have tried adding the Reghack and updated the NIC drivers. Our client OS is Windows XP. I am able to authenticate with the DC’s, but when you look in the event logs the following is tagged:

    Windows cannot obtain the domain controller name for your computer network. (An unexpected network error occurred. ). Group Policy processing aborted.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in 15 minutes.

    The funny thing is some of the GPO’s that I defined have been applied – just added some interactive messaging, and that worked?!? When I go to the ‘run’ command I can hit the domain controller and see the SYSVOL share.

    This is a brand new setup with two Windows 2003 SP domain controllers.

    ZT

    • Changed type

      Monday, November 9, 2009 2:49 AM

Источник

We installed a few new computers to the network, and all of them appear to be having the same issue in Application Event Log:

Windows cannot obtain the domain controller name for your computer network. (The network path was not found. ). Group Policy processing aborted.

These workstations can still log into the domain, but deployed software installs and such to network computers are not taking place for these machines.

Is there a likely cause to this? Again, these were brand new machines, same OS (Win XP Pro) as all others.

asked Feb 18, 2010 at 16:51

CandyCo's user avatar

5

Obviously, be sure that the «problem» computers have the same DNS server specified as the «working» computers. (Ideally they’re having that set by DHCP.)

It seems unlikely that your Ethernet switch’s spanning tree implementation would be blocking access, but to be sure that it’s not switch port-related you might try one of the «problem» computers on one of the ports used by a known-working computer.

Some NICs have a problem with «media sense» and can cause problems with Group Policy processing. If you see event log entries from the NIC driver about the network connection coming up after the entries complaining about being unable to find the domain controller name then you’ve probably got a media sense problem. Have a look here for more background:

  • http://support.microsoft.com/kb/239924

  • http://support.microsoft.com/kb/326152

answered Feb 18, 2010 at 16:56

Evan Anderson's user avatar

Evan AndersonEvan Anderson

141k19 gold badges192 silver badges329 bronze badges

2

Make the client PCs use the Domain Controllers as DNS servers. Check that the proper SRV records are in the DC’s DNS records. Run DCDIAG /TEST:DNS on the Domain Controllers to check for any errors in the DNS records.

answered Feb 18, 2010 at 16:56

Wesley's user avatar

WesleyWesley

32.4k9 gold badges80 silver badges116 bronze badges

2

Does your switch have STP enabled? If so, try disabling it on the ports for the affected computers (enable portfast). There’s also a GPO andor registry setting you can try:

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon]
«WaitForNetwork»=dword:00000001

answered Feb 18, 2010 at 20:44

joeqwerty's user avatar

joeqwertyjoeqwerty

109k6 gold badges80 silver badges171 bronze badges

Check if you’re assigning an FQDN as part of your DHCP setup and correct it if it’s not the same as your DNS domain name.

answered Feb 18, 2010 at 22:41

Maximus Minimus's user avatar

Maximus MinimusMaximus Minimus

8,9571 gold badge22 silver badges36 bronze badges

XP uses ICMP to check connectivity to domain controllers in order to decide whether to be selective about applying Group Policies. If ICMP is blocked or restricted by your network then you will see the error you report for XP systems. Vista and Windows 7 use NLA which isn’t affected by this. Obviously since most of your XP systems don’t have this issue it’s not a core network problem but possibly these new systems all connect via a common switchrouter that is doing something undesirable. It may not be the root cause but if it is this Microsoft KB article discusses some mitigation approaches if you can’t fix this on the network hardware.

answered Feb 18, 2010 at 22:57

Helvick's user avatar

HelvickHelvick

19.7k4 gold badges37 silver badges55 bronze badges

1

Источник

img

Are you getting the following error on your Windows Server 2003? If so, your event viewer is probably displaying this error every 5 minutes.

Event ID: 1054
Source: Userenv
Type: Error
Description: Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted). Group Policy processing aborted.

error1054

Microsoft’s KB article 324174 addresses this issue. This behavior may occur if the address for the configured preferred DNS server on the client is invalid or unreachable. This error may also cause the client computer to take a long time to logon. To resolve this issue, correct the DNS address in the TCP/IP properties.

NOTE: If you are getting this error in Windows XP, then check out this KB article 298656.

This div height required for enabling the sticky sidebar

Источник

Problem

During the IBM® Rational® Build Forge® installation, it fails with a Microsoft® Windows® authentication error, []Error code 1265[].

Symptom

Build Forge installation fails with the error code: 1265 — The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you.

This symptom exhibited by the Build Forge installer is due to a Windows authentication error. The problem is specific to installations using the built-in IBM DB2, which attempts to create a new local user for database access.

Cause

This is caused by a failure of the Windows client to contact its domain controller to validate its group policy and certificate information for the user. This is needed in order for the installer, running as the current logged in user, to create a new local user to access DB2.

Diagnosing The Problem

The application log may show something like these messages:

Automatic certificate enrollment for DOMAINuser failed to contact the active directory (0x8007054b).  The specified domain either does not exist or could not be contacted.

OR

Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

Note: These are is only examples, and the application log should be consulted for more specific details regarding the failure.

Resolving The Problem

Verify that the PDC can be contacted, and that the WINS settings for the host are correct.

WORKAROUNDS:

  1. Install while logged into a local user account, like Administrator or a local account that is a member of the local administrators group. This will remove the need for a PDC lookup.
  2. Use an already existing user to connect to DB2. This will also allow for the installation to proceed since no new user will need to be created.

[{«Product»:{«code»:»SSB2MV»,»label»:»Rational Build Forge»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud & Data Platform»},»Component»:»Engine: Installation»,»Platform»:[{«code»:»PF033″,»label»:»Windows»}],»Version»:»7.0.2″,»Edition»:»Enterprise;Standard;Express»,»Line of Business»:{«code»:»LOB45″,»label»:»Automation»}}]

Источник
Details
Product: Windows Operating System
Event ID: 1054
Source: Userenv
Version: 5.2
Symbolic Name: EVENT_FAILED_DSNAME
Message: Windows cannot obtain the domain controller name for your computer network. (%1). Group Policy processing aborted.
   
Explanation

A network connectivity or configuration problem exists. Group Policy settings cannot be applied until the problem is fixed.
   
User Action

To troubleshoot the network connectivity or configuration problem, try one or all of the following:

  • In Event Viewer, click System, and check for any networking-related messages, such as Netlogon messages, that indicate a network connectivity issue.
  • At the command prompt, type netdiag, and note any errors. Those errors usually have to be resolved before Group Policy processing can continue.
  • At the command prompt, type gpupdate, and then check Event Viewer to see if the Userenv 1054 event is logged again.
  • To verify that the domain controller can be contacted through Domain Name System (DNS), try to access \mydomain.comsysvolmydomain.com, where mydomain.com is the fully qualified DNS name of your domain.
  • Verify that you can access the domain controller by using tools such as the Active Directory Users and Computers snap-in.
  • Check to see whether other computers on your network are having the same problem.
  • If this computer is a part of a cross-forest domain, verify that the forest for the user account is currently available and can be contacted by the computer on which the Group Policy processing failed.

If none of the above actions identified the problem, see the ‘Troubleshooting Group Policy in Windows Server 2003’
white paper at the Microsoft Web site.
Источник

  • Windows Cannot obtain the domain controller name for your computer network.

    I’ve been having a problem with one of my client computers. Every time the computer logs onto the domain this error is logged.
    ============================
    Event ID: 1054
    Source: Userenv
    User: NT AUTHORITY/SYSTEM
    Description:
    Windows Cannot obtain the domain controller name for your computer network. (An unexpected network error occurred.) Group Policy processing aborted
    ============================

    on the domain controller I get two entries into the security log with the user being the client computer name

    first this one-
    Event ID: 540
    Source: Security
    Category: Log on / Log off
    Successful Network Log on:
    username: (client computer name)
    logon type: 3
    Logon Process: Kerberos
    Authentication Package: Kerberos

    the second one is rather long but the category is Directory Service Access

    If anyone could help me get through this that would be fantastic and your help would be greatly appreciated.

    • Источник

    Can someone please help!!! I have been fighting this issue for awhile now.

    I have 4 different offices. 1 main office (where all my servers are) and the other 3 just have user computers. We are all connected VPN via checkpoint firewalls.

    I am trying to apply group policies to my users but whenever they try to logon they are getting Windows cannot obtain the domain controller name for your computer network return value(59) in the event viewer, and no GP’s are being applied. However they are able to logon to the domain and browse to the sysvol at my main office with the dns name without any problems!

    Here is something that puts a twist into things, at one of my sites i setup a DC and after that the GP’s were being applied with no prob, however once I took it offline they once again were getting the above message and no GP’s.

    I checked MS site and cannot find anything helpful, all I can find is reference to DNS errors, but my users are all using the correct DNS servers.

    I have checked my firewall logs and Im not seeing anything dropped, I have even added a route to my servers for my remote offices.

    Please someone help, I am about at the end of my rope!

    Источник

    Like this post? Please share to your friends:
  • Windows cannot load the extensible counter dll oracle11
  • Windows cannot install required files make sure all files
  • Windows cannot install required files 0x80070570
  • Windows cannot install required files 0x8007025d что делать
  • Windows cannot install required files 0x80070017