If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.
Windows 2003 Secondary DC unable to communicate AD with FMSO DC at other end of WAN
I have a Windows 2003 Secondary DC located in office 2 it also runs Exchange 2003. Since yesterday it cannot provide shares for users and cannot replicate with DC1 at office 1. I can communicate with server via ip address (192.168.2.11) and when I ping DC1 using fully qual name (dc1.domain.com) it shows correct address, which reflects DNS Server entry, but if I PING DC1 with just host name (DC1) it shows 192.168.2.119 which is incorrect. I have checked host files and they do not show that address.
I get several errors in the event log
NTDS KCC 1865
NTDS KCC 1311
multiple KERBEROS 4 events
Userenv 1006 (Windows cannot bind to domain)
This problem is also causing a problem for Exchange System Attendant Service to start, causing Exchange not to function
I get several errors in the event log
NTDS KCC 1865
NTDS KCC 1311
multiple KERBEROS 4 events
Userenv 1006 (Windows cannot bind to domain)
This problem is also causing a problem for Exchange System Attendant Service to start, causing Exchange not to function
Asked:
Who is Participating?
If SA isnt starting what is the error for SA you get in EVent logs ?
How Many DC's are in the local Site for Exchange ?
- Rancy
How Many DC's are in the local Site for Exchange ?
- Rancy
two sites each containing a DC, each site has global catalog
MSExchaneSA Event 9098 The MAD Monitoring thread was unable to read its configuration from the DS, error '0x80010002'.
MSExchaneSA Event 9098 The MAD Monitoring thread was unable to read its configuration from the DS, error '0x80010002'.
Do you have any secondary NIC on Office 2 DC, If so, check it might be got registered in DNS, that could be one reason for this issue.
Did you rename the Domain ?
http://support.microsoft.com/kb/327844
Ensure the EDS and EES groups are in default Users conatiner
Also you can try to run /domainprep
- Rancy
http://support.microsoft.com/kb/327844
Ensure the EDS and EES groups are in default Users conatiner
Also you can try to run /domainprep
- Rancy
Before you run /domainprep as suggested by Rancy, just run policytest.exe and check the result, if sesecurityprivilege shows not found on office 2 dc, then domain prep is required to fix it.
I really do not believe that Exchange is the cause. I believe that there is a larger AD, DNS or Authentication issue which is the problem and Exchange is just a symptom. If the DC2 could correctly communicate and replicate with AD on DC1, I believe that Exchange SA will start
if I run policytest.exe from DC2 it shows
DC = "DC2"
In Site = "Phoenix"
Right found: "SeSecurityPrivelege"
DC = "DC1"
In Site = "Denver"
!! LSAOpenPolicy returned error 5 !!!
DC = "DC2"
In Site = "Phoenix"
Right found: "SeSecurityPrivelege"
DC = "DC1"
In Site = "Denver"
!! LSAOpenPolicy returned error 5 !!!
basically on all computers connecting to DC2 cannot access shares and on one RDP Windows 2008 server, users get authentication issues with trying to logon, since it attaches to that local DC. This cannot be just an exchange issue
anything you disabled recently, like ipv6 or firewall. check all automatic services are running on dc.
Microsoft .NET Framework NGEN v4.0.30319_X86
Microsoft Exchange System Attendant
Microsoft Exchange Information Store
those are not running
Microsoft Exchange System Attendant
Microsoft Exchange Information Store
those are not running
I can ping and access DC1 (the one with FMSO roles) and can access shares via IP address, but cannot access shares using host name \\DC1 I says "\\DC1 is not accessible. Logon Failure: The target account name is incorrect.
The name \\DC1 correctly resolves to IP address
The name \\DC1 correctly resolves to IP address
The reason i asked is if its a FSMO issue why not transfer the roles to DC2 and get Exchange running and then check whats the AD or DNS side issue
- Rancy
- Rancy
In your orginal post you stated that for two day's you haven't been able to access shares on DC1. Was anything changed on the server? Configuration, Windows updates, AV etc...
is the time on the server correct?
In DNS are all of the necessary AD DNS records in place?
When you view the sysvol/netlogon share on DC1 does it contain all of the same files and correct timestamps as the sysvol share on dc2?
Have you tried to install the MSBPA for AD to help troubleshoot the issue further: http://technet.microsoft.com/en-us/library/dd378893(v=ws.10).aspx
is the time on the server correct?
In DNS are all of the necessary AD DNS records in place?
When you view the sysvol/netlogon share on DC1 does it contain all of the same files and correct timestamps as the sysvol share on dc2?
Have you tried to install the MSBPA for AD to help troubleshoot the issue further: http://technet.microsoft.com/en-us/library/dd378893(v=ws.10).aspx
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.
All Courses
From novice to tech pro — start learning today.
It could very well be that your DC at the far side of the WAN is tombstoned.
Run the following commands on each DC to check the health and replication status.
dcdiag /c /v /f:dcdiag.txt - runs comprehensive ad tests and writes results to a log file. Upload the log file for further analysis.
repadmin /showrepl - shows the replication status and latest update times for all replication partners
repadmin /replsummary - shows the time offset of the most recent updates carried over by replication.
netdom query fsmo - returns the fsmo role holders that each DC knows about.
Not that it's makes a big difference, but I'm quite curious now...Can you also confirm the reason for "because I need the Server at the other site to hold those roles".
Note: I'm not suggesting that you transfer...just curious.