Liste d'adresses globales Exch & DNS : pb de MÃ j de la liste.
Le
sbo

Bonjour,
Mes clients Outlook lorsqu'ils cliquent sur 'A' obtiennent une liste
d'adresses globales obsolète; l'aperçu depuis le serveur Exchange
présente en revanche une liste à jour, celle que j'aimerais que tous
mes utilisateurs voient.
Comment se fait-il que Outlook utilise une liste obsolète et que le
serveur Exchange quant à lui me donne à voir une liste à jour (avec
toutes les modifications récentes demandées) ?
Est-ce une liste en cache à défaut de ne pouvoir atteindre celle du
serveur ? Chose plus étrange encore, ce matin en déployant un Outlook
2003, la liste du serveur donc correcte est apparue quelques minutes,
puis a disparu au profit de celle obsolète ???
Après une brève recherche, il semble que mon DNS soit en cause; et il
est vrai qu'il n'est pas au mieux de sa forme; voici ce que retourne
un
> cdgiad /text:dns
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Premier-Site-par-defautW2K-SRV-13
Starting test: Connectivity
. W2K-SRV-13 passed test Connectivity
Doing primary tests
Testing server: Premier-Site-par-defautW2K-SRV-13
DNS Tests are running and not hung. Please wait a few minutes
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : mondomaine
Running enterprise tests on : mondomaine.lan
Starting test: DNS
Test results for domain controllers:
DC: w2k-srv-13.tajan.org
Domain: mondomaine.lan
TEST: Forwarders/Root hints (Forw)
Error: Root hints list has invalid root hint server:
a.root-se
rvers.net. (198.41.0.4)
Error: Root hints list has invalid root hint server:
c.root-se
rvers.net. (192.33.4.12)
Error: Root hints list has invalid root hint server:
d.root-se
rvers.net. (128.8.10.90)
Error: Root hints list has invalid root hint server:
e.root-se
rvers.net. (192.203.230.10)
Error: Root hints list has invalid root hint server:
f.root-se
rvers.net. (192.5.5.241)
Error: Root hints list has invalid root hint server:
g.root-se
rvers.net. (192.112.36.4)
Error: Root hints list has invalid root hint server:
h.root-se
rvers.net. (128.63.2.53)
Error: Root hints list has invalid root hint server:
i.root-se
rvers.net. (192.36.148.17)
Error: Root hints list has invalid root hint server:
j.root-se
rvers.net. (192.58.128.30)
Error: Root hints list has invalid root hint server:
k.root-se
rvers.net. (193.0.14.129)
Error: Root hints list has invalid root hint server:
l.root-se
rvers.net. (198.32.64.12)
Error: Root hints list has invalid root hint server:
m.root-se
rvers.net. (202.12.27.33)
Summary of test results for DNS servers used by the above
domain contro
llers:
DNS server: 128.63.2.53 (h.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 128.63.2.53
DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 128.8.10.90
DNS server: 192.112.36.4 (g.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.112.36.4
DNS server: 192.203.230.10 (e.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.203.230.10
DNS server: 192.33.4.12 (c.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.33.4.12
DNS server: 192.36.148.17 (i.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.36.148.17
DNS server: 192.5.5.241 (f.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.5.5.241
DNS server: 192.58.128.30 (j.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.58.128.30
DNS server: 193.0.14.129 (k.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 193.0.14.129
DNS server: 198.32.64.12 (l.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 198.32.64.12
DNS server: 198.41.0.4 (a.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 198.41.0.4
DNS server: 202.12.27.33 (m.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 202.12.27.33
. mondomaine.lan passed test DNS
Je précise exploiter 3 contrôleurs de domaine.
Ce test a été lancé sur le contrôleur principale de domaine.
PDC : Windows 2003 Server
BDC1 : Windows 2000 Server
BDC2 : Windows 2000 Server
Mes clients Outlook lorsqu'ils cliquent sur 'A' obtiennent une liste
d'adresses globales obsolète; l'aperçu depuis le serveur Exchange
présente en revanche une liste à jour, celle que j'aimerais que tous
mes utilisateurs voient.
Comment se fait-il que Outlook utilise une liste obsolète et que le
serveur Exchange quant à lui me donne à voir une liste à jour (avec
toutes les modifications récentes demandées) ?
Est-ce une liste en cache à défaut de ne pouvoir atteindre celle du
serveur ? Chose plus étrange encore, ce matin en déployant un Outlook
2003, la liste du serveur donc correcte est apparue quelques minutes,
puis a disparu au profit de celle obsolète ???
Après une brève recherche, il semble que mon DNS soit en cause; et il
est vrai qu'il n'est pas au mieux de sa forme; voici ce que retourne
un
> cdgiad /text:dns
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Premier-Site-par-defautW2K-SRV-13
Starting test: Connectivity
. W2K-SRV-13 passed test Connectivity
Doing primary tests
Testing server: Premier-Site-par-defautW2K-SRV-13
DNS Tests are running and not hung. Please wait a few minutes
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : mondomaine
Running enterprise tests on : mondomaine.lan
Starting test: DNS
Test results for domain controllers:
DC: w2k-srv-13.tajan.org
Domain: mondomaine.lan
TEST: Forwarders/Root hints (Forw)
Error: Root hints list has invalid root hint server:
a.root-se
rvers.net. (198.41.0.4)
Error: Root hints list has invalid root hint server:
c.root-se
rvers.net. (192.33.4.12)
Error: Root hints list has invalid root hint server:
d.root-se
rvers.net. (128.8.10.90)
Error: Root hints list has invalid root hint server:
e.root-se
rvers.net. (192.203.230.10)
Error: Root hints list has invalid root hint server:
f.root-se
rvers.net. (192.5.5.241)
Error: Root hints list has invalid root hint server:
g.root-se
rvers.net. (192.112.36.4)
Error: Root hints list has invalid root hint server:
h.root-se
rvers.net. (128.63.2.53)
Error: Root hints list has invalid root hint server:
i.root-se
rvers.net. (192.36.148.17)
Error: Root hints list has invalid root hint server:
j.root-se
rvers.net. (192.58.128.30)
Error: Root hints list has invalid root hint server:
k.root-se
rvers.net. (193.0.14.129)
Error: Root hints list has invalid root hint server:
l.root-se
rvers.net. (198.32.64.12)
Error: Root hints list has invalid root hint server:
m.root-se
rvers.net. (202.12.27.33)
Summary of test results for DNS servers used by the above
domain contro
llers:
DNS server: 128.63.2.53 (h.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 128.63.2.53
DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 128.8.10.90
DNS server: 192.112.36.4 (g.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.112.36.4
DNS server: 192.203.230.10 (e.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.203.230.10
DNS server: 192.33.4.12 (c.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.33.4.12
DNS server: 192.36.148.17 (i.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.36.148.17
DNS server: 192.5.5.241 (f.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.5.5.241
DNS server: 192.58.128.30 (j.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.58.128.30
DNS server: 193.0.14.129 (k.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 193.0.14.129
DNS server: 198.32.64.12 (l.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 198.32.64.12
DNS server: 198.41.0.4 (a.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 198.41.0.4
DNS server: 202.12.27.33 (m.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 202.12.27.33
. mondomaine.lan passed test DNS
Je précise exploiter 3 contrôleurs de domaine.
Ce test a été lancé sur le contrôleur principale de domaine.
PDC : Windows 2003 Server
BDC1 : Windows 2000 Server
BDC2 : Windows 2000 Server
je ne pense pas que les DNS soient en cause !
Le plus probable est que la liste d'adresse "en mode autonome" préparée par
le serveur Exchange ne soit pas à jour.
=> C'est celle-ci que Outlook 2003 utilise dans son cache pour éviter
d'interroger systématiquement Exchange ou le catalogue global.
Vérifier et forcer la génération de cette liste en mode autonome.
Forcer la synchronisation de cette liste sur le poste client.
A bientôt,
--
Thierry DEMAN-BARCELÒ
(@ MVP Summit Seattle )
MVP Exchange, SQL/Server
http://base.faqexchange.info http://www.faqexchange.info
http://ISAFirewalls.org
"sbo" news:
Bonjour,
Mes clients Outlook lorsqu'ils cliquent sur 'A' obtiennent une liste
d'adresses globales obsolète; l'aperçu depuis le serveur Exchange
présente en revanche une liste à jour, celle que j'aimerais que tous
mes utilisateurs voient.
Comment se fait-il que Outlook utilise une liste obsolète et que le
serveur Exchange quant à lui me donne à voir une liste à jour (avec
toutes les modifications récentes demandées) ?
Est-ce une liste en cache à défaut de ne pouvoir atteindre celle du
serveur ? Chose plus étrange encore, ce matin en déployant un Outlook
2003, la liste du serveur donc correcte est apparue quelques minutes,
puis a disparu au profit de celle obsolète ???
Après une brève recherche, il semble que mon DNS soit en cause; et il
est vrai qu'il n'est pas au mieux de sa forme; voici ce que retourne
un ...
---
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Premier-Site-par-defautW2K-SRV-13
Starting test: Connectivity
......................... W2K-SRV-13 passed test Connectivity
Doing primary tests
Testing server: Premier-Site-par-defautW2K-SRV-13
DNS Tests are running and not hung. Please wait a few minutes...
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : mondomaine
Running enterprise tests on : mondomaine.lan
Starting test: DNS
Test results for domain controllers:
DC: w2k-srv-13.tajan.org
Domain: mondomaine.lan
TEST: Forwarders/Root hints (Forw)
Error: Root hints list has invalid root hint server:
a.root-se
rvers.net. (198.41.0.4)
Error: Root hints list has invalid root hint server:
c.root-se
rvers.net. (192.33.4.12)
Error: Root hints list has invalid root hint server:
d.root-se
rvers.net. (128.8.10.90)
Error: Root hints list has invalid root hint server:
e.root-se
rvers.net. (192.203.230.10)
Error: Root hints list has invalid root hint server:
f.root-se
rvers.net. (192.5.5.241)
Error: Root hints list has invalid root hint server:
g.root-se
rvers.net. (192.112.36.4)
Error: Root hints list has invalid root hint server:
h.root-se
rvers.net. (128.63.2.53)
Error: Root hints list has invalid root hint server:
i.root-se
rvers.net. (192.36.148.17)
Error: Root hints list has invalid root hint server:
j.root-se
rvers.net. (192.58.128.30)
Error: Root hints list has invalid root hint server:
k.root-se
rvers.net. (193.0.14.129)
Error: Root hints list has invalid root hint server:
l.root-se
rvers.net. (198.32.64.12)
Error: Root hints list has invalid root hint server:
m.root-se
rvers.net. (202.12.27.33)
Summary of test results for DNS servers used by the above
domain contro
llers:
DNS server: 128.63.2.53 (h.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 128.63.2.53
DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 128.8.10.90
DNS server: 192.112.36.4 (g.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.112.36.4
DNS server: 192.203.230.10 (e.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.203.230.10
DNS server: 192.33.4.12 (c.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.33.4.12
DNS server: 192.36.148.17 (i.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.36.148.17
DNS server: 192.5.5.241 (f.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.5.5.241
DNS server: 192.58.128.30 (j.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 192.58.128.30
DNS server: 193.0.14.129 (k.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 193.0.14.129
DNS server: 198.32.64.12 (l.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 198.32.64.12
DNS server: 198.41.0.4 (a.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 198.41.0.4
DNS server: 202.12.27.33 (m.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for
the 1.0.0.12
7.in-addr.arpa. failed on the DNS server 202.12.27.33
......................... mondomaine.lan passed test DNS
---
Je précise exploiter 3 contrôleurs de domaine.
Ce test a été lancé sur le contrôleur principale de domaine.
PDC : Windows 2003 Server
BDC1 : Windows 2000 Server
BDC2 : Windows 2000 Server
Vous avez probablement raison; j'ai "assaini" les DNS, validé la bonne
marche de la réplication de l'AD; tout est OK.
En revanche, la liste d'adresses globales demeure obsolète sur les
clients.
Je tente de suivre votre conseil et vous tiens ici informé.
Merci, Stéphane.
On 12 mar, 05:59, "Thierry DEMAN [MVP]" wrote: