many errors like this

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
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
Dennis MillerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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.
Rob WilliamsCommented:
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:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dennis MillerAuthor Commented:
Thanks. I will inform the DNS admin.
Rob WilliamsCommented:
Thanks millerdog, good luck with it.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.