The specified domain either does not exist or could not be contacted как исправить ошибку

When you try to join a Windows-based computer to an existing domain, you may get an error prompt with the error message The specified domain either does not exist or could not be contacted. This post identifies the most likely culprits, as well as provides the most suitable solutions to fix the error. The error prompt appears after entering the username and the associated password.

The error commonly occurs due to invalid DNS settings on the workstation, because Active Directory requires the use of domain DNS (and not router’s address) to work properly. The error can also occur due to IPv6 (if configured) is not working.

Assuming that your Active Directory Domain Controller (and DNS Server) is a Windows Server machine and is responsible for the local domain and has the IP Address of 123.123.123.123. At this example, the IP and the Preferred DNS address on the Primary Domain Controller must be the same, otherwise, you may encounter the issue in view.

So, if you have encountered The specified domain either does not exist or could not be contacted issue on a Windows 11/10 client machine you’re trying to join to a domain, you can try our recommended solution below to resolve the issue on the system.

1. Set the Preferred DNS IP to match the Domain Controller’s IP on Client Workstation
2. Specify the WINS Server’s IP address on Client machine
3. Modify SysVolReady registry key value on Domain Controller

Let’s take a look at the description of the process involved concerning each of the listed solutions.

Before you try the solutions below, if you have IPv6 configured, you can disable the protocol and then release TCP/IP, Flush DNS, Reset Winsock, Reset Proxy which can potentially resolve DNS issue on Windows 11/10. Afterwards, try the client PC domain join again and see if the procedure completes without the error in hand.

1] Set the Preferred DNS IP to match the Domain Controller’s IP on Client Workstation

This solution to resolve The specified domain either does not exist or could not be contacted issue on a Windows 11/10 client machine you’re trying to join to a domain, is to set the Preferred DNS IP to point to Primary Domain Controller’s IP address on each client workstation that you want to join in the domain.

Do the following:

• Press Windows key + R to invoke the Run dialog.
• In the Run dialog box, type ncpa.cpl and hit Enter to open Network and Sharing Center (if unable, see Network and Sharing Center not opening).
• Right-click on Local Area Connection and select Properties.
• Next, double-click on Internet Protocol TCP/IPv4.
• Now, change the Preferred DNS server address to match the Primary Domain Controller’s IP address (run IPConfig to see the exact IP for your setup).
• Check the Validate settings upon exit option.
• Click OK all through to close all windows.

Now, you can go ahead and join the workstation to the Domain without the issue in view reoccurring.

2] Specify the WINS Server’s IP address on Client machine

You can apply this solution if your Active Directory Domain Controller acts also as a WINS server – set the WINS IP address to point to the WINS Server’s (Primary Domain Controller’s IP address) on the client machine that you want to join to the Domain.

Note: This method works even when the Primary Domain Controller does not act as a WINS Server.

Do the following:

• Open Network and Sharing Center.
• Right-click on Local Area Connection and select Properties.
• Next, double-click on Internet Protocol TCP/IPv4.
• Click the Advanced button.
• Click WINS tab.
• Click Add button.
• In the WINS server field, type in the IP address of the WINS server.
• Click Add.
• Click OK all through to apply changes and close all windows.

You should now be able to join the workstation to the Domain without the issue in view reoccurring.

3] Modify SysVolReady registry key value on Domain Controller

SysVolReady indicates the replication status of the system volume on a domain controller. This entry appears only in the registry of a domain controller, and is set by DcPromo, Backup, and File Replication service (FRS) to indicate the replication state of the SYSVOL share. During replication, the system volume is not shared and the domain controller does not respond to DSGetDcName calls, which seek a domain controller in the domain.

This entry notifies the system that replication of the SYSVOL is complete. If a problem with the FRS prevents it from resetting this value automatically after replication, you can change the value of this entry to 1 via Registry Editor.

Since this is a registry operation, it is recommended that you back up the registry or create a system restore point as necessary precautionary measures. Once done, you can proceed as follows:

• Press Windows key + R to invoke the Run dialog.
• In the Run dialog box, type regedit and hit Enter to open Registry Editor.
• Navigate or jump to the registry key path below:

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesNetlogonParameters

• At the location, on the right pane, double-click the SysVolReady entry to edit its properties.
• Input 1 in the Value data field.

The value 1 means the system volume is not being replicated – the volume is shared. The value 0 means the system volume is being replicated or receiving replication updates and is not shared.

• Click OK or hit Enter to save the change.
• Exit Registry Editor.
• You may have to reboot the Domain Controller.

