• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 249
  • Last Modified:

Domain Controller Issue

Hi All hoping you can help me.

I have two Domain controllers in my network, and I also have a Terminal Server.

I had an issue this morning where it would take ages logging onto the Terminal Server, Users also Reported that Web Sites , and connection from within the Terminal Server to Exchange
was also reporting that Microsoft Exchange Was offline.

I checked the Status of the DC's and they were UP, I then went into the network properties of the Terminal server and in the DNS settings there was 1 entry which was the Primary Domain Controller, I added the second DC, and logging in speeded up.
They could also access their email although they were prompted with a username and password box.

I am guessing I am right thinking that this a DNS Issue?

Can anybody help me to fault find this issue, I'm worried now that if I loose my DC2 I am going to have real issues

1 Solution
Please make sure your DHCP server distributing both DCs as DNS server to the clients. If your DCs have multiple NICs, make sure that your DNS server listening the 1 only whihc is your DCs IP address.
Nagendra Pratap SinghCommented:
I guess DC1 is already a DNS. If not, make both of your DCs DNS servers (AD integrated).
Miguel Angel Perez MuñozCommented:
Check your DNS service on DC1 and restart it if not responding. Try rebooting DC1, sometimes reboot is needed.
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

pepps11976Author Commented:
Yes I believe that both DC's are DNS Servers
however I have just looked in the event log and found the following error for the 10/01/2013

ID 4015

Event Type:      Error
Event Source:      DNS
Event Category:      None
Event ID:      4015
Date:            10/01/2013
Time:            03:39:24
User:            N/A
Computer:      DC1
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0000: 51 00 00 00               Q...
can you run and test your DC with the following command
(cmd-Run as administrator)
dcdiag /test:dns /v
pepps11976Author Commented:
Ok I ran the test at the end it said passed test DNS

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.

Join & Write a Comment

Featured Post

WEBINAR: GDPR Implemented - Tips & Lessons Learned

Join the WatchGuard team on Thursday, March 29th as we recount some valuable lessons learned in weighing the needs of a business against the new regulatory environment, look ahead at the two months left before implementation, and help you understand the steps you can take today!

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