Ошибки при установки второго DC

[pokul]

Добрый день.

Есть DC1 - Win2003 SP2 (serverDC1), решил поставить второй DC на Win2008R2 (serverDC2) и все бы ничего но после установки при проверки командой dcdiag, сыпятся ошибки + на serverDC2 нет шар Sysvol + Netlogon:

Directory Server Diagnosis

Performing initial setup:

Trying to find home server...

Home Server = serverDC2

* Identified AD Forest.

Done gathering initial info.



Doing initial required tests



Testing server: Default-First-Site-Name\SERVERDC2

Starting test: Connectivity

......................... SERVERDC2 passed test Connectivity



Doing primary tests



Testing server: Default-First-Site-Name\SERVERDC2

Starting test: Advertising

Warning: DsGetDcName returned information for \\serverDC1.ms.int, when

we were trying to reach SERVERDC2.

SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.

......................... SERVERDC2 failed test Advertising

Starting test: FrsEvent

There are warning or error events within the last 24 hours after the

SYSVOL has been shared. Failing SYSVOL replication problems may cause

Group Policy problems.

......................... SERVERDC2 passed test FrsEvent

Starting test: DFSREvent

......................... SERVERDC2 passed test DFSREvent

Starting test: SysVolCheck

......................... SERVERDC2 passed test SysVolCheck

Starting test: KccEvent

......................... SERVERDC2 passed test KccEvent

Starting test: KnowsOfRoleHolders

......................... SERVERDC2 passed test KnowsOfRoleHolders

Starting test: MachineAccount

......................... SERVERDC2 passed test MachineAccount

Starting test: NCSecDesc

Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have

Replicating Directory Changes In Filtered Set

access rights for the naming context:

DC=DomainDnsZones,DC=ms,DC=int

Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have

Replicating Directory Changes In Filtered Set

access rights for the naming context:

DC=ForestDnsZones,DC=ms,DC=int

......................... SERVERDC2 failed test NCSecDesc

Starting test: NetLogons

Unable to connect to the NETLOGON share! (\\SERVERDC2\netlogon)

[SERVERDC2] An net use or LsaPolicy operation failed with error 67,

The network name cannot be found..

......................... SERVERDC2 failed test NetLogons

Starting test: ObjectsReplicated

......................... SERVERDC2 passed test ObjectsReplicated

Starting test: Replications

......................... SERVERDC2 passed test Replications

Starting test: RidManager

......................... SERVERDC2 passed test RidManager

Starting test: Services

......................... SERVERDC2 passed test Services

Starting test: SystemLog

......................... SERVERDC2 passed test SystemLog

Starting test: VerifyReferences

......................... SERVERDC2 passed test VerifyReferences





Running partition tests on : DomainDnsZones

Starting test: CheckSDRefDom

......................... DomainDnsZones passed test CheckSDRefDom

Starting test: CrossRefValidation

......................... DomainDnsZones passed test

CrossRefValidation



Running partition tests on : ForestDnsZones

Starting test: CheckSDRefDom

......................... ForestDnsZones passed test CheckSDRefDom

Starting test: CrossRefValidation

......................... ForestDnsZones passed test

CrossRefValidation



Running partition tests on : Schema

Starting test: CheckSDRefDom

......................... Schema passed test CheckSDRefDom

Starting test: CrossRefValidation

......................... Schema passed test CrossRefValidation



Running partition tests on : Configuration

Starting test: CheckSDRefDom

......................... Configuration passed test CheckSDRefDom

Starting test: CrossRefValidation

......................... Configuration passed test CrossRefValidation



Running partition tests on : ts

Starting test: CheckSDRefDom

......................... ts passed test CheckSDRefDom

Starting test: CrossRefValidation

......................... ts passed test CrossRefValidation



Running enterprise tests on : ms.int

Starting test: LocatorCheck

......................... ms.int passed test LocatorCheck

Starting test: Intersite

......................... ms.int passed test Intersite



ipconfig -all - serverDC1:

Windows IP Configuration

Host Name . . . . . . . . . . . . : serverDC1
Primary Dns Suffix . . . . . . . : ms.int
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ms.int

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100+ Server Adapter (PILA
0B)
Physical Address. . . . . . . . . : 00-30-48-21-9B-31
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.168.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.168.254
DNS Servers . . . . . . . . . . . : 192.168.168.1
Primary WINS Server . . . . . . . : 192.168.168.1

