Windows Server SystemPost your Windows Server System question here. Besides Windows Server 2003, Windows Server System also includes other Microsoft Server software (such as BizTalk Server, Exchange Server, ISA Server & others).
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
We have been having some DNS issues on a few of our servers which i believe are causing Active Directory to crash. When trying to access active directory user and computers, domains and trusts, we sometimes get the erroe "the server is not operational" Usually a reboot fixes the problem but this is not always the easy to do as we have clients accessing the servers 24 hours a day.
Upon examination of the DNS logs there are numerous errors such as:
Event ID 4015:
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.
Event ID 9999
The DNS server has encountered numerous run-time events. To determine the initial cause of these run-time events, examine the DNS server event log entries that preceded these run-time events. The data is the number of events that have been suppressed in the last 60 minute interval.
Event ID 404
The DNS server could not bind a Transmission Control Protocol (TCP) socket to address 0.0.0.0. The event data is the error code. An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all configured IP addresses on the computer are available for use.
Restart the DNS server or reboot the computer.
EVent ID 408
The DNS server could not open socket for address 0.0.0.0.
Verify that this is a valid IP address for the server computer. If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces. Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error. In that case remove the DNS\Parmeters\ ListenAddress value in the services section of the registry and restart.)
If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.
There are hundreds of these errors all through the error log, Our DNS has seemed to work well for quite a long time, there have been no major changes to the system that would be causing these errors.
All servers are windows 2003
any one got any suggestions?
Didn't find the information you thought to find? Check out these Similar Threads
You speak of rebooting servers but don't say which one(s). Are you bouncing one or more of your DNS servers to clear this error or only the box that fails the connection?
You speak of rebooting servers but don't say which one(s). Are you bouncing one or more of your DNS servers to clear this error or only the box that fails the connection?
How many DNS servers are you running?
OK the problem is occuring with 3 DNS servers, which are all the PDC's of 3 different domains. All 3 servers are linked by two way trusts, and all servers and windows 2003 standard.
When this problem occurs the only way we have found to fix it is to reboot the the server(s). Normally when the problem happens to one server it will happen to the other ones within a few days of each other.
Are you running one or more of your DNS servers as a root server by any chance?
AD crashing - I still don't understand that.
PDC in an AD domain setup - I don't understand that either. You should have domain controller(s) and maybe global catalog server(s) but PDC/BDC was classic NT4 domain stuff.
Are you running one or more of your DNS servers as a root server by any chance?
AD crashing - I still don't understand that.
PDC in an AD domain setup - I don't understand that either. You should have domain controller(s) and maybe global catalog server(s) but PDC/BDC was classic NT4 domain stuff.
No no root servers.
by AD crashing i mean that when i try to open up AD either users and computers, domains and trusts or sites and services, it doesnt open and a big long error message comes up that I cant remember right now but the last thing it says is "The server is not Opperational." And AD wont even open up. Only a restart fixes it for a while.
Yes sorry for the PDC reference, force of habbit. All servers are just DC's for their respective domains
After doing some digging I couldn't find the answer I was looking for in Standard Vs Enterprise.
It appears all versions support this:
Quote:
Cross-forest trust
Cross-forest trust provides a new type of Windows trust for managing the security relationship between two Active Directory forests. This feature vastly simplifies cross-forest security administration and enables the trusting forest to enforce constraints that determine which security principal names it trusts other forests to authenticate.
