Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1240
  • Last Modified:

Win2003 servers, Event ID 1054, two DC's the second server cannot obtain domain controller name. NEED HELP...

Hi,

I'm new to EE and need some help..here is my problem.
I have installed two Windows 2003 standard servers (Saturn & Venus) in a new domain 'OVUK'. Both servers are fully patched and have had no extra software installed.Saturn is set for DNS & Wins. My problem appears to be on Venus.

 From computer Manager I am looking in Event Viewer at the Application log and I have an error repeating at exactly five minute intervals. The error is
 Event ID 1054,
 Source userenv,
type error
User NT Authority\system.
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 proccessing aborted.

So there you have it.. Im stuck. I can't seem to find out much on 1054, so now I have arrived at the house of knowledge. I may evem have to join after this :¬)

Hope someone can help..

Regards

Tim

I only have a 195 points sorry.
0
TimWe
Asked:
TimWe
  • 3
  • 2
1 Solution
 
Pete LongTechnical ConsultantCommented:
Sounds like a DNS issue?

SYMPTOMS
The following event may be logged in the application event log:
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.
The client computer may also experience an extremely slow logon.
CAUSE
This behavior may occur if the address for the configured preferred Domain Name System (DNS) server on the client is not valid or unreachable.
RESOLUTION
To resolve this issue, correct the DNS address in the Internet Protocol (IP) properties. To do this, follow these steps:
Click Start, point to Settings, click Control Panel, and then double-click Network Connections.
Right-click Local Area Connection, and then click Properties.
Click Internet Protocol (TCP/IP), and then click Properties.
Click the Use the following DNS server addresses option, if it is not already selected.
Type the correct DNS address in the Preferred DNS server box.
Click OK.
0
 
TimWeAuthor Commented:
Hi, Thanks for the comment.
OK I have had a look on Venus and the DNS settings are correct. In 'prefered server' I have the IP address of Saturn (10.10.10.3)my DNS server.
In the 'alternate Server' field I have the IP address for my ISP DNS server. (195.184.228.6).
Login is very slow as you mention & the 1054 error occures every 5 minutes exactly.
I see that the default gateway is pointing at our firewall should this point to saturn instead? These IP settings are static not assigned via a dhcp server.

Whats Next? :¬(

0
 
TimWeAuthor Commented:
Hi,

I ran Dcdiag, dont know if this helps or may its just a consequence .

here are the results


===================================================================================================

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\VENUS
      Starting test: Connectivity
         The host 9158f822-fdf8-4b1f-8b39-4631843f1cf6._msdcs.dns_uk.orthoview.c
om could not be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name
         (9158f822-fdf8-4b1f-8b39-4631843f1cf6._msdcs.dns_uk.orthoview.com)
         couldn't be resolved, the server name (venus.dns_uk.orthoview.com)
         resolved to the IP address (10.10.10.6) and was pingable.  Check that
         the IP address is registered correctly with the DNS server.
         ......................... VENUS failed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\VENUS
      Skipping all tests, because server VENUS is
      not responding to directory service requests

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : dns_uk
      Starting test: CrossRefValidation
         ......................... dns_uk passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... dns_uk passed test CheckSDRefDom

   Running enterprise tests on : dns_uk.orthoview.com
      Starting test: Intersite
         ......................... dns_uk.orthoview.com passed test Intersite
      Starting test: FsmoCheck
         Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
         A Global Catalog Server could not be located - All GC's are down.
         Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
         A Primary Domain Controller could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
         A Time Server could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 135
5
         A Good Time Server could not be located.
         Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
         A KDC could not be located - All the KDCs are down.
         ......................... dns_uk.orthoview.com failed test FsmoCheck

==================================================================================================
0
 
TimWeAuthor Commented:
Thanks to PL for the help.
Eventually Changed DHCP server to only issue the address of our internal DNS server.
Recreated the DNS server on Saturn and added ISP address to Forwarders. Then Ran  Netdiag /Fix,  Netdiag /debug ..Start/Stop Netlogon service..Voila!

Many Thanks for the Cognative Nudge Pete.

Regards

Tim
0
 
Pete LongTechnical ConsultantCommented:
:0) ThanQ
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now