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

x
?
Solved

Event ID 2102 All domain controller servers in use are not responding

Posted on 2005-04-04
7
Medium Priority
?
19,664 Views
Last Modified: 2011-08-18
Hello,

On our Exchange 2003 server we consistently get the following error;

Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2102
Date:            04/04/2005
Time:            08:22:26
User:            N/A
Computer:      GINTOSERVER1
Description:
Process EMSMTA.EXE (PID=3720). All Domain Controller Servers in use are not responding:
gwintoserver.gwinto.co.uk
dc1.gwinto.co.uk
gintoserver1.gwinto.co.uk
 

For more information, click http://www.microsoft.com/contentredirect.asp.

Our exchange server (gintoserver1) can ping the other two servers, the other two servers are up and running with the ports for LDAP and GC both open and listening.  Any ideas to what could be causing this or things i can try to troubleshoot this problem?

thanks in advance

euskills
0
Comment
Question by:euskills
  • 4
  • 3
7 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 13696579
First check that the Exchange server is using the domain controllers ONLY for DNS, no external DNS servers should be listed in the network configuration.

Next, install the Windows support tools from the server CD on to both the domain controllers and the Exchange server. There are some tests on there that can confirm the connectivity to the domain. The two that you need are DCDIAG and NETDIAG. See whether you get an errors, if so, resolve them or post them here for diagnostics. Try and limit how much you post as they can create very large log files.

Simon.
0
 

Author Comment

by:euskills
ID: 13696616
Hi,

The DC passed all dcdiag tests.  On netdiag it passed all but provided a warning for the following;

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.

The Exchange server is only using our Internal DNS server.

thanks in advance.

euskills
0
 
LVL 104

Expert Comment

by:Sembee
ID: 13696934
WINS errors are fine.

Did the tests pass on the Exchange server as well?

Simon.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:euskills
ID: 13696975
Hi,

Sorry, those are the results from the Exchange server.  The other DC reports the following errors on dcdiag;

      Starting test: frssysvol
         There are errors after the SYSVOL has been shared.
         The SYSVOL can prevent the AD from starting.
         ......................... GWINTOSERVER passed test frssysvol
      Starting test: kccevent
         An Warning Event occured.  EventID: 0x800004F1
            Time Generated: 04/04/2005   13:20:54
            Event String: The attempt to establish a replication link with
         An Warning Event occured.  EventID: 0x800004F1
            Time Generated: 04/04/2005   13:21:17
            Event String: The attempt to establish a replication link with
         An Warning Event occured.  EventID: 0x800004F1
            Time Generated: 04/04/2005   13:21:40
            Event String: The attempt to establish a replication link with
         ......................... GWINTOSERVER failed test kccevent


and the following on netdiag;

DNS test . . . . . . . . . . . . . : Failed
    [WARNING] The DNS entries for this DC are not registered correctly on DNS server '10.0.1.4'. Ple
ase wait for 30 minutes for DNS server replication.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS server '10.0.0.4'. Ple
ase wait for 30 minutes for DNS server replication.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS server '127.0.0.1'. Pl
ease wait for 30 minutes for DNS server replication.
    [FATAL] No DNS servers have the DNS records for this DC registered.

I will rung netdiag /fix to sort out the DNS issue.

Thanks in advance.

euskills
0
 
LVL 104

Expert Comment

by:Sembee
ID: 13700964
First - pull out 127.0.0.1 in the DNS entries as I have seen that cause problems. DNS entries should be the computer's real IP address. You may also want to look at the DNS server settings to ensure that they are AD integrated and there aren't any errors in the event logs relating to DNS.

Most of these types of problems are DNS related... it is just a matter of tracking down where.

Simon.
0
 

Author Comment

by:euskills
ID: 13704789
Hi,

127.0.0.1 is not listed in the DNS lookup zone for our domain - I think its just part of the netdiag /test:dns test.

The DNS server all seems fine, its a AD integrated and the logs look clean (there are some errors but they are regarding receiving invalid formatted packets for updates from a server that isnt on our network and have been on there for a few weeks)

Thanks in advance
0
 
LVL 104

Accepted Solution

by:
Sembee earned 750 total points
ID: 13705937
127.0.0.1 must be in the configuration somewhere as I have just run the same test on a domain controller and it isn't listed anywhere.

DNS doesn't tend to error much, so seeing old entries in the log is quite normal. The DNS event log doesn't have the traffic that system and application do. Therefore if it is clean then it should be behaving itself. You may have to look at the DNS configuration on the Exchange server instead.

One other thought I had was whether the DCs that Exchange is looking to for DNS are also global catalogs. I have seen errors when this isn't the case.

Simon.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Steps to fix error: “Couldn’t mount the database that you specified. Specified database: HU-DB; Error code: An Active Manager operation fail”
In this post, we will learn to set up the Group Naming policy and will see how it is going to impact the Display Name and the Email addresses of the Group.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Suggested Courses

571 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question