Link to home
Start Free TrialLog in
Avatar of mberryaz

asked on

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 ( and when I ping DC1 using fully qual name ( it shows correct address, which reflects DNS Server entry, but if I PING DC1 with just host name (DC1) it shows which is incorrect.  I have checked host files and they do not show that address.
I get several errors in the event log
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
Avatar of Manpreet SIngh Khatra
Manpreet SIngh Khatra
Flag of India image

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
Avatar of mberryaz


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'.
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 ?

Ensure the EDS and EES groups are in default Users conatiner
Also you can try to run /domainprep

- Rancy
no, the domain was not renamed
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.
Any extra NIC?
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
yes, there are two NICs
ok run ipconfig /all | more and post here.
the second ID on NIC is not registered in DNS (it had been removed years ago)
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 !!!
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
Computer Browser service is running, i might suggest to do a reboot
Computer browser running, I've rebooted several times
Is the DC with FSMO roles not contactable or not on the same site as Exchange ?

- Rancy
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 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
because I need the Server at the other site to hold those roles
Avatar of Leon Fester
Leon Fester
Flag of South Africa image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
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:
Check AD partition status from replmon