After the DC restarts, you can now successfully join the client machine to the domain.

That’s it!

Related post: An Active Directory Domain Controller (AD DC) for the domain could not be contacted

How do I fix Domain not available?

To fix the We can’t sign you with this credential because your domain isn’t available error, you can try the following suggestions:

• Reboot the system with no network connectivity.
• Remove the user from the protected user group.
• Using Security policy snap-in.
• Change the DNS server address.

What does domain does not exist mean?

If you are getting the domain does not exist error message, then it simply means the HTTP client will not be able to connect to any HTTP server, and thus you will not get any HTTP response at all, because the lower layer protocols cannot connect to provide the conduit for the higher-level HTTP connection.

How do I log into a computer without a domain?

You can log into a computer without a domain by simply logging in to Windows with Local Account without specifying the Computer Name. In the username field simply enter .. – the domain below will disappear and switch to your local computer name without typing it. Then specify your local username after the .. to use the local account with that username. Alternatively, type the computer name followed by a backslash and the username to achieve the same effect.

How do you use DCDiag?

The DCDiag utility is built into Windows Server 2008 R2 and Windows Server 2008. The tool analyzes the state of domain controllers in a forest or enterprise and reports any problems to help in troubleshooting. To use dcdiag, you must run the dcdiag command from an elevated command prompt. Dcdiag is available if you have the Active Directory Domain Services (AD DS) or Active Directory Lightweight Directory Services (AD LDS) server role installed. It is also available if you install the AD DS Tools that are part of the Remote Server Administration Tools (RSAT).

When you try to join a Windows-based computer to an existing domain, you may get an error prompt with the error message The specified domain either does not exist or could not be contacted. This post identifies the most likely culprits, as well as provides the most suitable solutions to fix the error. The error prompt appears after entering the username and the associated password.

The error commonly occurs due to invalid DNS settings on the workstation, because Active Directory requires the use of domain DNS (and not router’s address) to work properly. The error can also occur due to IPv6 (if configured) is not working.

Assuming that your Active Directory Domain Controller (and DNS Server) is a Windows Server machine and is responsible for the local domain and has the IP Address of 123.123.123.123. At this example, the IP and the Preferred DNS address on the Primary Domain Controller must be the same, otherwise, you may encounter the issue in view.

So, if you have encountered The specified domain either does not exist or could not be contacted issue on a Windows 11/10 client machine you’re trying to join to a domain, you can try our recommended solution below to resolve the issue on the system.

1. Set the Preferred DNS IP to match the Domain Controller’s IP on Client Workstation
2. Specify the WINS Server’s IP address on Client machine
3. Modify SysVolReady registry key value on Domain Controller

Let’s take a look at the description of the process involved concerning each of the listed solutions.

Before you try the solutions below, if you have IPv6 configured, you can disable the protocol and then release TCP/IP, Flush DNS, Reset Winsock, Reset Proxy which can potentially resolve DNS issue on Windows 11/10. Afterwards, try the client PC domain join again and see if the procedure completes without the error in hand.

1] Set the Preferred DNS IP to match the Domain Controller’s IP on Client Workstation

This solution to resolve The specified domain either does not exist or could not be contacted issue on a Windows 11/10 client machine you’re trying to join to a domain, is to set the Preferred DNS IP to point to Primary Domain Controller’s IP address on each client workstation that you want to join in the domain.

Do the following:

• Press Windows key + R to invoke the Run dialog.
• In the Run dialog box, type ncpa.cpl and hit Enter to open Network and Sharing Center (if unable, see Network and Sharing Center not opening).
• Right-click on Local Area Connection and select Properties.
• Next, double-click on Internet Protocol TCP/IPv4.
• Now, change the Preferred DNS server address to match the Primary Domain Controller’s IP address (run IPConfig to see the exact IP for your setup).
• Check the Validate settings upon exit option.
• Click OK all through to close all windows.

Now, you can go ahead and join the workstation to the Domain without the issue in view reoccurring.

2] Specify the WINS Server’s IP address on Client machine

You can apply this solution if your Active Directory Domain Controller acts also as a WINS server – set the WINS IP address to point to the WINS Server’s (Primary Domain Controller’s IP address) on the client machine that you want to join to the Domain.

Note: This method works even when the Primary Domain Controller does not act as a WINS Server.

Do the following:

