Привязал, ко внутреннему, убрал из настроек сетевого интерфейса внешний IP, добавил 127.0.0.1 вторым, перезагрузился. Вроде все нормально. Только nslookup и с основного сервера, и с дополнительного контроллера выдает:
***Can't find server name for address 192.168.8.1: Non-existent domain
Default server: UnKnown
Address: 192.168.8.1
>
И еще, были на внутреннем интерфейсе основного контроллера еще NWLink'овсние какие-то вещи, но отключенные (без галочек), при анинсталле выдало синий экран 0x000000d1
В журнале появилась ошибка:
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 18.06.2006
Time: 9:55:02
User: N/A
Computer: VIRIS-SRV
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.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Добавил в реестре этот ключ, перезагрузился...
На доп. контроллере:
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13509
Date: 18.06.2006
Time: 10:23:01
User: N/A
Computer: VIRIAL-SEC
Description:
The File Replication Service has enabled replication from VIRIS-SRV to VIRIAL-SEC for c:\windows\sysvol\domain after repeated retries.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Пара минут и шары SYSVOL и NETLOGON появились.
Т.е. все было действительно в привязке DNS сервера?! Я уже пробовал убирать внешний IP из списка ДНС на внутреннем интерфейсе. В прошлый раз это привело к неработоспособности контроллера. Почему же сейчас все получилось? NWLink'овские привязки виноваты?.. Или 127.0.0.1?.. Одни вопросы...
Но главное - все получилось! Спасибо всем, помогавшим советами!
