Good Day,
I have inherited support for a small network where the external and internal domain names are the same. The external domain is hosted off site.
For purposes of illustration the external domain name is diddywap.org and the internal domain name is diddywap.org.
To complicate things further there are two locations, each with its own domain server in a configuration we used to call PDC/BDC in an NT network but I guess they just call them Domain servers now, joined by a VPN. The two locations also have Internet access.
I think the external domain and internal domain name being the same is causing problems for authentication and replication. At times users cannot authenticate to the Domain and at other times it's no problem (this seems to be random) and File and Security Replication between the two sites is not working at all.
What can I do to configure these two domain servers so the external domain doesn't get into the mix?
ChrisK
I have inherited support for a small network where the external and internal domain names are the same. The external domain is hosted off site.
For purposes of illustration the external domain name is diddywap.org and the internal domain name is diddywap.org.
To complicate things further there are two locations, each with its own domain server in a configuration we used to call PDC/BDC in an NT network but I guess they just call them Domain servers now, joined by a VPN. The two locations also have Internet access.
I think the external domain and internal domain name being the same is causing problems for authentication and replication. At times users cannot authenticate to the Domain and at other times it's no problem (this seems to be random) and File and Security Replication between the two sites is not working at all.
What can I do to configure these two domain servers so the external domain doesn't get into the mix?
ChrisK