• Open Network and Sharing Center.
• Right-click on Local Area Connection and select Properties.
• Next, double-click on Internet Protocol TCP/IPv4.
• Click the Advanced button.
• Click WINS tab.
• Click Add button.
• In the WINS server field, type in the IP address of the WINS server.
• Click Add.
• Click OK all through to apply changes and close all windows.

You should now be able to join the workstation to the Domain without the issue in view reoccurring.

3] Modify SysVolReady registry key value on Domain Controller

SysVolReady indicates the replication status of the system volume on a domain controller. This entry appears only in the registry of a domain controller, and is set by DcPromo, Backup, and File Replication service (FRS) to indicate the replication state of the SYSVOL share. During replication, the system volume is not shared and the domain controller does not respond to DSGetDcName calls, which seek a domain controller in the domain.

This entry notifies the system that replication of the SYSVOL is complete. If a problem with the FRS prevents it from resetting this value automatically after replication, you can change the value of this entry to 1 via Registry Editor.

Since this is a registry operation, it is recommended that you back up the registry or create a system restore point as necessary precautionary measures. Once done, you can proceed as follows:

• Press Windows key + R to invoke the Run dialog.
• In the Run dialog box, type regedit and hit Enter to open Registry Editor.
• Navigate or jump to the registry key path below:

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesNetlogonParameters

• At the location, on the right pane, double-click the SysVolReady entry to edit its properties.
• Input 1 in the Value data field.

The value 1 means the system volume is not being replicated – the volume is shared. The value 0 means the system volume is being replicated or receiving replication updates and is not shared.

• Click OK or hit Enter to save the change.
• Exit Registry Editor.
• You may have to reboot the Domain Controller.

After the DC restarts, you can now successfully join the client machine to the domain.

That’s it!

Related post: An Active Directory Domain Controller (AD DC) for the domain could not be contacted

How do I fix Domain not available?

To fix the We can’t sign you with this credential because your domain isn’t available error, you can try the following suggestions:

• Reboot the system with no network connectivity.
• Remove the user from the protected user group.
• Using Security policy snap-in.
• Change the DNS server address.

What does domain does not exist mean?

If you are getting the domain does not exist error message, then it simply means the HTTP client will not be able to connect to any HTTP server, and thus you will not get any HTTP response at all, because the lower layer protocols cannot connect to provide the conduit for the higher-level HTTP connection.

How do I log into a computer without a domain?

You can log into a computer without a domain by simply logging in to Windows with Local Account without specifying the Computer Name. In the username field simply enter .. – the domain below will disappear and switch to your local computer name without typing it. Then specify your local username after the .. to use the local account with that username. Alternatively, type the computer name followed by a backslash and the username to achieve the same effect.

How do you use DCDiag?

The DCDiag utility is built into Windows Server 2008 R2 and Windows Server 2008. The tool analyzes the state of domain controllers in a forest or enterprise and reports any problems to help in troubleshooting. To use dcdiag, you must run the dcdiag command from an elevated command prompt. Dcdiag is available if you have the Active Directory Domain Services (AD DS) or Active Directory Lightweight Directory Services (AD LDS) server role installed. It is also available if you install the AD DS Tools that are part of the Remote Server Administration Tools (RSAT).

Error The specified domain either does not exist or could not be contacted Windows error is a very common error that occurs when you try to connect to your domain server. No matter how many times you enter the credentials, this error prevents the user from accessing the domain by giving this error. This error can be caused due to a system upgrade, misconfigured network settings, or misconfigured registries. To fix the error. We have collected a few troubleshooting methods that will surely help you in getting rid of the error.

Causes of The Specified Domain either does not Exist or Could not be Contacted Error:

The major causes behind this error include misconfigured network settings, bad network connection. Misconfigured or corrupted registries, system upgrade, can also be the reason behind this Error The Specified Domain either does not Exist or Could not be Contacted Windows error. Let’s take a look at each of the possible causes.

• Misconfigured Network Settings
• Misconfigured registry keys
• Bad Network connection
• Windows Update

Similar Types of The Specified Domain either does not Exist or Could not be Contacted Error:

• The specified domain does not exist or cannot be contacted windows 10
• Windows XP
• Windows 10 administrator the specified domain does not exist
• The specified domain either does not exist server 2016
• Windows 7
• Windows 10 boot error
• The specified domain does not exist or cannot be contacted remote desktop
• Certificate enrollment
• The specified domain does not exist or cannot be contacted windows 10

