Shulou(Shulou.com)06/02 Report--

The company has 2 servers

1. BICSVR08R2H additional domain controller 192.168.1.16

2. DC_BIC08R2 primary domain controller 192.168.1.219

The following phenomena occur when these two domain controllers are replicated:

The primary domain controller DC_BIC08R2 replicates the OK from the additional domain controller BICSVR08R2H

Additional domain controller BICSVR08R2H replicates X from primary domain controller DC_BIC08R2

As shown in the following figure:

In order to solve this problem, I compared the reference documents given by Microsoft on the official website, but in the end, it seems that

Can't solve the problems I face.

Prior to this, a series of attempts have been made, such as (DNS check / redo; restart netlogon; or even

Even the additional domain controller has been knocked down and done all over again.

When I was almost in despair, I decided to put this aside in advance and have a good night's sleep.

Feel. Maybe you may wake up the next day to clear your head and have inspiration.

When I went to work the next morning, I slowly remembered all the operations I had done on the server.

Played it back (some time ago, the blackmail virus ransacked the port 135 137 139 445 and so on.

Time paused here for a few seconds and seemed to see a bright light vaguely. I remember.

Later, for some reason, the port 137 139 445 was unsealed, but not 135.

Try again:

Step 1

Execute the TELNET command

Telnet 192.168.1.16 135 X

Telnet 192.168.1.219 135 OK

Step 2

Netstat-an | more checks whether the port is listening.

Step 3

Check IP security policies on local computer

That's the problem. This time I directly set Deny_135_137_139_445 to be unassigned (

Previously, only 137 139 445 was deleted from it, and then on the Active Directory site

And service to test again.

As shown in the following figure (so far the failure has been resolved):

Summary:

Because replication between domain controllers is disabled when using IP security policies on local computer

The port is used, which leads to a failure during replication.

About 135 / below from Baidu

Port 135is used to remotely open the telnet service of the other party, and to start the RPC connection with the remote computer.

It's easy to hack into the computer. The famous "shock wave" invades using port 135. The function of 135 is to carry out

Remote, malicious code can be written on the remote computer, which is extremely dangerous.

Port 135 is mainly used to use the RPC (Remote Procedure Call, remote procedure call) protocol and provide DCOM (sub-points)

Distributed component object Model) service.

Attach / part of the dcdiag diagnosis in case of failure

C:\ Users\ Administrator > dcdiag

Directory Server Diagnosis

Performing initial setup:

Trying to find home server...

Home Server = dc_bic08r2

* Identified AD Forest.

Done gathering initial info.

Doing initial required tests

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

Starting test: Connectivity

. DC_BIC08R2 passed test Connectivity

Doing primary tests

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

Starting test: Advertising

. DC_BIC08R2 passed test Advertising

Starting test: FrsEvent

. DC_BIC08R2 passed test FrsEvent

Starting test: DFSREvent

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.

. DC_BIC08R2 failed test DFSREvent

Starting test: SysVolCheck

. DC_BIC08R2 passed test SysVolCheck

Starting test: KccEvent

A warning event occurred. EventID: 0x8000082C

Time Generated: 11/07/2017 18:15:37

Event String:

A warning event occurred. EventID: 0x80000828

Time Generated: 11/07/2017 18:18:20

Event String:

Active Directory DNS IP, Active Directory NetBIOS

. DC_BIC08R2 passed test KccEvent

Starting test: KnowsOfRoleHolders

. DC_BIC08R2 passed test KnowsOfRoleHolders

Starting test: MachineAccount

. DC_BIC08R2 passed test MachineAccount

Starting test: NCSecDesc

. DC_BIC08R2 passed test NCSecDesc

Starting test: NetLogons

. DC_BIC08R2 passed test NetLogons

Starting test: ObjectsReplicated

. DC_BIC08R2 passed test ObjectsReplicated

Starting test: Replications

[Replications Check,DC_BIC08R2] A recent replication attempt failed:

From BICSVR08R2HR to DC_BIC08R2

Naming Context: DC=ForestDnsZones,DC=burnet,DC=com

The replication generated an error (1722):

The RPC server is unavailable.

The failure occurred at 2017-11-07 18:17:13.

The last success occurred at 2017-11-07 17:55:58.

1 failures have occurred since the last success.

[BICSVR08R2HR] DsBindWithSpnEx () failed with error 1722

The RPC server is unavailable..

The source remains down. Please check the machine.

[Replications Check,DC_BIC08R2] A recent replication attempt failed:

From BICSVR08R2HR to DC_BIC08R2

Naming Context: DC=DomainDnsZones,DC=burnet,DC=com

The replication generated an error (1722):

The RPC server is unavailable.

The failure occurred at 2017-11-07 18:17:56.

The last success occurred at 2017-11-07 18:05:12.

2 failures have occurred since the last success.

The source remains down. Please check the machine.

[Replications Check,DC_BIC08R2] A recent replication attempt failed:

From BICSVR08R2HR to DC_BIC08R2

Naming Context: CN=Schema,CN=Configuration,DC=burnet,DC=com

The replication generated an error (1722):

The RPC server is unavailable.

The failure occurred at 2017-11-07 18:16:10.

The last success occurred at 2017-11-07 17:55:58.

1 failures have occurred since the last success.

The source remains down. Please check the machine.

[Replications Check,DC_BIC08R2] A recent replication attempt failed:

From BICSVR08R2HR to DC_BIC08R2

Naming Context: CN=Configuration,DC=burnet,DC=com

The replication generated an error (1722):

The RPC server is unavailable.

The failure occurred at 2017-11-07 18:15:49.

The last success occurred at 2017-11-07 18:01:52.

1 failures have occurred since the last success.

The source remains down. Please check the machine.

[Replications Check,DC_BIC08R2] A recent replication attempt failed:

From BICSVR08R2HR to DC_BIC08R2

Naming Context: DC=burnet,DC=com

The replication generated an error (1722):

The RPC server is unavailable.

The failure occurred at 2017-11-07 18:24:03.

The last success occurred at 2017-11-07 18:10:31.

7 failures have occurred since the last success.

The source remains down. Please check the machine.

. DC_BIC08R2 failed test Replications

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.