не стартует DNS

[felo]

Господа специалисты!
Перерыл кучу форумов, но так и не нашел решения своих траблов.
Предыстория:
В существующий домен 2000 добавил контроллер 2008 с целью последующего избавления от старого сервера.
Все как положено, подготовил с adprep.
Поставил винду, сделал его доп контроллером и настроил DNS server.
В настоящее время отслеживаю ошибки, прежде чем сделать его хозяином.
Ошибок тьма, но большинство связано с DNS.
Вся фишка в том, что при перезагрузке данной машины выдается "dns server - stopped",
в остальные ошибки я даже не лезу, т.к. они исходят именно из этого.
С чем это может быть связано?
Где-то на форумах мне попадались темы, что сетевые сервисы стартовали позже AD, но решения так и не было,
кто-то заменил сетевуху - и все полетело, кто-то пишет, что надо netlogon привязать к запуску DNS.
Но все это применимо, если DNS запускается, почему же он стопится?
Если потом запустить его вручную - все ОК. остаются только ошибки в разделе "best practices analyser" - в events исчезают.

[zai]

В настройках DNS "Загружать зону при старте:" откуда установлено?
покажи: ipconfig /all

[exo]

Обновление домена на Windows 2000 Server до Windows Server 2008 R2 (http://www.youtube.com/watch?v=OUQq0drYs24)

[felo]

load zone data at startup - "from AD and registry"


ipconfig /all
Windows IP Configuration

Host Name . . . . . . . . . . . . : TorServer
Primary Dns Suffix . . . . . . . : Tors
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Tors

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
Physical Address. . . . . . . . . : 00-25-90-AD-66-47
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.10.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.10
192.168.10.100
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{FDEDA10D-4750-43B8-B242-D577220415F1}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


dcdiag /test:dns
Directory Server Diagnosis

Performing initial setup:
Trying to find home server...
Home Server = TorServer
* Identified AD Forest.
Ldap search capabality attribute search failed on server SERVERNT, return
value = 81
Got error while checking if the DC is using FRS or DFSR. Error:
Win32 Error 81The VerifyReferences, FrsEvent and DfsrEvent tests might fail
because of this error.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\TORSERVER
Starting test: Connectivity
......................... TORSERVER passed test Connectivity

Doing primary tests

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

Starting test: DNS

DNS Tests are running and not hung. Please wait a few minutes...
......................... TORSERVER passed test DNS

Running partition tests on : Schema

Running partition tests on : Configuration

Running partition tests on : Tors

Running enterprise tests on : Tors
Starting test: DNS
Test results for domain controllers:

DC: TorServer.Tors
Domain: Tors


TEST: Dynamic update (Dyn)
Warning: Failed to delete the test record dcdiag-test-record in zone Tors

TorServer PASS PASS PASS PASS WARN PASS n/a
......................... Tors passed test DNS


dcdiag

Doing primary tests

Testing server: Default-First-Site-Name\TORSERVER
Starting test: Advertising
......................... TORSERVER passed 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.
......................... TORSERVER passed test FrsEvent
Starting test: DFSREvent
......................... TORSERVER passed test DFSREvent
Starting test: SysVolCheck
......................... TORSERVER passed test SysVolCheck
Starting test: KccEvent
......................... TORSERVER passed test KccEvent
Starting test: KnowsOfRoleHolders
[SERVERNT] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
Warning: SERVERNT is the Schema Owner, but is not responding to DS RPC
Bind.
Warning: SERVERNT is the Schema Owner, but is not responding to LDAP
Bind.
Warning: SERVERNT is the Domain Owner, but is not responding to DS RPC
Bind.
Warning: SERVERNT is the Domain Owner, but is not responding to LDAP
Bind.
Warning: SERVERNT is the PDC Owner, but is not responding to DS RPC
Bind.
Warning: SERVERNT is the PDC Owner, but is not responding to LDAP
Bind.
Warning: SERVERNT is the Rid Owner, but is not responding to DS RPC
Bind.
Warning: SERVERNT is the Rid Owner, but is not responding to LDAP
Bind.
Warning: SERVERNT is the Infrastructure Update Owner, but is not
responding to DS RPC Bind.
Warning: SERVERNT is the Infrastructure Update Owner, but is not
responding to LDAP Bind.
......................... TORSERVER failed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... TORSERVER passed test MachineAccount
Starting test: NCSecDesc
......................... TORSERVER passed test NCSecDesc
Starting test: NetLogons
[TORSERVER] User credentials does not have permission to perform this
operation.
The account used for this test must have network logon privileges
for this machine's domain.
......................... TORSERVER failed test NetLogons
Starting test: ObjectsReplicated
......................... TORSERVER passed test ObjectsReplicated
Starting test: Replications
......................... TORSERVER failed test Replications
Starting test: RidManager
......................... TORSERVER failed test RidManager
Starting test: Services
Could not open NTDS Service on TORSERVER, error 0x5
"Access is denied."
IsmServ Service is stopped on [TORSERVER]
......................... TORSERVER failed test Services
Starting test: SystemLog
An error event occurred. EventID: 0xC0002719
Time Generated: 11/13/2013 12:14:30
Event String:
DCOM was unable to communicate with the computer 195.177.123.1 using
any of the configured protocols.
An error event occurred. EventID: 0xC0002719
Time Generated: 11/13/2013 12:14:51
Event String:
DCOM was unable to communicate with the computer 84.52.107.107 using
any of the configured protocols.
......................... TORSERVER failed test SystemLog
Starting test: VerifyReferences
......................... TORSERVER passed test VerifyReferences


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 : Tors
Starting test: CheckSDRefDom
......................... Tors passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Tors passed test CrossRefValidation

Running enterprise tests on : Tors
Starting test: LocatorCheck
......................... Tors passed test LocatorCheck
Starting test: Intersite
......................... Tors passed test Intersite

[zai]

Попробуй:
ipconfig/flushdns
ipconfig/registerdns

[felo]

Попробовал - та же хрень.

Проблему решил, но наполовину.
Поставил сетевуху еще одну - и ошибки пропали.
Теперь вопрос - что со встроенными сетевухами?
Купил мать не дешевую Supermicro, и получается две сетевухи бестолковые, или слишком умные.
Они на самом деле долго стартуют.
Буду звонить в Тринити - пусть разбираются.

Если кто сталкивался с таким - пишите.