ipconfig -all - serverDC2:

Windows IP Configuration

Host Name . . . . . . . . . . . . : serverDC2
Primary Dns Suffix . . . . . . . : ms.int
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ms.int

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Ada
pter
Physical Address. . . . . . . . . : 00-15-5D-A8-05-07
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.168.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.168.254
DNS Servers . . . . . . . . . . . : 192.168.168.1
127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled[/I]

Подскажите пож-та, как устранить ошибки?

[cameron]

вывод nslookup serverDC2 с сервера serverDC1?

[pokul]

nslookup serverDC2:
C:\Users\admin>nslookup
Default Server: serverDC1.ms.int
Address: 192.168.168.1

nslookup serverDC1:
C:\Documents and Settings\Administrator>nslookup
Default Server: serverDC1.ms.int
Address: 192.168.168.1

[cameron]

такс.
заходите на сервер serverDC1
пуск - выполнить - cmd
там пишете, в одну строчку:
nslookup serverDC2

покажите вывод

[pokul]

Не понял, извините :)

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : serverDC1
Primary Dns Suffix . . . . . . . : ms.int
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ms.int

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100+ Server Adapter (PILA847
0B)
Physical Address. . . . . . . . . : 00-30-48-21-9B-31
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.168.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.168.254
DNS Servers . . . . . . . . . . . : 192.168.168.1
Primary WINS Server . . . . . . . : 192.168.168.1

C:\Documents and Settings\Administrator>nslookup serverDC2
Server: serverDC1.ms.int
Address: 192.168.168.1

Name: serverDC2.ms.int
Address: 192.168.168.3

[pokul]

Друзья, есть идеи?

[Telepuzik]

pokul,
Сервер 2003-й давно перезагружали? На 2003 сервере в логах есть какие нибудь ошибки??

[pokul]

Перегружал давно, сегодня ночью попробую.
Касаемо логов на 2003-ем: в System ошибок нет, в Application две, постоянно повторяющиеся:

Первая:
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: 15.03.2012
Time: 13:20:04
User: NT AUTHORITY\SYSTEM
Computer: serverDC1
Description:
Windows cannot access the file gpt.ini for GPO CN={BA96A584-DF89-4C28-8FEE-33C9911BD49A},CN=Policies,CN=System,DC=ms,DC=int. The file must be present at the location <\\ms.int\SysVol\ms.int\Policies\{BA96A584-DF89-4C28-8FEE-33C9911BD49A}\gpt.ini>. (The network name cannot be found. ). Group Policy processing aborted.

Вторая:
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 15.03.2012
Time: 12:50:02
User: NT AUTHORITY\SYSTEM
Computer: serverDC1
Description:
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.

+
В логах File Replication Service, одна но постоянная:
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 02.09.2011
Time: 16:52:15
User: N/A
Computer: serverDC1
Description:
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.

[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.

WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.

To change this registry parameter, run regedit.

Click on Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.

If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.

[brass_net]

Прикольно - в логах постоянно две довольно серьезные ошибки и вы даже не пытались их устранить?
У вас DC сам по себе не адекватно работает, а вы пытаетесь поднять второй, ессно репликации никакой нет, ибо он даже на себя ничего не может сделать... imho

[pokul]

ну прикольного мало, а второй поднять пытаюсь, т.к. как вы правильно заметили первый работает не адекватно. По существу можете что то подсказать?

[Telepuzik]

Event Category: None
Event ID: 13568 »
Как и предпологал эта ошибка присутствует. Пока от нее не избавитесь второй КД у Вас не заработает.
По существу можете что то подсказать? »
Вам же система сама дала рекомендации что нужно сделать:
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value. »
Сделайте так:
Запустите редактор реестра и раскройте раздел HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters дважды щелкните по параметру Enable Journal Wrap Automatic Restore (если его нет создайте) измените значение с 0 на 1. Затем выполните команду net stop ntfrs & net start ntfrs
Смотрим в журнал там должны быть события с ID: 13553, 13554, 13516. Затем вывод net share c обоих КД покажите.