Desktop

Ask something
Question Locked

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

0 helpful
13 replies

by miketkelly

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

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.

13 replies

by w2ktechman

removing the computer from the domain and re-adding it?

by miketkelly

re-added once already
is there something I can test on the server to ensure it is setup correctly for logging on or is this an issue with the client

by w2ktechman

working properly, and this system is not, more than once, it is likely the install or a service has failed.
What happens with a re-install of the OS?

by maex

...this...
I would go about it like so...

Do a NSLOOKUP on your DC from the PC.

Telnet your AD on your DC from that PC.

If something is strange, would delete machine account from AD, and put PC in workgroup mode and verify network settings. Check Netbios, usually is on Default.

Join the AD, from the PC.

by miketkelly

doing nslookup server00-dc and these are my results

*** Can't find server name for address 172.20.1.117: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 172.20.1.117

Name: server00-dc.
Address: 172.20.1.117

I also tried my secondary DC (server01-db)

*** Can't find server name for address 172.20.1.117: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 172.20.1.117

Name: server01-db.
Address: 172.20.1.118

is this telling to anyone

I also tried taking the client pc off the domain changing the computer name and rejoining the domain

Thanks for all the suggestions so far

by miketkelly

I was using FRSDiag.msi to check out some of the problems

would the fact that my current server's (server00-dc) member name is the old computer name (VISION-1E30CAA5) have anything to do with the problem I'm having

I had actually completely forgot that this server's name was changed until I saw this

=================================================
Replica Set GUID: 96a3551d4e96-4cod-a0145f5b51fd22226
Replica Set Name : DOMAIN SYSTEM VOLUME (SYSVOL SHARE)
======================================================
GUID_________MEMBERNAME__________SERVER NAME
--------------------------------------------------------------------------------------------------------
#######______SERVER01-DB___________server01-db
#######______VISION-1E30CAA5________server00-dc
======================================================

=============================================
Replica Set GUID: ######################
Replica Set Name: DFS Network Share
=============================================

by seanferd

Something about being unable to apply gp when no when no one is logged on or some other reason.

Local Policy:
Computer\Administrative Templates\System\Logon\[Always wait for the network at computer startup and logon]

I had to mess with this when I was given a computer that was pulled right off a domain and given away when Stupid Wasteful Bank was upgrading.

Anyway, it's somewhere to look.

by don19

A post on Microsoft says:

This problem occurs when the time-stamp counters for different processor cores are not synchronized. Windows Server 2003 uses the time-stamp counter as a timekeeping source. Each processor contains a time-stamp counter.

To resolve this problem, configure Windows Server 2003 to use the PM_TIMER setting instead of the time-stamp counter. To do this, add the /usepmtimer parameter to the Boot.ini file, and then restart the server.

Note that the /usepmtimer parameter is automatically added to the Boot.ini file when you install the latest AMD PowerNow! Technology driver from AMD. The updated driver itself does not resolve this problem. However, the installation process makes the necessary changes to the Boot.ini file to resolve this problem.

by ashishpatel

frist check your network settings using admiitrator account i think there is some problem with your network.....

Ashish Patel

This discussion is closed to new replies.