Replication problem

Guest · Posted: Tue May 16, 2006 2:06 am Post subject: Replication problem

Customer has a 2003 small business server as the root of the forest and
has added an Enterprise edition 2003 server and a standard 2003 server
as additional domain controllers. I didn't think that you could have
additional domain controllers with a small business server, but after
researching it, apparently you can. The rules as I understand it are
that there can only be one small business server and it has to be the
root of the forest and hold all of the FSMO roles, but other servers
including other domain controllers can be added. Anyway my problem is
that the 2003 standard server is not replicating properly. I have
installed the support tools and used replmon.exe to see the replication
status. It appears the 2003 standard server is replicating fine with
the 2003 Enterprise server but not with the Small Business Server. It
gives me this as the reason for failing "Logon Failure: The target
account name is incorrect." During the past few weeks we changed the
admin password but replmon says that this particular server hasn't
replicated properly in the past few months. Also, nslookup fails to see
the Small Business Server. I'm fairly certain this is a DNS issue but
the 2003 Standar Server has multiple IP's bound to a bridged NIC and
I'm still in the process of trying to sort out what is going on in this
network. However, I would like to get this problem taken care of and
any help is appreciated.

Thanks,
Josh

akeiii · Guest

It may be a name resolution issue. Check both DNS and WINS, if the
Enterprise system is replicating and the standard is not then I would compare
the results of ipconfig /all between the two systems. If that does not point
out the problem try deleting the AD connection and let it re-generate to see
if that fixes the problem. Also check the nslookup answer for the domain
name. Does nslookup return the same answer for the server name as it does
for the fully qualfied server name ("server.domain.com")?

"josh.katie.jordan@gmail.com" wrote:

Guest · Posted: Tue May 16, 2006 2:43 am Post subject: Re: Replication problem

Thanks, I will try that when I am onsite tomorrow. But when you say
delete the AD connection and regenerate it, I'm sure I understand what
you mean or how to do that. Are you referring to demoting the DC and
and removing it from the domain and then rejoining?

akeiii · Guest

I am not referring to demoting the DC. Open Active Directory Sites and
Services. Under Default-First-Site-Name\Servers find the server name and
under that you will find NTDS Settings, in NTDS Settings you should find an
"<automatically generated>" entry of type "Connection", that is the entry I
am referring to.

"josh.katie.jordan@gmail.com" wrote:

Guest · Posted: Tue May 16, 2006 10:17 pm Post subject: Re: Replication problem

I deleted the connection from the 2003 standard server to the small
business server in the NTDS settings. However, I noticed that on the
small business server, there isn't anything listed in the NTDS
setttings, whereas the other machines show the small business server
and the 2 2003 servers.

akeiii wrote:

akeiii · Guest

Question: After you deleted the connection did it automatically regenerate?

If the NTDS connections are not automaticlly generated on the SBS server
then you maybe able to resolve the replication problem by manually creating
the connections on the SBS server. Are the two other servers listed on the
SBS server? If they are then under the NTDS Settings for each server
manually create a new Active Directory Connection. After you create the
connections check them by doing a "Check Replication Topology" on each.

"josh.katie.jordan@gmail.com" wrote: