We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now

x

many errors like this

Dennis Miller
on
Medium Priority
274 Views
Last Modified: 2010-03-19
Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1054
Date:            4/4/2006
Time:            10:02:55 AM
User:            NT AUTHORITY\SYSTEM
Computer:      ANNSLACOMB
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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Comment
Watch Question

Is the computer part of a Domain or was it previously?  If so, is it connected to the network/domain?  What OS do you run?  Is this a home or work PC?

This message is received when the computer is a member of a Domain and network issues are stopping it contacting the Domain Controller for authentication during login.
Sound like a dns issue. Make sure you dns settings are correct as well as nic card link light, the ip address and rejoin domain for the last step.
CERTIFIED EXPERT
Top Expert 2013
Commented:
There can be numerous reasons for this message. The one I have found is most common, is incorrect DNS configuration. Check the following:
-The DNS Server's DNS entries in it's NIC TCP/IP properties should only point to itself
-The Workstations, and member servers, should only point to your DNS server in their NIC TCP/IP properties, whether statically or through DHCP
-The DNS server should be configured with the ISP's DNS servers as forwarders in the DNS management console. Do not add the ISP's DNS to the NIC's DNS entries
-On the DHCP server add the DNS server's IP to option 006 in the DHCP scope
-Make sure on the workstation's NIC TCP/IP properties, under advanced/DNS that if entered the DNS suffix is correct. If not added, it is a good idea to add it there or through the DHCP scope.

Other possible causes can be found at:
http://www.eventid.net/display.asp?eventid=1054&eventno=1393&source=Userenv&phase=1

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Author

Commented:
Thanks. I will inform the DNS admin.
CERTIFIED EXPERT
Top Expert 2013

Commented:
Thanks millerdog, good luck with it.
--Rob
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.