ipmanyak [more=dcdiag /v]C:\Documents and Settings\Администратор>psexec \\server dcdiag /v
PsExec v2.11 - Execute processes remotely
Copyright (C) 2001-2014 Mark Russinovich
Sysinternals -
www.sysinternals.com Domain Controller Diagnosis
Performing initial setup:
* Verifying that the local machine server, is a DC.
* Connecting to directory service on server server.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 1 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\SERVER
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... SERVER passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\SERVER
Starting test: Replications
* Replications Check
* Replication Latency Check
DC=ForestDnsZones,DC=ruta,DC=ua
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
DC=DomainDnsZones,DC=ruta,DC=ua
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
CN=Schema,CN=Configuration,DC=ruta,DC=ua
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
CN=Configuration,DC=ruta,DC=ua
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
DC=ruta,DC=ua
Latency information for 1 entries in the vector were ignored.
1 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
......................... SERVER passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC SERVER.
* Security Permissions Check for
DC=ForestDnsZones,DC=ruta,DC=ua
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=ruta,DC=ua
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=ruta,DC=ua
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=ruta,DC=ua
(Configuration,Version 2)
* Security Permissions Check for
DC=ruta,DC=ua
(Domain,Version 2)
......................... SERVER passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Unable to connect to the NETLOGON share! (\\SERVER\netlogon)
[SERVER] An net use or LsaPolicy operation failed with error 1203, Win3
2 Error 1203.
......................... SERVER failed test NetLogons
Starting test: Advertising
Fatal Error:DsGetDcName (SERVER) call failed, error 1355
The Locator could not find the server.
......................... SERVER failed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-Fi
rst-Site-Name,CN=Sites,CN=Configuration,DC=ruta,DC=ua
Role Domain Owner = CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-Fi
rst-Site-Name,CN=Sites,CN=Configuration,DC=ruta,DC=ua
Role PDC Owner = CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First
-Site-Name,CN=Sites,CN=Configuration,DC=ruta,DC=ua
Role Rid Owner = CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First
-Site-Name,CN=Sites,CN=Configuration,DC=ruta,DC=ua
Role Infrastructure Update Owner = CN=NTDS Settings,CN=SERVER,CN=Server
s,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ruta,DC=ua
......................... SERVER passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 2600 to 1073741823
* server.ruta.ua is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1600 to 2099
* rIDPreviousAllocationPool is 1600 to 2099
* rIDNextRID: 1671
......................... SERVER passed test RidManager
Starting test: MachineAccount
Checking machine account for DC SERVER on DC SERVER.
* SPN found :LDAP/server.ruta.ua/ruta.ua
* SPN found :LDAP/server.ruta.ua
* SPN found :LDAP/SERVER
* SPN found :LDAP/server.ruta.ua/RUTA
* SPN found :LDAP/bf7ab091-bb6b-4d48-a01f-21854d6cee93._msdcs.ruta.ua
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/bf7ab091-bb6b-4d48-a0
1f-21854d6cee93/ruta.ua
* SPN found :HOST/server.ruta.ua/ruta.ua
* SPN found :HOST/server.ruta.ua
* SPN found :HOST/SERVER
* SPN found :HOST/server.ruta.ua/RUTA
* SPN found :GC/server.ruta.ua/ruta.ua
......................... SERVER passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
NtFrs Service is stopped on [SERVER]
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... SERVER failed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
SERVER is in domain DC=ruta,DC=ua
Checking for CN=SERVER,OU=Domain Controllers,DC=ruta,DC=ua in domain DC
=ruta,DC=ua on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Sit
e-Name,CN=Sites,CN=Configuration,DC=ruta,DC=ua in domain CN=Configuration,DC=rut
a,DC=ua on 1 servers
Object is up-to-date on all servers.
......................... SERVER passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
The registry lookup failed to determine the state of the SYSVOL. The
error returned was 0 (Win32 Error 0). Check the FRS event log to see
if the SYSVOL has successfully been shared.
......................... SERVER passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
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.
An Warning Event occured. EventID: 0x800034FE
Time Generated: 04/27/2015 11:02:03
(Event String could not be retrieved)
......................... SERVER failed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15 minut
es.
......................... SERVER passed test kccevent
Starting test: systemlog
* The System Event log test
Found no errors in System Event log in the last 60 minutes.
......................... SERVER passed test systemlog
Test omitted by user request: VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)
CN=SERVER,OU=Domain Controllers,DC=ruta,DC=ua and backlink on
CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configurati
on,DC=ruta,DC=ua
are correct.
The system object reference (frsComputerReferenceBL)
CN=SERVER,CN=Domain System Volume (SYSVOL share),CN=File Replication Se
rvice,CN=System,DC=ruta,DC=ua
and backlink on CN=SERVER,OU=Domain Controllers,DC=ruta,DC=ua are
correct.
The system object reference (serverReferenceBL)
CN=SERVER,CN=Domain System Volume (SYSVOL share),CN=File Replication Se
rvice,CN=System,DC=ruta,DC=ua
and backlink on
CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sit
es,CN=Configuration,DC=ruta,DC=ua
are correct.
......................... SERVER passed test VerifyReferences
Test omitted by user request: VerifyEnterpriseReferences
Test omitted by user request: CheckSecurityError
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 : ruta
Starting test: CrossRefValidation
......................... ruta passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ruta passed test CheckSDRefDom
Running enterprise tests on : ruta.ua
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... ruta.ua 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.
PDC Name: \\server.ruta.ua
Locator Flags: 0xe00003fd
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 135
5
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.
......................... ruta.ua failed test FsmoCheck
Test omitted by user request: DNS
Test omitted by user request: DNS
dcdiag exited on server with error code 0.[/more]
[more=netdiag /v]C:\Documents and Settings\Администратор>psexec \\server netdiag /v
PsExec v2.11 - Execute processes remotely
Copyright (C) 2001-2014 Mark Russinovich
Sysinternals -
www.sysinternals.com Gathering IPX configuration information.
Querying status of the Netcard drivers... Passed
Testing Domain membership... Failed
Gathering NetBT configuration information.
Testing for autoconfiguration... Passed
Testing IP loopback ping... Passed
Testing default gateways... Passed
Enumerating local and remote NetBT name cache... Passed
Testing the WINS server
Local Area Connection
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this adapter.
Gathering Winsock information.
Testing DNS
PASS - All the DNS entries for DC are registered on DNS server '127.0.0.1' a
nd other DCs also have some of the names registered.
Testing redirector and browser... Passed
Testing DC discovery.
Looking for a DC
Gathering the list of Domain Controllers for domain 'RUTA'
Testing trust relationships... Skipped
Testing Kerberos authentication... Passed
Testing LDAP servers in Domain RUTA ...
Gathering routing information
Gathering network statistics information.
Component Name : Point to Point Tunneling Protocol
Bind Name: mspptp
Binding Paths:
Component Name : Layer 2 Tunneling Protocol
Bind Name: msl2tp
Binding Paths:
Component Name : Remote Access NDIS WAN Driver
Bind Name: NdisWan
Binding Paths:
Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: Direct Parallel
Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: WAN Miniport (PPPOE)
Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: WAN Miniport (PPTP)
Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiscowan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: WAN Miniport (L2TP)
Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanasync
Upper Component: Remote Access NDIS WAN Driver
Lower Component: RAS Async Adapter
Component Name : NDIS Usermode I/O Protocol
Bind Name: Ndisuio
Binding Paths:
Owner of the binding path : NDIS Usermode I/O Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS Usermode I/O Protocol
Lower Component: HP NC107i PCIe Gigabit Server Adapter
Component Name : Message-oriented TCP/IP Protocol (SMB session)
Bind Name: NetbiosSmb
Binding Paths:
Component Name : WINS Client(TCP/IP) Protocol
Bind Name: NetBT
Binding Paths:
Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: HP NC107i PCIe Gigabit Server Adapter
Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)
Component Name : Internet Protocol (TCP/IP)
Bind Name: Tcpip
Binding Paths:
Owner of the binding path : Internet Protocol (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: HP NC107i PCIe Gigabit Server Adapter
Owner of the binding path : Internet Protocol (TCP/IP)
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)
Component Name : Client for Microsoft Networks
Bind Name: LanmanWorkstation
Binding Paths:
Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: Client for Microsoft Networks
Lower Component: Message-oriented TCP/IP Protocol (SMB session)
Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: HP NC107i PCIe Gigabit Server Adapter
Owner of the binding path : Client for Microsoft Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: Client for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)
Component Name : WebClient
Bind Name: WebClient
Binding Paths:
Component Name : Wireless Configuration
Bind Name: wzcsvc
Binding Paths:
Component Name : Network Load Balancing
Bind Name: Wlbs
Binding Paths:
Owner of the binding path : Network Load Balancing
Binding Enabled: No
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: Network Load Balancing
Lower Component: HP NC107i PCIe Gigabit Server Adapter
Component Name : Steelhead
Bind Name: RemoteAccess
Binding Paths:
Component Name : Dial-Up Server
Bind Name: msrassrv
Binding Paths:
Component Name : Remote Access Connection Manager
Bind Name: RasMan
Binding Paths:
Component Name : Dial-Up Client
Bind Name: msrascli
Binding Paths:
Component Name : File and Printer Sharing for Microsoft Networks
Bind Name: LanmanServer
Binding Paths:
Owner of the binding path : File and Printer Sharing for Microsoft Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios_smb
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: Message-oriented TCP/IP Protocol (SMB session)
Owner of the binding path : File and Printer Sharing for Microsoft Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: HP NC107i PCIe Gigabit Server Adapter
Owner of the binding path : File and Printer Sharing for Microsoft Netwo
rks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)
Component Name : Generic Packet Classifier
Bind Name: Gpc
Binding Paths:
Component Name : Application Layer Gateway
Bind Name: ALG
Binding Paths:
Component Name : NetBIOS Interface
Bind Name: NetBIOS
Binding Paths:
Owner of the binding path : NetBIOS Interface
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: HP NC107i PCIe Gigabit Server Adapter
Owner of the binding path : NetBIOS Interface
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: NetBIOS Interface
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndiswanip
Upper Component: Internet Protocol (TCP/IP)
Lower Component: WAN Miniport (IP)
Component Name : HP NC107i PCIe Gigabit Server Adapter
Bind Name: {A22EF1CC-A1F0-4AEB-ADF4-2C7E64576693}
Binding Paths:
Component Name : WAN Miniport (IP)
Bind Name: NdisWanIp
Binding Paths:
Component Name : Direct Parallel
Bind Name: {122797F8-6CC0-42FB-A5E2-C1AAFE98F84C}
Binding Paths:
Component Name : WAN Miniport (PPPOE)
Bind Name: {23BD07D6-4E0D-4524-BA2A-6029965EAA0D}
Binding Paths:
Component Name : WAN Miniport (PPTP)
Bind Name: {0F37850C-A4BF-459F-BAE8-AAC2FA4EE953}
Binding Paths:
Component Name : WAN Miniport (L2TP)
Bind Name: {64C26F47-CEEF-4A13-916F-969D3997C15B}
Binding Paths:
Component Name : RAS Async Adapter
Bind Name: {AABEEAE9-AEE1-41E3-A390-185E5C6CF693}
Binding Paths:
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
netdiag exited on server with error code 1.[/more]
Да, контроллер точно один. Когда то был вторым, потом остался один и был повышен до основного, но в журнале были ошибки ntfrs, которые я и пытался исправить.
