Hello everyone.
I have a curious question but first let me lay out our network
root domain: 3 DC's - 1 of them in a co-location site (holds all 5 roles)
child domain 1 (sits within the same walls of the root domain): 1 dc
child domain 2 (remote office): 2 dc
child domain 3 (remote office): 1 cd
All servers are 2003 Enterprise, AD Integrated and each domain runs DNS and DHCP.
Now when I reboot that single DC that is at the co-location site all 4 domains (including childs) become unavailable. If I try to log into a workstation or server under any domain it gets mad at me and screams:
"The system cannot log you un due to the following error: The specified domain either does not exist or could not be contacted. Please try again or consult your system administrator".
It can take up to 15 minutes for everything to get back to normal in regards to access to network resources.
Now we've ran DCDIAG, Netdiag and DNSDiag and we're clean, good replication and no errors. All machines can ping each other cross domain via ip and unc. We've also checked our FSMO roles for each DC and they were configured as recommended by MS (as to what I remember I did about 2 years ago or so). I am attaching a report of our 7 DC's and their FSMO roles (no worries, domain name changed to protect the innocent).
Our DHCP server scope options are configured to assign the 1st DNS IP to workstations/servers of the DC within their domain/child followed by the other 3 IP addresses of the DC's from our main office which includes the co-lo DC. My understanding is that if the 1st DNS is not available the workstation/server should then find the IP address that is next in line and try to resolve through that one. Am I correct?
All the servers except for the co-lo is a global catalog server.
Hope I explained as much as I could.
Thank you for reading,
ceez
I have a curious question but first let me lay out our network
root domain: 3 DC's - 1 of them in a co-location site (holds all 5 roles)
child domain 1 (sits within the same walls of the root domain): 1 dc
child domain 2 (remote office): 2 dc
child domain 3 (remote office): 1 cd
All servers are 2003 Enterprise, AD Integrated and each domain runs DNS and DHCP.
Now when I reboot that single DC that is at the co-location site all 4 domains (including childs) become unavailable. If I try to log into a workstation or server under any domain it gets mad at me and screams:
"The system cannot log you un due to the following error: The specified domain either does not exist or could not be contacted. Please try again or consult your system administrator".
It can take up to 15 minutes for everything to get back to normal in regards to access to network resources.
Now we've ran DCDIAG, Netdiag and DNSDiag and we're clean, good replication and no errors. All machines can ping each other cross domain via ip and unc. We've also checked our FSMO roles for each DC and they were configured as recommended by MS (as to what I remember I did about 2 years ago or so). I am attaching a report of our 7 DC's and their FSMO roles (no worries, domain name changed to protect the innocent).
Our DHCP server scope options are configured to assign the 1st DNS IP to workstations/servers of the DC within their domain/child followed by the other 3 IP addresses of the DC's from our main office which includes the co-lo DC. My understanding is that if the 1st DNS is not available the workstation/server should then find the IP address that is next in line and try to resolve through that one. Am I correct?
All the servers except for the co-lo is a global catalog server.
Hope I explained as much as I could.
Thank you for reading,
ceez