As from the causes, we can conclude that due to invalid network settings on the workstation side, this error occurs. So we will first make sure that the DNS network is set correctly. The second method will disable the IPV6 in the network settings. Thirdly we will try to fix the WINS server network settings. Fourthly we will tweak the registries to remove the error. Let’s go through all of the methods in detail.

1. Setting the Right DNS Server Address on Client Workstation –

In the first error The Specified Domain either does not Exist or Could not be Contacted Windows 10 method; we will set the right DNS address in the network settings on the client-side. If you have recently upgraded your system, the chances are that your DNS settings maybe have been reset. If you haven’t upgraded, then also it is suggested to verify that the DNS address is matching to that of the domain controller.

• STEP 1. Go to the start menu and open up Control Panel
• STEP 2. Now Go to Network and Internet > Network Connections

• STEP 3. Right Click on your Network Connection and go to Properties
• STEP 4. To change DNS double click on Internet Protocol (TCP/IPv4)
• STEP 5. Make sure Use the following DNS server address is chosen
• STEP 6. Finally, put the DNS server address in the field and click OK

• STEP 7. Now will be able to connect easily without errors

2. Disabling the IPv6 in Network Settings –

In the second method, we will disable the IPv6 from the Network Adapter properties, and Then we will perform some commands to fix Windows 10 boot error The Specified Domain either does not Exist or Could not be Contacted error. Let’s see how it is done.

• STEP 1. Open Up Control Panel and
• STEP 2. Navigate to Network and Internet > Network and Sharing Center
• STEP 3. Now on Left Click on Change Adapter Settings
• STEP 4. Now Uncheck Internet Protocol (TCP/IPv6)

• STEP 5. Reboot your system now
• STEP 6. After rebooting open command prompt and type the following commands

ipconfig /flushdns
ipconfig /release
ipconfig /renew

• STEP 7. After performing all the commands, reboot system
• STEP 8. Finally, Try to connect

3. Making Changes in the WINS Server –

In this error The Specified Domain either does not Exist or Could not be Contacted server 2012 method; we will specify the WINS server IP address onto the client machine. Follow the steps.

• STEP 1. Follow STEPS 1-6 from Method 1
• STEP 2. Now Below Click on the Advance Button

• STEP 3. Navigate to WINS tab and click on Add

• STEP 4. Now in the field type the WINS Server’s IP Address and click Add

• STEP 5. Save all the changes, finally, try to reconnect and see if the error still persists

4. Tweaking the Registry Editor –

In this error The Specified Domain either does not Exist or Could not be Contacted 2012 method; we will try to tweak the registry keys. But make sure you follow each step carefully. Wrong changes may lead to an unstable system and prone to more errors.

• STEP 1. Open up the Run window by holding the Windows+R key simultaneously
• STEP 2. In the run window type regedit and hit Enter
• STEP 3. Now in the registry window navigate to the following location

HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > Netlogon > Parameters

• STEP 4. On right side locate SysvolReady and right-click then modify
• STEP 5. Now under the Value Data field put 1 and apply the change
• STEP 6. After saving the change reboot the system
• STEP 7. Now try to reconnect

Conclusion:

In this troubleshooting guide on error the specified domain either does not exist or could not be contacted windows error. We conclude that by following all f the above methods, you will surely get rid of this error. With this article, you get all the knowledge regarding the error about its cause and effects on the system.

We hope this article solved your problem and for more guides like this follow us.

Приветствую!
Заранее извиняюсь за сумбур.
Случилась беда. Лежит весь домен.
Всего 3 контроллера домена. DC1, DC4 в одном сайте, DC3 — в другом.
Началось с того, что основной контроллер (DC1) внезапно и безнадежно канул в лету. После тщетных попыток его восстановить из единственного систем-стэйта, было решено поднять новый по этой инструкции https://technet.microsoft.com/ru-ru/library/cc785849.aspx
Роли захватывал DC4. Всё прошло отлично до пункта с SYSVOL. NTFRS-репликация на вновь поднятый DC1 почему-то не шла и неудачные попытки ее оживить привели к полной неработоспособности вообще всего домена.
Признаюсь честно, пробовал рецепт из первого комментария отсюда http://eventid.net/display.asp?eventid=13568&eventno=1743&source=NtFrs&phase=1
Сначала исчезли ошибки и пошли нормальные сообщения, и потом я вернул «Enable Journal Wrap Automatic Restore» в 0 на всех доменах. Возможно после этого всё и началось.
При попытке залогиниться пользователь получает сообщение «The system cannot log you on due to the following error: The specified domain either does not exist or could not be contacted.»
DC4 (основной, на который были переданы все основные роли):
C:Documents and Settingsadmin>netdiag

