R
Rodney
Hello,
I got sort of a weird problem. The scenario is this, we
have 3 W2K AD servers, 1 of those is also our exchange
server. The other two do DNS. We had a problem with the
DNS on one of our servers, this lead to some replication
problems. I was able to correct the DNS and get
everything to work minus the exchange server.
Now comes the strange part, I can go to either of the
other servers and force them to replicate with the
exchange server, but for some reason it will not replicate
with one of the others, let's call it server A. But from
server A i can replicate to it. From the replication
monitor when I try to force sync, it gives me a DNS lookup
error. And when I go to the exchange server and look at
the event viewer, it gives me the following:
Event 9239 MSExchangeSA
Referal Interface found duplicate MSExchangeServer objects
with legacy ExchangeDN in Active Directory.
I looked through the knowledge base but I can't find
anything. Does anyone have any suggestions, this is
problematic since I work off that exchange server alot.
I got sort of a weird problem. The scenario is this, we
have 3 W2K AD servers, 1 of those is also our exchange
server. The other two do DNS. We had a problem with the
DNS on one of our servers, this lead to some replication
problems. I was able to correct the DNS and get
everything to work minus the exchange server.
Now comes the strange part, I can go to either of the
other servers and force them to replicate with the
exchange server, but for some reason it will not replicate
with one of the others, let's call it server A. But from
server A i can replicate to it. From the replication
monitor when I try to force sync, it gives me a DNS lookup
error. And when I go to the exchange server and look at
the event viewer, it gives me the following:
Event 9239 MSExchangeSA
Referal Interface found duplicate MSExchangeServer objects
with legacy ExchangeDN in Active Directory.
I looked through the knowledge base but I can't find
anything. Does anyone have any suggestions, this is
problematic since I work off that exchange server alot.