1 domaine - 3 sites - 4 DC Win2k3, mode 2000 natif. (Sur Site1 j'ai 2 DC) .
Tous ces DC (sauf "Site3Server1"...il était déjà à 2k3) ont été migré à 2003
depuis les 6 derniers mois. La réplication se fait très bien, ils sont tous
DNS et aucun serveur ne génère d'erreurs de réplication/DNS/system. Si je
fais des changements dans AD sur n'importe quel site le changement est
répliqué sur mes 4 DC. Par routine, j'ai fait un dcdiag sur l'un d'entre eux
et j'obtiens le résultat suivant :
_________________
Running enterprise tests on : domaine.com
Starting test: Intersite
Doing intersite inbound replication test on site Site1:
Locating & Contacting Intersite Topology Generator (ISTG) ...
*Warning: ISTG time stamp is 70163 minutes old on Site1Server1.
Looking for a new ISTG.
*Warning: The next ISTG could not be authoratively determined
for site Site1. A DC should make an ISTG failover attempt in 23 minutes.
* Warning: Current ISTG failed, ISTG role should be taken by
Site1Server2 in 23 minutes.
Checking for down bridgeheads ...
Bridghead Site3\Site3Server1 is up and replicating fine.
Bridghead Site1\Site1Server1 is up and replicating fine.
Bridghead Site2\Site2Server1 is up and replicating fine.
Doing in depth site analysis ...
All expected sites and bridgeheads are replicating into site
Site1.
Doing intersite inbound replication test on site Site2:
Locating & Contacting Intersite Topology Generator (ISTG) ...
*Warning: ISTG time stamp is 1204 minutes old on Site2Server1.
Looking for a new ISTG.
***Error: The current ISTG is down in site Site2 and further
dcdiag could not contact any other servers in the site that
could take the ISTG role. Ensure there is at least one up DC.
Must abandon inbound intersite replication test for this site.
*Warning: Could not locate the next ISTG or site Site2.
Using the last known ISTG Site2Server1 as the ISTG.
The ISTG for site Site2 is: Site2Server1.
Checking for down bridgeheads ...
Bridghead Site1\Site1Server1 is up and replicating fine.
Bridghead Site2\Site2Server1 is up and replicating fine.
Bridghead Site3\Site3Server1 is up and replicating fine.
Doing in depth site analysis ...
All expected sites and bridgeheads are replicating into site
Site2.
Doing intersite inbound replication test on site Site3:
Locating & Contacting Intersite Topology Generator (ISTG) ...
*Warning: ISTG time stamp is 1593682 minutes old on Site3Server1.
Looking for a new ISTG.
***Error: The current ISTG is down in site Site3 and further
dcdiag could not contact any other servers in the site that
could take the ISTG role. Ensure there is at least one up DC.
Must abandon inbound intersite replication test for this site.
*Warning: Could not locate the next ISTG or site Site3.
Using the
last known ISTG Site3Server1 as the ISTG.
The ISTG for site Site3 is: Site3Server1.
Checking for down bridgeheads ...
Bridghead Site1\Site1Server1 is up and replicating fine.
Bridghead Site3\Site3Server1 is up and replicating fine.
Bridghead Site2\Site2Server1 is up and replicating fine.
Doing in depth site analysis ...
All expected sites and bridgeheads are replicating into site
Site3.
......................... domaine.com passed test Intersite
______________________
Je ne comprends pas. Surtout qu'il dit "passed test intersite" ...
Et si je vais dans AD sites & services, sur chaque site, dans NTDS site
settings properties, le "Inter-Site topology generator" porte bien le nom du
bridgehead pour ce site. Par contre plus bas dans ce même écran j'ai
l'avertissement suivant :
"Auto-generation of Active Directory replication topology between this site
and other sites is disabled."
Quelqu'un pourrait m'éclairer? Il y a quelque chose que j'ai dû louper...
Cette action est irreversible, confirmez la suppression du commentaire ?
Signaler le commentaire
Veuillez sélectionner un problème
Nudité
Violence
Harcèlement
Fraude
Vente illégale
Discours haineux
Terrorisme
Autre
JF
J'ai trouvé. Dans adsiedit.msc dans "NTDS site settings" de mes sites il y a l'attribut options. Il avait la valeur 16, ce qui signifie de désactiver le ISTG. En effaçant cette valeur sur chacun de mes sites tous les messages d'erreur de DCDiag disparaissent et la synchro de la topologie se fait à nouveau.
Trouvé sur http://support.microsoft.com/kb/242780/en-us
JF
"JF" wrote:
Bonjour,
1 domaine - 3 sites - 4 DC Win2k3, mode 2000 natif. (Sur Site1 j'ai 2 DC) . Tous ces DC (sauf "Site3Server1"...il était déjà à 2k3) ont été migré à 2003 depuis les 6 derniers mois. La réplication se fait très bien, ils sont tous DNS et aucun serveur ne génère d'erreurs de réplication/DNS/system. Si je fais des changements dans AD sur n'importe quel site le changement est répliqué sur mes 4 DC. Par routine, j'ai fait un dcdiag sur l'un d'entre eux et j'obtiens le résultat suivant : _________________ Running enterprise tests on : domaine.com Starting test: Intersite Doing intersite inbound replication test on site Site1: Locating & Contacting Intersite Topology Generator (ISTG) ... *Warning: ISTG time stamp is 70163 minutes old on Site1Server1. Looking for a new ISTG. *Warning: The next ISTG could not be authoratively determined for site Site1. A DC should make an ISTG failover attempt in 23 minutes. * Warning: Current ISTG failed, ISTG role should be taken by Site1Server2 in 23 minutes. Checking for down bridgeheads ... Bridghead Site3Site3Server1 is up and replicating fine. Bridghead Site1Site1Server1 is up and replicating fine. Bridghead Site2Site2Server1 is up and replicating fine. Doing in depth site analysis ... All expected sites and bridgeheads are replicating into site Site1.
Doing intersite inbound replication test on site Site2: Locating & Contacting Intersite Topology Generator (ISTG) ... *Warning: ISTG time stamp is 1204 minutes old on Site2Server1. Looking for a new ISTG. ***Error: The current ISTG is down in site Site2 and further dcdiag could not contact any other servers in the site that could take the ISTG role. Ensure there is at least one up DC. Must abandon inbound intersite replication test for this site. *Warning: Could not locate the next ISTG or site Site2. Using the last known ISTG Site2Server1 as the ISTG. The ISTG for site Site2 is: Site2Server1. Checking for down bridgeheads ... Bridghead Site1Site1Server1 is up and replicating fine. Bridghead Site2Site2Server1 is up and replicating fine. Bridghead Site3Site3Server1 is up and replicating fine. Doing in depth site analysis ... All expected sites and bridgeheads are replicating into site Site2.
Doing intersite inbound replication test on site Site3: Locating & Contacting Intersite Topology Generator (ISTG) ... *Warning: ISTG time stamp is 1593682 minutes old on Site3Server1. Looking for a new ISTG. ***Error: The current ISTG is down in site Site3 and further dcdiag could not contact any other servers in the site that could take the ISTG role. Ensure there is at least one up DC. Must abandon inbound intersite replication test for this site. *Warning: Could not locate the next ISTG or site Site3. Using the last known ISTG Site3Server1 as the ISTG. The ISTG for site Site3 is: Site3Server1. Checking for down bridgeheads ... Bridghead Site1Site1Server1 is up and replicating fine. Bridghead Site3Site3Server1 is up and replicating fine. Bridghead Site2Site2Server1 is up and replicating fine. Doing in depth site analysis ... All expected sites and bridgeheads are replicating into site Site3. ......................... domaine.com passed test Intersite
______________________
Je ne comprends pas. Surtout qu'il dit "passed test intersite" ...
Et si je vais dans AD sites & services, sur chaque site, dans NTDS site settings properties, le "Inter-Site topology generator" porte bien le nom du bridgehead pour ce site. Par contre plus bas dans ce même écran j'ai l'avertissement suivant :
"Auto-generation of Active Directory replication topology between this site and other sites is disabled."
Quelqu'un pourrait m'éclairer? Il y a quelque chose que j'ai dû louper...
Merci à l'avance
JF
J'ai trouvé. Dans adsiedit.msc dans "NTDS site settings" de mes sites il y a
l'attribut options. Il avait la valeur 16, ce qui signifie de désactiver le
ISTG. En effaçant cette valeur sur chacun de mes sites tous les messages
d'erreur de DCDiag disparaissent et la synchro de la topologie se fait à
nouveau.
Trouvé sur http://support.microsoft.com/kb/242780/en-us
JF
"JF" wrote:
Bonjour,
1 domaine - 3 sites - 4 DC Win2k3, mode 2000 natif. (Sur Site1 j'ai 2 DC) .
Tous ces DC (sauf "Site3Server1"...il était déjà à 2k3) ont été migré à 2003
depuis les 6 derniers mois. La réplication se fait très bien, ils sont tous
DNS et aucun serveur ne génère d'erreurs de réplication/DNS/system. Si je
fais des changements dans AD sur n'importe quel site le changement est
répliqué sur mes 4 DC. Par routine, j'ai fait un dcdiag sur l'un d'entre eux
et j'obtiens le résultat suivant :
_________________
Running enterprise tests on : domaine.com
Starting test: Intersite
Doing intersite inbound replication test on site Site1:
Locating & Contacting Intersite Topology Generator (ISTG) ...
*Warning: ISTG time stamp is 70163 minutes old on Site1Server1.
Looking for a new ISTG.
*Warning: The next ISTG could not be authoratively determined
for site Site1. A DC should make an ISTG failover attempt in 23 minutes.
* Warning: Current ISTG failed, ISTG role should be taken by
Site1Server2 in 23 minutes.
Checking for down bridgeheads ...
Bridghead Site3Site3Server1 is up and replicating fine.
Bridghead Site1Site1Server1 is up and replicating fine.
Bridghead Site2Site2Server1 is up and replicating fine.
Doing in depth site analysis ...
All expected sites and bridgeheads are replicating into site
Site1.
Doing intersite inbound replication test on site Site2:
Locating & Contacting Intersite Topology Generator (ISTG) ...
*Warning: ISTG time stamp is 1204 minutes old on Site2Server1.
Looking for a new ISTG.
***Error: The current ISTG is down in site Site2 and further
dcdiag could not contact any other servers in the site that
could take the ISTG role. Ensure there is at least one up DC.
Must abandon inbound intersite replication test for this site.
*Warning: Could not locate the next ISTG or site Site2.
Using the last known ISTG Site2Server1 as the ISTG.
The ISTG for site Site2 is: Site2Server1.
Checking for down bridgeheads ...
Bridghead Site1Site1Server1 is up and replicating fine.
Bridghead Site2Site2Server1 is up and replicating fine.
Bridghead Site3Site3Server1 is up and replicating fine.
Doing in depth site analysis ...
All expected sites and bridgeheads are replicating into site
Site2.
Doing intersite inbound replication test on site Site3:
Locating & Contacting Intersite Topology Generator (ISTG) ...
*Warning: ISTG time stamp is 1593682 minutes old on Site3Server1.
Looking for a new ISTG.
***Error: The current ISTG is down in site Site3 and further
dcdiag could not contact any other servers in the site that
could take the ISTG role. Ensure there is at least one up DC.
Must abandon inbound intersite replication test for this site.
*Warning: Could not locate the next ISTG or site Site3.
Using the
last known ISTG Site3Server1 as the ISTG.
The ISTG for site Site3 is: Site3Server1.
Checking for down bridgeheads ...
Bridghead Site1Site1Server1 is up and replicating fine.
Bridghead Site3Site3Server1 is up and replicating fine.
Bridghead Site2Site2Server1 is up and replicating fine.
Doing in depth site analysis ...
All expected sites and bridgeheads are replicating into site
Site3.
......................... domaine.com passed test Intersite
______________________
Je ne comprends pas. Surtout qu'il dit "passed test intersite" ...
Et si je vais dans AD sites & services, sur chaque site, dans NTDS site
settings properties, le "Inter-Site topology generator" porte bien le nom du
bridgehead pour ce site. Par contre plus bas dans ce même écran j'ai
l'avertissement suivant :
"Auto-generation of Active Directory replication topology between this site
and other sites is disabled."
Quelqu'un pourrait m'éclairer? Il y a quelque chose que j'ai dû louper...
J'ai trouvé. Dans adsiedit.msc dans "NTDS site settings" de mes sites il y a l'attribut options. Il avait la valeur 16, ce qui signifie de désactiver le ISTG. En effaçant cette valeur sur chacun de mes sites tous les messages d'erreur de DCDiag disparaissent et la synchro de la topologie se fait à nouveau.
Trouvé sur http://support.microsoft.com/kb/242780/en-us
JF
"JF" wrote:
Bonjour,
1 domaine - 3 sites - 4 DC Win2k3, mode 2000 natif. (Sur Site1 j'ai 2 DC) . Tous ces DC (sauf "Site3Server1"...il était déjà à 2k3) ont été migré à 2003 depuis les 6 derniers mois. La réplication se fait très bien, ils sont tous DNS et aucun serveur ne génère d'erreurs de réplication/DNS/system. Si je fais des changements dans AD sur n'importe quel site le changement est répliqué sur mes 4 DC. Par routine, j'ai fait un dcdiag sur l'un d'entre eux et j'obtiens le résultat suivant : _________________ Running enterprise tests on : domaine.com Starting test: Intersite Doing intersite inbound replication test on site Site1: Locating & Contacting Intersite Topology Generator (ISTG) ... *Warning: ISTG time stamp is 70163 minutes old on Site1Server1. Looking for a new ISTG. *Warning: The next ISTG could not be authoratively determined for site Site1. A DC should make an ISTG failover attempt in 23 minutes. * Warning: Current ISTG failed, ISTG role should be taken by Site1Server2 in 23 minutes. Checking for down bridgeheads ... Bridghead Site3Site3Server1 is up and replicating fine. Bridghead Site1Site1Server1 is up and replicating fine. Bridghead Site2Site2Server1 is up and replicating fine. Doing in depth site analysis ... All expected sites and bridgeheads are replicating into site Site1.
Doing intersite inbound replication test on site Site2: Locating & Contacting Intersite Topology Generator (ISTG) ... *Warning: ISTG time stamp is 1204 minutes old on Site2Server1. Looking for a new ISTG. ***Error: The current ISTG is down in site Site2 and further dcdiag could not contact any other servers in the site that could take the ISTG role. Ensure there is at least one up DC. Must abandon inbound intersite replication test for this site. *Warning: Could not locate the next ISTG or site Site2. Using the last known ISTG Site2Server1 as the ISTG. The ISTG for site Site2 is: Site2Server1. Checking for down bridgeheads ... Bridghead Site1Site1Server1 is up and replicating fine. Bridghead Site2Site2Server1 is up and replicating fine. Bridghead Site3Site3Server1 is up and replicating fine. Doing in depth site analysis ... All expected sites and bridgeheads are replicating into site Site2.
Doing intersite inbound replication test on site Site3: Locating & Contacting Intersite Topology Generator (ISTG) ... *Warning: ISTG time stamp is 1593682 minutes old on Site3Server1. Looking for a new ISTG. ***Error: The current ISTG is down in site Site3 and further dcdiag could not contact any other servers in the site that could take the ISTG role. Ensure there is at least one up DC. Must abandon inbound intersite replication test for this site. *Warning: Could not locate the next ISTG or site Site3. Using the last known ISTG Site3Server1 as the ISTG. The ISTG for site Site3 is: Site3Server1. Checking for down bridgeheads ... Bridghead Site1Site1Server1 is up and replicating fine. Bridghead Site3Site3Server1 is up and replicating fine. Bridghead Site2Site2Server1 is up and replicating fine. Doing in depth site analysis ... All expected sites and bridgeheads are replicating into site Site3. ......................... domaine.com passed test Intersite
______________________
Je ne comprends pas. Surtout qu'il dit "passed test intersite" ...
Et si je vais dans AD sites & services, sur chaque site, dans NTDS site settings properties, le "Inter-Site topology generator" porte bien le nom du bridgehead pour ce site. Par contre plus bas dans ce même écran j'ai l'avertissement suivant :
"Auto-generation of Active Directory replication topology between this site and other sites is disabled."
Quelqu'un pourrait m'éclairer? Il y a quelque chose que j'ai dû louper...