…………………………………

Computer Name: DC4
DNS Host Name: dc4.concord.com
System info : Microsoft Windows Server 2003 R2 (Build 3790)
Processor : x86 Family 15 Model 6 Stepping 5, GenuineIntel
List of installed hotfixes :
KB2570791
KB2998527
KB3013410
KB957097
KB958644
KB958687
Q147222

Netcard queries test . . . . . . . : Passed

Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : dc4
IP Address . . . . . . . . : 192.168.0.14
Subnet Mask. . . . . . . . : 255.255.0.0
Default Gateway. . . . . . : 192.168.0.1
Primary WINS Server. . . . : 192.168.0.10
Secondary WINS Server. . . : 192.168.0.14
Dns Servers. . . . . . . . : 192.168.0.14
192.168.0.10

AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed

WINS service test. . . . . : Failed
The test failed. We were unable to query the WINS servers.

Global results:

Domain membership test . . . . . . : Failed
[WARNING] Ths system volume has not been completely replicated to the local
machine. This machine is not working properly as a DC.

NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{DCDCBD18-BEB6-425A-A017-B97CFEC98B49}
1 NetBt transport currently configured.

Autonet address test . . . . . . . : Passed

IP loopback ping test. . . . . . . : Passed

Default gateway test . . . . . . . : Passed

NetBT name test. . . . . . . . . . : Passed

Winsock test . . . . . . . . . . . : Passed

DNS test . . . . . . . . . . . . . : Passed
PASS — All the DNS entries for DC are registered on DNS server ‘192.168.0.14
‘ and other DCs also have some of the names registered.
PASS — All the DNS entries for DC are registered on DNS server ‘192.168.0.10
‘ and other DCs also have some of the names registered.

Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{DCDCBD18-BEB6-425A-A017-B97CFEC98B49}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{DCDCBD18-BEB6-425A-A017-B97CFEC98B49}
The browser is bound to 1 NetBt transport.

DC discovery test. . . . . . . . . : Failed
[FATAL] Cannot find DC in domain ‘CONCORD’. [ERROR_NO_SUCH_DOMAIN]

DC list test . . . . . . . . . . . : Failed
‘CONCORD’: Cannot find DC to get DC list from [test skipped].

Trust relationship test. . . . . . : Skipped

Kerberos test. . . . . . . . . . . : Skipped
‘CONCORD’: 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: The specified d
omain either does not exist or could not be contacted.

