troubleshooting Question

Windows 2003 Secondary DC unable to communicate AD with FMSO DC at other end of WAN

Avatar of mberryaz
mberryaz asked on
ExchangeWindows Server 2003Active Directory
24 Comments1 Solution232 ViewsLast Modified:
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
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 24 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 24 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros