Случилось страшное. В сети два сервара с AD, после нештатного выключения питания и простоя около суток перестали работать оба сервера. Не запускаеться AD и DNS.
Сеть лежит полностью. Откаты с backup-a не помогают. Голову уже сломал что делать.
Где рыть что делать пересоздавать AD геморно слишком большая сеть? Помогите плиз.
Поискал почитал подобного случая не нашол
PS до этого пара програмеров меняли сервера ролями (дня за 3 до аварии) но все работало и машины перезагружалиь нормально.
Netdiag.exe: (сетевой кабель от сетевки отключен)
Computer Name: S01
DNS Host Name: s01.vbh.local
System info : Microsoft Windows Server 2003 (Build 3790)
Processor : EM64T Family 15 Model 6 Stepping 5, GenuineIntel
List of installed hotfixes :
Q147222
Netcard queries test . . . . . . . : Passed
GetStats failed for 'Прямой параллельный порт'. [ERROR_NOT_SUPPORTED]
[WARNING] The net card 'Минипорт WAN (PPTP)' may not be working because it has not received any packets.
[WARNING] The net card 'Минипорт WAN (PPPoE)' may not be working because it has not received any packets.
[WARNING] The net card 'Минипорт WAN (IP)' may not be working because it has not received any packets.
GetStats failed for 'Минипорт WAN (L2TP)'. [ERROR_NOT_SUPPORTED]
[WARNING] The net card 'Intel(R) PRO/1000 PM Network Connection' may not be working.
Per interface results:
Adapter : Подключение по локальной сети 2
Netcard queries test . . . : Failed
NetCard Status: DISCONNECTED
Some tests will be skipped on this interface.
Host Name. . . . . . . . . : s01
IP Address . . . . . . . . : 192.168.0.10
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.0.10
Primary WINS Server. . . . : 192.168.0.10
Dns Servers. . . . . . . . : 192.168.0.10
192.168.0.13
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{1E8B795F-09C9-4D6B-9625-F2112E007B46}
1 NetBt transport currently configured.
Autonet address test . . . . . . . : Failed
[FATAL] All adapters are autoconfigured.
The DHCP servers are unreachable. Please check cables, hubs, and taps.
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Failed
[FATAL] NO GATEWAYS ARE REACHABLE.
You have no connectivity to other network segments.
If you configured the IP protocol manually then
you need to add at least one valid gateway.
NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for the name
's01.vbh.local.'. [ERROR_TIMEOUT]
The name 's01.vbh.local.' may not be registered in DNS.
[FATAL] Could not open file C:\WINDOWS\system32\config\netlogon.dns for reading.
[FATAL] Could not open file C:\WINDOWS\system32\config\netlogon.dns for reading.
[FATAL] No DNS servers have the DNS records for this DC registered.
Redir and Browser test . . . . . . : Failed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{1E8B795F-09C9-4D6B-9625-F2112E007B46}
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{1E8B795F-09C9-4D6B-9625-F2112E007B46}
The browser is bound to 1 NetBt transport.
[FATAL] Cannot send mailslot message to 'VBH*' via browser. [ERROR_INVALID_FUNCTION]
DC discovery test. . . . . . . . . : Failed
[FATAL] Cannot find DC in domain 'VBH'. [ERROR_NO_SUCH_DOMAIN]
DC list test . . . . . . . . . . . : Failed
'VBH': Cannot find DC to get DC list from [test skipped].
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Skipped
'VBH': Cannot find DC to get DC list from [test skipped].
LDAP test. . . . . . . . . . . . . : Failed
Cannot find DC to run LDAP tests on. The error occurred was: Указанный домен не существует или к нему невозможно подключиться.
[WARNING] Cannot find DC in domain 'VBH'. [ERROR_NO_SUCH_DOMAIN]
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Skipped
Note: run "netsh ipsec dynamic show /?" for more detailed information
The command completed successfully
Dcdiag.exe
Domain Controller Diagnosis
Performing initial setup:
The directory service on s01 has not finished initializing.
In order for the directory service to consider itself synchronized, it must
attempt an initial synchronization with at least one replica of this
server's writeable domain. It must also obtain Rid information from the Rid
FSMO holder.
The directory service has not signalled the event which lets other services
know that it is ready to accept requests. Services such as the Key
Distribution Center, Intersite Messaging Service, and NetLogon will not
consider this system as an eligible domain controller.
The directory service on S01 has not finished initializing.
In order for the directory service to consider itself synchronized, it must
attempt an initial synchronization with at least one replica of this
server's writeable domain. It must also obtain Rid information from the Rid
FSMO holder.
The directory service has not signalled the event which lets other services
know that it is ready to accept requests. Services such as the Key
Distribution Center, Intersite Messaging Service, and NetLogon will not
consider this system as an eligible domain controller.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\S01
Starting test: Connectivity
The host 9d9a8573-bb26-4c48-a48c-8e7959750cbc._msdcs.vbh.local could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(9d9a8573-bb26-4c48-a48c-8e7959750cbc._msdcs.vbh.local) couldn't be
resolved, the server name (s01.vbh.local) resolved to the IP address
(192.168.0.10) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... S01 failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\S01
Skipping all tests, because server S01 is
not responding to directory service requests
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : vbh
Starting test: CrossRefValidation
......................... vbh passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... vbh passed test CheckSDRefDom
Running enterprise tests on : vbh.local
Starting test: Intersite
......................... vbh.local passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
A KDC could not be located - All the KDCs are down.
......................... vbh.local failed test FsmoCheck
, так и это надо походить 