[Ivan Bardeen]

Cейчас там имена контролеров домена - верно ли это »

Наблюдаются какие-то проблемы с разрешением имен?
Как у вас настроено разрешение внешних имен?
Чем руководствовались назначив ваши контроллеры домена корневыми серверами пронстранства имен?

[exo]

В корневых ссылках »

вы про Root Hints ?

[Levin]

вы про Root Hints ? именно.

Имеются проблемы с репликацией внутри домена. Дело явно в ошибках настройки - я стал пытаться изменить. До этого там были сервера домена. И по форуму и по литературе очень туманно и невнятно то, что же должно быть в этом разделе и в разделе "пересылки(Forwardes)"

[Ivan Bardeen]

Имеются проблемы с репликацией внутри домена »

Вывод команды dcdiag /e покажите

[Levin]

Описка в первом посте - в корневых ссылках - адреса контролеров домена, а адреса провайдеров - в пересылках.

[exo]

вы про Root Hints ? именно. »

в корневых ссылках - адреса контролеров домена »

а зачем вы их вообще трогали ??? пусть там стоят стандартные. и всё.

что же должно быть в этом разделе и в разделе "пересылки(Forwardes)" »

а вот здесь - ДНС провайдера.

[Levin]

В результате моих манипуляций результат dcdiag стал еще ужасней! Вот он - запущен на Server-A - на нем все роли FSMO и CG.


Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SERVER-L
Starting test: Connectivity
The host 0e9ad78c-a9b2-4c38-a1ac-5329b3ff6424._msdcs.LMGTW-DOMAIN could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(0e9ad78c-a9b2-4c38-a1ac-5329b3ff6424._msdcs.LMGTW-DOMAIN) couldn't be

resolved, the server name (server-l.LMGTW-DOMAIN) resolved to the IP

address (192.168.1.5) and was pingable. Check that the IP address is

registered correctly with the DNS server.
......................... SERVER-L failed test Connectivity

Testing server: Default-First-Site-Name\SERVER-H
Starting test: Connectivity
The host 24968a4d-f9e8-4c91-90f1-095b1a09a875._msdcs.LMGTW-DOMAIN could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(24968a4d-f9e8-4c91-90f1-095b1a09a875._msdcs.LMGTW-DOMAIN) couldn't be

resolved, the server name (server-h.LMGTW-DOMAIN) resolved to the IP

address (192.168.2.4) and was pingable. Check that the IP address is

registered correctly with the DNS server.
......................... SERVER-H failed test Connectivity

Testing server: Default-First-Site-Name\SERVER-D
Starting test: Connectivity
The host 79b184b9-bc49-43f9-bb86-5bc73d62b26a._msdcs.LMGTW-DOMAIN could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(79b184b9-bc49-43f9-bb86-5bc73d62b26a._msdcs.LMGTW-DOMAIN) couldn't be

resolved, the server name (server-d.LMGTW-DOMAIN) resolved to the IP

address (192.168.3.3) and was pingable. Check that the IP address is

registered correctly with the DNS server.
......................... SERVER-D failed test Connectivity

Testing server: Default-First-Site-Name\SERVER-A
Starting test: Connectivity
The host f4c03cb0-2701-4796-b585-f0309d893ace._msdcs.LMGTW-DOMAIN could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(f4c03cb0-2701-4796-b585-f0309d893ace._msdcs.LMGTW-DOMAIN) couldn't be

resolved, the server name (server-a.LMGTW-DOMAIN) resolved to the IP

address (192.168.1.6) and was pingable. Check that the IP address is

registered correctly with the DNS server.
......................... SERVER-A failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\SERVER-L
Skipping all tests, because server SERVER-L is
not responding to directory service requests

Testing server: Default-First-Site-Name\SERVER-H
Skipping all tests, because server SERVER-H is
not responding to directory service requests

Testing server: Default-First-Site-Name\SERVER-D
Skipping all tests, because server SERVER-D is
not responding to directory service requests

Testing server: Default-First-Site-Name\SERVER-A
Skipping all tests, because server SERVER-A is
not responding to directory service requests

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
For the partition (DC=ForestDnsZones,DC=LMGTW-DOMAIN) we

encountered the following error retrieving the cross-ref's

(CN=2f0d3c6d-4fa6-4edf-8e7d-3dcd7c1513f7,CN=Partitions,CN=Configuration,DC=LMGTW-DOMAIN)

information:
LDAP Error 0x3a (58).
......................... ForestDnsZones failed test CrossRefValidation
Starting test: CheckSDRefDom
For the partition (DC=ForestDnsZones,DC=LMGTW-DOMAIN) we

encountered the following error retrieving the cross-ref's

(CN=2f0d3c6d-4fa6-4edf-8e7d-3dcd7c1513f7,CN=Partitions,CN=Configuration,DC=LMGTW-DOMAIN)

information:
LDAP Error 0x3a (58).
......................... ForestDnsZones failed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
For the partition (DC=DomainDnsZones,DC=LMGTW-DOMAIN) we

encountered the following error retrieving the cross-ref's

(CN=8f21449d-89ab-45b9-a283-3ef11cbabbd9,CN=Partitions,CN=Configuration,DC=LMGTW-DOMAIN)

information:
LDAP Error 0x3a (58).
......................... DomainDnsZones failed test CrossRefValidation
Starting test: CheckSDRefDom
For the partition (DC=DomainDnsZones,DC=LMGTW-DOMAIN) we

encountered the following error retrieving the cross-ref's

(CN=8f21449d-89ab-45b9-a283-3ef11cbabbd9,CN=Partitions,CN=Configuration,DC=LMGTW-DOMAIN)

information:
LDAP Error 0x3a (58).
......................... DomainDnsZones failed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
For the partition (CN=Schema,CN=Configuration,DC=LMGTW-DOMAIN) we

encountered the following error retrieving the cross-ref's

(CN=Enterprise Schema,CN=Partitions,CN=Configuration,DC=LMGTW-DOMAIN)

information:
LDAP Error 0x3a (58).
......................... Schema failed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
For the partition (CN=Configuration,DC=LMGTW-DOMAIN) we encountered

the following error retrieving the cross-ref's

(CN=Enterprise Configuration,CN=Partitions,CN=Configuration,DC=LMGTW-DOMAIN)

information:
LDAP Error 0x3a (58).
......................... Configuration failed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : LMGTW-DOMAIN
Starting test: CrossRefValidation
For the partition (DC=LMGTW-DOMAIN) we encountered the following

error retrieving the cross-ref's

(CN=LMGTW-DOMAIN,CN=Partitions,CN=Configuration,DC=LMGTW-DOMAIN)

information:
LDAP Error 0x3a (58).
......................... LMGTW-DOMAIN failed test CrossRefValidation
Starting test: CheckSDRefDom
......................... LMGTW-DOMAIN passed test CheckSDRefDom

Running enterprise tests on : LMGTW-DOMAIN
Starting test: Intersite
......................... LMGTW-DOMAIN passed test Intersite
Starting test: FsmoCheck
......................... LMGTW-DOMAIN passed test FsmoCheck

а зачем вы их вообще трогали ??? пусть там стоят стандартные. и всё.
А что значит стандартные???

[exo]

А что значит стандартные??? »

а там по умолчанию стоят типа a.root-servers.net

[Levin]

а там по умолчанию стоят типа a.root-servers.net

А как установить стандартные? При добавлении оно требует найти их в зонах.