[WARNING] Cannot find DC in domain ‘CONCORD’. [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

C:Documents and Settingsadmin>ntfrsutl ds
NTFRS CONFIGURATION IN THE DS
SUBSTITUTE DCINFO FOR DC
FRS DomainControllerName: (null)
Computer Name : DC4
Computer DNS Name : dc4.concord.com

BINDING TO THE DS:
ldap_connect : dc4.concord.com
DsBind : dc4.concord.com

NAMING CONTEXTS:
SitesDn : CN=Sites,cn=configuration,dc=concord,dc=com
ServicesDn : CN=Services,cn=configuration,dc=concord,dc=com
DefaultNcDn: DC=concord,DC=com
ComputersDn: CN=Computers,DC=concord,DC=com
DomainCtlDn: OU=Domain Controllers,DC=concord,DC=com
Fqdn : CN=DC4,OU=Domain Controllers,DC=concord,DC=com
Searching : Fqdn

COMPUTER: DC4
DN : cn=dc4,ou=domain controllers,dc=concord,dc=com
Guid : a7f4fd77-6f6b-491d-8ac256fab14c9a88
UAC : 0x00082000
Server BL : CN=DC4,CN=Servers,CN=Akonit,CN=Sites,CN=Configuration,DC=concord,
DC=com
Settings : cn=ntds settings,cn=dc4,cn=servers,cn=akonit,cn=sites,cn=configur
ation,dc=concord,dc=com
DNS Name : dc4.concord.com
WhenCreated : 2/12/2009 9:20:44 Russia TZ 2 Standard Time Russia TZ 2 Standa
rd Time [-180]
WhenChanged : 10/3/2015 19:32:52 Russia TZ 2 Standard Time Russia TZ 2 Stand
ard Time [-180]

SUBSCRIPTION: NTFRS SUBSCRIPTIONS
DN : cn=ntfrs subscriptions,cn=dc4,ou=domain controllers,dc=concord,dc=c
om
Guid : cfb61ea1-34c8-4979-8ea72df65283a7f3
Working : c:windowsntfrs
Actual Working: c:windowsntfrs
WhenCreated : 2/12/2009 10:20:38 Russia TZ 2 Standard Time Russia TZ 2 St
andard Time [-180]
WhenChanged : 2/12/2009 10:20:38 Russia TZ 2 Standard Time Russia TZ 2 St
andard Time [-180]

SUBSCRIBER: DOMAIN SYSTEM VOLUME (SYSVOL SHARE)
DN : cn=domain system volume (sysvol share),cn=ntfrs subscriptions,cn
=dc4,ou=domain controllers,dc=concord,dc=com
Guid : 450298ae-e734-4abf-9e4fc3f47d6baee2
Member Ref: CN=DC4,CN=Domain System Volume (SYSVOL share),CN=File Repli
cation Service,CN=System,DC=concord,DC=com
Root : c:windowssysvoldomain
Stage : c:windowssysvolstagingdomain
WhenCreated : 2/12/2009 10:20:38 Russia TZ 2 Standard Time Russia TZ 2
Standard Time [-180]
WhenChanged : 2/12/2009 10:20:38 Russia TZ 2 Standard Time Russia TZ 2
Standard Time [-180]
Subscriber Member Back Links:
cn=dc4,cn=domain system volume (sysvol share),cn=file replication service,
cn=system,dc=concord,dc=com

SETTINGS: FILE REPLICATION SERVICE
DN : cn=file replication service,cn=system,dc=concord,dc=com
Guid : 2c15400f-6070-44be-90293824d8c1648e
WhenCreated : 11/10/2001 20:28:33 Russia TZ 2 Standard Time Russia TZ 2 Stan
dard Time [-180]
WhenChanged : 2/12/2009 10:14:6 Russia TZ 2 Standard Time Russia TZ 2 Standa
rd Time [-180]

SET: DOMAIN SYSTEM VOLUME (SYSVOL SHARE)
DN : cn=domain system volume (sysvol share),cn=file replication service,
cn=system,dc=concord,dc=com
Guid : d2f74eee-9985-48b1-b5d7dcb5b56d77ea
Type : 2
Primary Member: (null)
File Filter : *.tmp, *.bak, ~*
Dir Filter : (null)
FRS Flags : (null)
WhenCreated : 11/10/2001 20:35:47 Russia TZ 2 Standard Time Russia TZ 2 S
tandard Time [-180]
WhenChanged : 2/12/2009 10:15:8 Russia TZ 2 Standard Time Russia TZ 2 Sta
ndard Time [-180]

MEMBER: DC1
DN : cn=dc1,cn=domain system volume (sysvol share),cn=file replicatio
n service,cn=system,dc=concord,dc=com
Guid : 030f326e-540a-4fe5-910893e83caac413
Server Ref : CN=NTDS Settings,CN=DC1,CN=Servers,CN=Akonit,CN=Sites,
CN=Configuration,DC=concord,DC=com
Computer Ref : cn=dc1,ou=domain controllers,dc=concord,dc=com
Cracked Domain : concord.com
Cracked Name : 00000002 CONCORDDC1$
Cracked Domain : concord.com
Cracked Name : fffffff4 S-1-5-21-1304569826-626877892-1847928074-1758
6
Computer’s DNS : dc1.concord.com
WhenCreated : 10/9/2015 22:1:55 Russia TZ 2 Standard Time Russia TZ 2
Standard Time [-180]
WhenChanged : 10/9/2015 22:2:32 Russia TZ 2 Standard Time Russia TZ 2
Standard Time [-180]

CXTION: 27A9F25E-5F90-4F2D-A9F8-920AFD54D41F
DN : cn=27a9f25e-5f90-4f2d-a9f8-920afd54d41f,cn=ntds settings,cn=d
c1,cn=servers,cn=akonit,cn=sites,cn=configuration,dc=concord,dc=com
Guid : 70be9b5b-18b1-4068-94d30f3d8436e007
Partner Dn : cn=ntds settings,cn=dc4,cn=servers,cn=akonit,cn=sites
,cn=configuration,dc=concord,dc=com
Partner Rdn : NTDS SETTINGS
Enabled : TRUE
WhenCreated : 10/9/2015 22:6:54 Russia TZ 2 Standard Time Russia TZ
2 Standard Time [-180]
WhenChanged : 10/9/2015 22:37:32 Russia TZ 2 Standard Time Russia T
Z 2 Standard Time [-180]
Options : 0x00000001 [AutoGenCxtion ]
Schedule
Day 1: 111111111111111111111111
Day 2: 111111111111111111111111
Day 3: 111111111111111111111111
Day 4: 111111111111111111111111
Day 5: 111111111111111111111111
Day 6: 111111111111111111111111
Day 7: 111111111111111111111111

MEMBER: DC3
DN : cn=dc3,cn=domain system volume (sysvol share),cn=file replicatio
n service,cn=system,dc=concord,dc=com
Guid : d1330c13-8dfe-41ac-aa99f911e0951e9a
Server Ref : CN=NTDS Settings,CN=DC3,CN=Servers,CN=Farmproekt,CN=Si
tes,CN=Configuration,DC=concord,DC=com
Computer Ref : cn=dc3,ou=domain controllers,dc=concord,dc=com
Cracked Domain : concord.com
Cracked Name : 00000002 CONCORDDC3$
Cracked Domain : concord.com
Cracked Name : fffffff4 S-1-5-21-1304569826-626877892-1847928074-1534
9
Computer’s DNS : dc3.concord.com
WhenCreated : 3/26/2008 12:34:47 Russia TZ 2 Standard Time Russia TZ 2
Standard Time [-180]
WhenChanged : 2/12/2009 10:15:58 Russia TZ 2 Standard Time Russia TZ 2
Standard Time [-180]

CXTION: F8FDF71C-636F-42FA-BFD3-789EB493614D
DN : cn=f8fdf71c-636f-42fa-bfd3-789eb493614d,cn=ntds settings,cn=d
c3,cn=servers,cn=farmproekt,cn=sites,cn=configuration,dc=concord,dc=com
Guid : cc83954c-ec7e-4ee0-abc31ad9d5b743af
Partner Dn : cn=ntds settings,cn=dc4,cn=servers,cn=akonit,cn=sites
,cn=configuration,dc=concord,dc=com
Partner Rdn : NTDS SETTINGS
Enabled : TRUE
WhenCreated : 10/9/2015 1:9:54 Russia TZ 2 Standard Time Russia TZ
2 Standard Time [-180]
WhenChanged : 10/9/2015 21:28:15 Russia TZ 2 Standard Time Russia T
Z 2 Standard Time [-180]
Options : 0x00000005 [AutoGenCxtion OverrideNotifyDefault ]
Schedule
Day 1: ffffffffffffffffffffffff
Day 2: ffffffffffffffffffffffff
Day 3: ffffffffffffffffffffffff
Day 4: ffffffffffffffffffffffff
Day 5: ffffffffffffffffffffffff
Day 6: ffffffffffffffffffffffff
Day 7: ffffffffffffffffffffffff

MEMBER: DC4
DN : cn=dc4,cn=domain system volume (sysvol share),cn=file replicatio
n service,cn=system,dc=concord,dc=com
Guid : db9b3e11-0804-4a55-a37f3aded21aa45a
Server Ref : CN=NTDS Settings,CN=DC4,CN=Servers,CN=Akonit,CN=Sites,
CN=Configuration,DC=concord,DC=com
Computer Ref : cn=dc4,ou=domain controllers,dc=concord,dc=com
Cracked Domain : concord.com
Cracked Name : 00000002 CONCORDDC4$
Cracked Domain : concord.com
Cracked Name : fffffff4 S-1-5-21-1304569826-626877892-1847928074-1580
9
Computer’s DNS : dc4.concord.com
WhenCreated : 2/12/2009 10:20:38 Russia TZ 2 Standard Time Russia TZ 2
Standard Time [-180]
WhenChanged : 2/12/2009 10:20:38 Russia TZ 2 Standard Time Russia TZ 2
Standard Time [-180]

CXTION: B9410A0F-1C4B-4E81-9E23-19A174FD89F8
DN : cn=b9410a0f-1c4b-4e81-9e23-19a174fd89f8,cn=ntds settings,cn=d
c4,cn=servers,cn=akonit,cn=sites,cn=configuration,dc=concord,dc=com
Guid : da19afff-5f7c-4c28-a08298c16bdad88d
Partner Dn : cn=ntds settings,cn=dc3,cn=servers,cn=farmproekt,cn=s
ites,cn=configuration,dc=concord,dc=com
Partner Rdn : NTDS SETTINGS
Enabled : TRUE
WhenCreated : 10/9/2015 1:18:38 Russia TZ 2 Standard Time Russia TZ
2 Standard Time [-180]
WhenChanged : 10/9/2015 1:34:20 Russia TZ 2 Standard Time Russia TZ
2 Standard Time [-180]
Options : 0x00000005 [AutoGenCxtion OverrideNotifyDefault ]
Schedule
Day 1: ffffffffffffffffffffffff
Day 2: ffffffffffffffffffffffff
Day 3: ffffffffffffffffffffffff
Day 4: ffffffffffffffffffffffff
Day 5: ffffffffffffffffffffffff
Day 6: ffffffffffffffffffffffff
Day 7: ffffffffffffffffffffffff

CXTION: DD46D695-73A5-4356-A76C-F640558EB472
DN : cn=dd46d695-73a5-4356-a76c-f640558eb472,cn=ntds settings,cn=d
c4,cn=servers,cn=akonit,cn=sites,cn=configuration,dc=concord,dc=com
Guid : 82f15a02-b94e-4e52-849b14d1abf9b88b
Partner Dn : cn=ntds settings,cn=dc1,cn=servers,cn=akonit,cn=sites
,cn=configuration,dc=concord,dc=com
Partner Rdn : NTDS SETTINGS
Enabled : TRUE
WhenCreated : 10/9/2015 22:2:31 Russia TZ 2 Standard Time Russia TZ
2 Standard Time [-180]
WhenChanged : 10/9/2015 22:40:41 Russia TZ 2 Standard Time Russia T
Z 2 Standard Time [-180]
Options : 0x00000001 [AutoGenCxtion ]
Schedule
Day 1: 111111111111111111111111
Day 2: 111111111111111111111111
Day 3: 111111111111111111111111
Day 4: 111111111111111111111111
Day 5: 111111111111111111111111
Day 6: 111111111111111111111111
Day 7: 111111111111111111111111

C:Documents and Settingsadmin>dcdiag /q
[Replications Check,DC4] A recent replication attempt failed:
From DC1 to DC4
Naming Context: CN=Schema,CN=Configuration,DC=concord,DC=com
The replication generated an error (8524):
Win32 Error 8524
The failure occurred at 2015-10-10 00:49:44.
The last success occurred at 2015-10-10 00:14:25.
1 failures have occurred since the last success.
The guid-based DNS name 5d8285c5-071e-4968-8c56-cd91925ba31c._msdcs.
concord.com
is not registered on one or more DNS servers.
[Replications Check,DC4] A recent replication attempt failed:
From DC1 to DC4
Naming Context: CN=Configuration,DC=concord,DC=com
The replication generated an error (8524):
Win32 Error 8524
The failure occurred at 2015-10-10 00:49:47.
The last success occurred at 2015-10-10 00:29:47.
1 failures have occurred since the last success.
The guid-based DNS name 5d8285c5-071e-4968-8c56-cd91925ba31c._msdcs.
concord.com
is not registered on one or more DNS servers.
Unable to connect to the NETLOGON share! (\DC4netlogon)
[DC4] An net use or LsaPolicy operation failed with error 1203, Win32 E
rror 1203.
……………………. DC4 failed test NetLogons
Fatal Error:DsGetDcName (DC4) call failed, error 1355
The Locator could not find the server.
……………………. DC4 failed test Advertising
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.
……………………. DC4 failed test frsevent
An Error Event occured. EventID: 0xC00038BB
Time Generated: 10/10/2015 00:48:52
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC00110CD
Time Generated: 10/10/2015 00:49:00
Event String: The computer running the WINS server does not
An Error Event occured. EventID: 0x00000411
Time Generated: 10/10/2015 00:49:07
Event String: The DHCP service is not servicing any clients
An Error Event occured. EventID: 0xC0001B6F
Time Generated: 10/10/2015 00:50:25
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0001B70
Time Generated: 10/10/2015 00:50:25
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000423
Time Generated: 10/10/2015 00:55:17
Event String: The DHCP service failed to see a directory server
……………………. DC4 failed test systemlog
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located — All GC’s are 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 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.
……………………. concord.com failed test FsmoCheck

Ситуация усугубляется еще тем, что еще и Exchange 2010 с самого падения DC1 стоит колом. Очень надеюсь на вашу скорейшую помощь, вплоть до денежного вознаграждения, иначе мне край

UPD: Проблема решилась следующим образом:
1. Выравнивание SOA DNS-серверов исправлением настроек
2. Восстановление SYSVOL при помощи burflag D4 — на основном и затем D2 — на вторичных.
Всем спасибо за советы!
Отдельное спасибо poor_sysadm !