Need help resolving Event ID 1054 errors appearing in event log every 5 mins!

Need help resolving Event ID 1054 errors appearing in event log every 5 mins!

Post by thelotus9 » Sun, 15 Jul 2007 05:37:47

Hello all:

I have a newly installed domain controller for a client of mine that
I'm having a problem with, and am hoping I can get some good advice
tracking down the problem. This is for a small office, with about 8
computers total. This server is the first domain controller, as
previously the network was set up with all stand-alone computers.
a custom built box running Windows 2003 Small Business Server SP2.
Hardware specs are AMD Athlon 64 X2 Dual Core 3800+ with 2GB RAM.

The problem I'm trying to solve is Event ID 1054 appearing in the
Application Log every 5 minutes like clockwork, for the last few
months now.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1054
Date: 7/10/2007
Time: 10:47:45 AM
Windows cannot obtain the domain controller name for your computer
network. (An unexpected network error occurred. ). Group Policy
processing aborted.

I'm thinking this is a TCP/IP or DNS issue, and I'll explain why. I
thought I had the problem solved recently, after noticing some
entries in the DNS server. I saw entries pointing to the server's
hostname, with an IP address of 169.254.x.x, which reminded me of
forum posts and articles in the past referring to problems you can
have on a domain controller with multiple NICs, and this server does
have 2 NICs. One I had configured with a valid static IP address, and
the other was enabled, but not connected to the network and no IP
address assigned. I think that this second network card was causing
the 169.254 entries to appear in DNS. So, I disabled the 2nd NIC, and
cleaned up all the bad entries in DNS. I thought I had fixed it!
were no further errors for 4 hours, but during the night, they
again. It was strange though, because the first night, they were only
happening every 15-30 minutes, instead of the standard 5 minutes that
it has been happening with for the last few months. But, even now,
it's back up to every single 5 minutes, I get a new entry in the

Also, I have thried the suggestions in this article:

Can anyone offer any advice as to further troubleshooting steps I
should take with this server? I really don't want to scrub the hard
drives and start over, but I'm afraid that might be my only choice at
this point! Thanks much in advance!!!!

1. Help - Security Event Log Posts Error Event ID 560 every few seconds!

2. Event ID ( 4521 ) appear every 3 min after SP2 installed Help :(

Hello Everyone.

I am continously getting this warning message in the DNS event log after we
installed SP2 to our windows 2003 Root AD Server. I saw some of the post here
people also received 9002 event error. but in my case I don't see any.

I have restarted net logon service , this does since to fix the problem. any
help or suggestion will be really appreciated.

The description for Event ID ( 4521 ) in Source ( DNS ) cannot be found. The
local computer may not have the necessary registry information or message DLL
files to display messages from a remote computer. You may be able to use the
/AUXSOURCE= flag to retrieve this description; see Help and Support for
details. The following information is part of the event: 9002, ..

3. Event ID ( 4521 ) appear every 3 min after SP2 installed Help

4. Event 29, Event 40961 and Event 1054

5. Getting event id 1000 error on every 5 mins in domain controllers - can anyone help?

6. event id 1054 userenv error

7. Help with Event ID 1054

8. Detect the latest Event log occcurence of a particlar Event ID in the Event log

9. Error 1054 in Event Logs

10. Event Log Error: Event Source:WinMgmt Event ID:10

11. Event ID: 1003, Event Type: Error ,Event Source: System Error,Event Category: (102)

12. Security log event ID 529 & System log event ID 10004

13. Event ID 1003 : Source BINLSVC : Posted to Application Event Log Every 35 Seconds

14. Event ID 10016 Source DCOM error every 15 min after applying Win2K3 SP1

15. Event ID 577 appears repeatedly in the security event log