Dfs ошибка 5002 - Не ошибается лишь тот, кто ничего не делает!

Event Details
Summary
Causes
Resolutions
- Test basic network connectivity
- Check Firewall settings
- Install the latest updates
Verification
- See Also

Event Details

Product:	Windows Operating System
Event ID:	5002
Source:	DFSR
Version:	Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 R2
Message:	Service encountered an error communicating with partner for Replication Group

Summary

DFS Replication encountered an error while communicating with a replication partner during replication. DFS Replication will retry replication.

Causes

An unhealthy state of this monitor is caused by communication errors during replication. Communication errors can occur for the following reasons:

General network connectivity issues
DNS errors
Firewall settings
Lack of software updates on replication partners

Resolutions

Test basic network connectivity

To test network connectivity with the affected server, use the following procedure:

Open a command prompt window and then use the ping command to check basic network connectivity.

If the ping command fails, it is likely that the server is not running, or has network problems that require local access to resolve. If ping is blocked in your network environment, skip this step.
If the ping command is successful, test the server’s registration in DNS by using the
nslookup command.
If the nslookup command fails, there is a problem with DNS. Check the DNS server health or contact the DNS server administrator.
If the nslookup command succeeds, DNS is working properly.

Note: For more information about troubleshooting network issues, see
article 325487 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?linkid=46059).

Check Firewall settings

If a firewall has been configured between replication partners, ensure that it is not blocking RPC communication. DFS Replication depends on RPC for communication. DFS Replication uses the RPC Endpoint Mapper (port 135) and a randomly assigned dynamic port
in the range of 49152 through 65535 for Windows Server 2008 R2 and Windows Server 2008, or in the range of 1025 through 5000 for Windows Server 2003 R2.

You can use the Dfsrdiag command-line tool to specify a static port instead of the dynamic port. For more information about how to specify the RPC Endpoint Mapper, see
article 154596 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=73991). For more information about dynamic port usage in Windows Server 2008, see
article 929851 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=187092).

Install the latest updates

Install the latest service pack and updates on all members of the replication group.

Verification

To manually confirm that replication is healthy, run a propagation test on the affected folder by using DFS Management or the following commands where <ReplicationGroup>
is the name of the replication group and <ReplicatedFolder>
is the name of the replicated folder:

dfsrdiag propagationtest /rgname:»<ReplicationGroup>» /rfname:»<ReplicatedFolder>» /testfilename:DFS-RTestFile.xml

dfsrdiag propagationreport /rgname:»<ReplicationGroup>» /rfname:»<ReplicatedFolder>» /testfilename:DFS-RTestFile.xml /reportfilename:c:DFS-R_Report.xml

Knowledge Base article 832017, «Service overview and network port requirements for the Windows Server system» (http://go.microsoft.com/fwlink/?LinkId=65336)
Current Hotfixes for Distributed File System (DFS) technologies in Windows Server 2008 and Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkId=140177)

Источник

I was successfully replicating files in the DFS on the same LAN. When I moved the new file server to another LAN and connected via VPN over the WAN replication was not successful. I think I may have some sort of DNS issue…but I’m not sure how
to troubleshoot. I’m going to paste several related system log entries to see if this might show the issue. Any suggestions or tips on how to resolve are appreciated.

I think replication is successfully occurring on one side but NOT on both sides.

Also, it seems to successfully contact the domain.

The two servers are able to ping each other without issue.

Log Name:      DFS Replication
Source:        DFSR
Date:          12/2/2013 7:32:17 AM
Event ID:      1206
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      FSDP2.salesmaster.local
Description:
The DFS Replication service successfully contacted domain controller
\vmdcdpfsmo.salesmaster.local to access configuration information.
Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
<System>
    <Provider Name=»DFSR» />
    <EventID Qualifiers=»16384″>1206</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=»2013-12-02T12:32:17.000000000Z» />
    <EventRecordID>2101</EventRecordID>
    <Channel>DFS Replication</Channel>
    <Computer>FSDP2.salesmaster.local</Computer>
    <Security />
</System>
<EventData>
    <Data>\vmdcdpfsmo.salesmaster.local</Data>
</EventData>
</Event>

====================================================

Log Name:      DFS Replication
Source:        DFSR
Date:          12/2/2013 7:32:26 AM
Event ID:      5002
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      FSDP2.salesmaster.local
Description:
The DFS Replication service encountered an error communicating with partner FS3 for replication group FileServers2.

Partner DNS address: FS3.salesmaster.local

Optional data if available:
Partner WINS Address: FS3
Partner IP Address: 192.168.7.30

The service will retry the connection periodically.

Additional Information:
Error: 9032 (The connection is shutting down)
Connection ID: 07D60A4A-E0D7-454E-99B0-57A14BA9E923
Replication Group ID: B16DE925-8185-4038-843D-498D30D022F2
Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
<System>
    <Provider Name=»DFSR» />
    <EventID Qualifiers=»49152″>5002</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=»2013-12-02T12:32:26.000000000Z» />
    <EventRecordID>2102</EventRecordID>
    <Channel>DFS Replication</Channel>
    <Computer>FSDP2.salesmaster.local</Computer>
    <Security />
</System>
<EventData>
    <Data>07D60A4A-E0D7-454E-99B0-57A14BA9E923</Data>
    <Data>FS3</Data>
    <Data>FileServers2</Data>
    <Data>FS3.salesmaster.local</Data>
    <Data>FS3</Data>
    <Data>192.168.7.30</Data>
    <Data>9032</Data>
    <Data>The connection is shutting down</Data>
    <Data>B16DE925-8185-4038-843D-498D30D022F2</Data>
</EventData>
</Event>

====================================================

Log Name:      DFS Replication
Source:        DFSR
Date:          12/2/2013 7:40:57 AM
Event ID:      5002
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      FSDP2.salesmaster.local
Description:
The DFS Replication service encountered an error communicating with partner FS3 for replication group FileServers2.

Partner DNS address: FS3.salesmaster.local

Optional data if available:
Partner WINS Address: FS3
Partner IP Address: 192.168.7.30

The service will retry the connection periodically.

Additional Information:
Error: 9032 (The connection is shutting down)
Connection ID: 07D60A4A-E0D7-454E-99B0-57A14BA9E923
Replication Group ID: B16DE925-8185-4038-843D-498D30D022F2
Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
<System>
    <Provider Name=»DFSR» />
    <EventID Qualifiers=»49152″>5002</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=»2013-12-02T12:40:57.000000000Z» />
    <EventRecordID>2103</EventRecordID>
    <Channel>DFS Replication</Channel>
    <Computer>FSDP2.salesmaster.local</Computer>
    <Security />
</System>
<EventData>
    <Data>07D60A4A-E0D7-454E-99B0-57A14BA9E923</Data>
    <Data>FS3</Data>
    <Data>FileServers2</Data>
    <Data>FS3.salesmaster.local</Data>
    <Data>FS3</Data>
    <Data>192.168.7.30</Data>
    <Data>9032</Data>
    <Data>The connection is shutting down</Data>
    <Data>B16DE925-8185-4038-843D-498D30D022F2</Data>
</EventData>
</Event>

=========================================================

Log Name:      DFS Replication
Source:        DFSR
Date:          12/2/2013 7:56:00 AM
Event ID:      5002
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      FSDP2.salesmaster.local
Description:
The DFS Replication service encountered an error communicating with partner FS3 for replication group FileServers2.

Partner DNS address: FS3.salesmaster.local

Optional data if available:
Partner WINS Address: FS3
Partner IP Address: 192.168.7.30

The service will retry the connection periodically.

Additional Information:
Error: 9032 (The connection is shutting down)
Connection ID: 07D60A4A-E0D7-454E-99B0-57A14BA9E923
Replication Group ID: B16DE925-8185-4038-843D-498D30D022F2
Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
<System>
    <Provider Name=»DFSR» />
    <EventID Qualifiers=»49152″>5002</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=»2013-12-02T12:56:00.000000000Z» />
    <EventRecordID>2104</EventRecordID>
    <Channel>DFS Replication</Channel>
    <Computer>FSDP2.salesmaster.local</Computer>
    <Security />
</System>
<EventData>
    <Data>07D60A4A-E0D7-454E-99B0-57A14BA9E923</Data>
    <Data>FS3</Data>
    <Data>FileServers2</Data>
    <Data>FS3.salesmaster.local</Data>
    <Data>FS3</Data>
    <Data>192.168.7.30</Data>
    <Data>9032</Data>
    <Data>The connection is shutting down</Data>
    <Data>B16DE925-8185-4038-843D-498D30D022F2</Data>
</EventData>
</Event>

========================================================

Log Name:      DFS Replication
Source:        DFSR
Date:          12/2/2013 8:56:13 AM
Event ID:      5002
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      FSDP2.salesmaster.local
Description:
The DFS Replication service encountered an error communicating with partner FS3 for replication group FileServers2.

Partner DNS address: FS3.salesmaster.local

Optional data if available:
Partner WINS Address: FS3
Partner IP Address: 192.168.7.30

The service will retry the connection periodically.

Additional Information:
Error: 9032 (The connection is shutting down)
Connection ID: 07D60A4A-E0D7-454E-99B0-57A14BA9E923
Replication Group ID: B16DE925-8185-4038-843D-498D30D022F2
Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
<System>
    <Provider Name=»DFSR» />
    <EventID Qualifiers=»49152″>5002</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=»2013-12-02T13:56:13.000000000Z» />
    <EventRecordID>2105</EventRecordID>
    <Channel>DFS Replication</Channel>
    <Computer>FSDP2.salesmaster.local</Computer>
    <Security />
</System>
<EventData>
    <Data>07D60A4A-E0D7-454E-99B0-57A14BA9E923</Data>
    <Data>FS3</Data>
    <Data>FileServers2</Data>
    <Data>FS3.salesmaster.local</Data>
    <Data>FS3</Data>
    <Data>192.168.7.30</Data>
    <Data>9032</Data>
    <Data>The connection is shutting down</Data>
    <Data>B16DE925-8185-4038-843D-498D30D022F2</Data>
</EventData>
</Event>

Источник

Good Morning Windows Gurus,

I am running into a challenge with our DFS Replication where I am daily getting multiple alerts about the service stopping communication with the partner controller because the replication is being Paused for backup or restore. We are running Server 2012 R2 in a vmware vsphere installation. Messages below.

Text

The DFS Replication service is stopping communication with partner BV-DC1 for replication group Domain System Volume due to an error. The service will retry the connection periodically. 
 
Additional Information: 
Error: 9036 (Paused for backup or restore) 
Connection ID: E14D9BA1-6EBD-43BF-95B4-591C1773EA6D 
Replication Group ID: 7C857D6F-15C8-4C74-BDC6-1A49065B34B0

Text

The DFS Replication service encountered an error communicating with partner BV-DC1 for replication group Domain System Volume. 
 
Partner DNS address: BV-DC1.busd.loc 
 
Optional data if available: 
Partner WINS Address: BV-DC1 
Partner IP Address: 10.2.16.202 
 
The service will retry the connection periodically. 
 
Additional Information: 
Error: 9036 (Paused for backup or restore) 
Connection ID: E14D9BA1-6EBD-43BF-95B4-591C1773EA6D 
Replication Group ID: 7C857D6F-15C8-4C74-BDC6-1A49065B34B0

I have temporarily paused Veeam backups of the FSMO server to rule out the service causing the interruption. I have also ran the AD Replication Status tool and everything comes back clean. AD is replicating. Do I need to stress over these errors? They seem pretty numerous given my past experience with Windows Server.

Thank you very much for your time. Happy Wednesday.

Источник

Имеется контроллер домена DC01 на Windows Server 2012 R2 (уровень доменалеса 2012 R2) со всеми ролями FSMO, DNS, а также он DHCP.

PS C:Windowssystem32> netdom /query fsmo
Хозяин схемы                DC01.*.*.*
Хозяин именования доменов   DC01.*.*.*
PDC                         DC01.*.*.*
Диспетчер пула RID          DC01.*.*.*
Хозяин инфраструктуры       DC01.*.*.*
Команда выполнена успешно.

В журнале DFS появляется ошибка —

Имя журнала:   DFS Replication
Источник:      DFSR
Дата:          07.04.2014 11:35:47
Код события:   6002
Категория задачи:Отсутствует
Уровень:       Ошибка
Ключевые слова:Классический
Пользователь:  Н/Д
Компьютер:     DC01.*.*.*
Описание:
Служба репликации DFS обнаружила недопустимые данные объекта 
msDFSR-Subscriber при запросе  сведений о конфигурации. 
 
Дополнительные сведения: 
DN объекта: CN=Domain System Volume,CN=DFSR-LocalSettings,CN=DC01,
OU=Domain Controllers,DC=*,DC=*,DC=* 
Имя атрибута: msDFSR-MemberReference 
Контроллер домена: DC01.*.*.*
Цикл запроса: 60 мин
Xml события:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="DFSR" />
    <EventID Qualifiers="49152">6002</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-07T08:35:47.000000000Z" />
    <EventRecordID>276</EventRecordID>
    <Channel>DFS Replication</Channel>
    <Computer>DC01.*.*.*</Computer>
    <Security />
  </System>
  <EventData>
    <Data>msDFSR-Subscriber</Data>
    <Data>CN=Domain System Volume,CN=DFSR-LocalSettings,CN=DC01,
OU=Domain Controllers,DC=*,DC=*,DC=*</Data>
    <Data>msDFSR-MemberReference</Data>
    <Data>DC01.*.*.*</Data>
    <Data>60</Data>
  </EventData>
</Event>

Также имеется второй контроллер домена DC00, также Windows Server 2012 R2, на нем не появились шары SYSVOL и NETLOGON, в журнале следующее

Имя журнала:   DFS Replication
Источник:      DFSR
Дата:          07.04.2014 17:01:43
Код события:   4612
Категория задачи:Отсутствует
Уровень:       Ошибка
Ключевые слова:Классический
Пользователь:  Н/Д
Компьютер:     DC00.*.*.*
Описание:
Служба репликации DFS инициализировала SYSVOL по локальному 
пути C:WindowsSYSVOLdomain и готова к начальной репликации. 
Реплицированная папка останется в состоянии начальной синхронизации 
до выполнения репликации со своим партнером DC01.*.*.*. 
Если в это время выполнялось назначение сервера контроллером домена, 
контроллер домена не будет делать объявления и функционировать как 
контроллер домена, пока данная проблема не будет решена. Это могло 
произойти, если указанный партнер также находится в состоянии начальной 
синхронизации или обнаружены нарушения общего доступа на этом сервере 
или партнере синхронизации. Если данное событие произошло в результате 
миграции SYSVOL от службы репликации файлов (FRS) к репликации DFS, изменения 
не будут реплицироваться до тех пор, пока эта проблема не будет решена. 
В результате этого папка SYSVOL на данном сервере может стать не 
синхронизированной с другими контроллерами домена. 
  
Дополнительные сведения:  
Имя реплицированной папки: SYSVOL Share 
Идентификатор реплицированной папки: C0D02335-2516-4027-A9CA-0B86A386E210 
Имя группы репликации: Domain System Volume 
Идентификатор группы репликации: 5F0F06CC-E904-4E94-9ED2-9C70D442AD3B 
Код участника: 22614947-BBFD-4BE5-BBE0-20E99675B0B1 
Только для чтения: 0
Xml события:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="DFSR" />
    <EventID Qualifiers="49152">4612</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-07T14:01:43.000000000Z" />
    <EventRecordID>88</EventRecordID>
    <Channel>DFS Replication</Channel>
    <Computer>DC00.*.*.*</Computer>
    <Security />
  </System>
  <EventData>
    <Data>C0D02335-2516-4027-A9CA-0B86A386E210</Data>
    <Data>C:WindowsSYSVOLdomain</Data>
    <Data>SYSVOL Share</Data>
    <Data>Domain System Volume</Data>
    <Data>5F0F06CC-E904-4E94-9ED2-9C70D442AD3B</Data>
    <Data>22614947-BBFD-4BE5-BBE0-20E99675B0B1</Data>
    <Data>DC01.*.*.*y</Data>
    <Data>0</Data>
  </EventData>
</Event>

Имя журнала:   DFS Replication
Источник:      DFSR
Дата:          07.04.2014 17:01:43
Код события:   5002
Категория задачи:Отсутствует
Уровень:       Ошибка
Ключевые слова:Классический
Пользователь:  Н/Д
Компьютер:     DC00.*.*.*
Описание:
Служба репликации DFS обнаружила ошибку в подключении к 
партнеру DC01 для группы репликации Domain System Volume. 
 
DNS-адрес партнера: DC01.*.*.*
 
Доступные дополнительные сведения: 
WINS-адрес партнера: DC01 
IP-адрес партнера: 192.168.50.53 
  
Служба периодически будет пытаться установить подключение. 
 
Дополнительные сведения: 
Ошибка: 1753 (В системе отображения конечных точек не 
осталось доступных конечных точек.) 
Идентификатор подключения: 5F0F06CC-E904-4E94-9ED2-9C70D442AD3B 
Идентификатор группы репликации: D687A311-7DA0-48CC-8176-859049523817
Xml события:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="DFSR" />
    <EventID Qualifiers="49152">5002</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-07T14:01:43.000000000Z" />
    <EventRecordID>87</EventRecordID>
    <Channel>DFS Replication</Channel>
    <Computer>DC00.*.*.*</Computer>
    <Security />
  </System>
  <EventData>
    <Data>5F0F06CC-E904-4E94-9ED2-9C70D442AD3B</Data>
    <Data>DC01</Data>
    <Data>Domain System Volume</Data>
    <Data>DC01.*.*.*</Data>
    <Data>DC01</Data>
    <Data>192.168.50.53</Data>
    <Data>1753</Data>
    <Data>В системе отображения конечных точек не осталось 
доступных конечных точек.</Data>
    <Data>D687A311-7DA0-48CC-8176-859049523817</Data>
  </EventData>
</Event>

Решения из гугла не помогли. Если нужна еще какая-то информация — предоставлю.

Источник

when I check one of the dc with dcdiag the results are as follows :

Directory Server Diagnosis

Performing initial setup:
* Identified AD Forest.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-NameAD4
Starting test: Connectivity
……………………. AD4 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-NameAD4

Starting test: DNS

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

Running partition tests on : ForestDnsZones

Running partition tests on : DomainDnsZones

Running partition tests on : Schema

Running partition tests on : Configuration

Running partition tests on : domain

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

DC: AD4.domain.local
Domain: domain.local

TEST: Dynamic update (Dyn)
Warning: Failed to add the test record dcdiag-test-record in zone domain.local

TEST: Records registration (RReg)
Network Adapter [00000018] XenServer PV Network Device:
Warning:
Missing SRV record at DNS server 192.168.100.4:
_kerberos._tcp.dc._msdcs.domain.local

Warning:
Missing SRV record at DNS server 192.168.100.4:
_kerberos._tcp.domain.local

Warning:
Missing SRV record at DNS server 192.168.100.4:
_kerberos._udp.domain.local

Warning:
Missing SRV record at DNS server 192.168.100.4:
_kpasswd._tcp.domain.local

Warning:
Missing SRV record at DNS server 192.168.100.4:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.domain.local

Warning:
Missing SRV record at DNS server 192.168.100.4:
_kerberos._tcp.Default-First-Site-Name._sites.domain.local

Warning:
Missing SRV record at DNS server 192.168.100.4:
_ldap._tcp.gc._msdcs.domain.local

Warning:
Missing A record at DNS server 192.168.100.4:
gc._msdcs.domain.local

Warning:
Missing SRV record at DNS server 192.168.100.14:
_kerberos._tcp.dc._msdcs.domain.local

Warning:
Missing SRV record at DNS server 192.168.100.14:
_kerberos._tcp.domain.local

Warning:
Missing SRV record at DNS server 192.168.100.14:
_kerberos._udp.domain.local

Warning:
Missing SRV record at DNS server 192.168.100.14:
_kpasswd._tcp.domain.local

Warning:
Missing SRV record at DNS server 192.168.100.14:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.domain.local

Warning:
Missing SRV record at DNS server 192.168.100.14:
_kerberos._tcp.Default-First-Site-Name._sites.domain.local

Warning:
Missing SRV record at DNS server 192.168.100.14:
_ldap._tcp.gc._msdcs.domain.local

Warning:
Missing A record at DNS server 192.168.100.14:
gc._msdcs.domain.local

Error: Record registrations cannot be found for all the network adapters

Summary of DNS test results:

Auth Basc Forw Del Dyn RReg Ext
_________________________________________________________________
Domain: domain.local
AD4 PASS PASS PASS PASS WARN FAIL n/a

……………………. domain.local failed test DNS

Содержание

The dfs replication service encountered an error communicating with partner
Answered by:
Question
The dfs replication service encountered an error communicating with partner
Asked by:
Question
All replies
The dfs replication service encountered an error communicating with partner
Answered by:
Question
Answers
All replies

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I have installed windows 2008 R2 x64 on two servers and deployed DFS-Replication. Error 5014, 5008,5002 keeps on coming after certain days and replication starts after it. I’m worried why these error are occuring. can anyone help?

EVENT 5014

The DFS Replication service is stopping communication with partner EKTW2K8FSRV2 for replication group Photos due to an error. The service will retry the connection periodically.
Additional Information:

Error: 1723 (The RPC server is too busy to complete this operation.)

Connection ID: 17ED06AD-C3FD-40E1-ABAB-73139A5C0097

Replication Group ID: E980F065-7465-4523-A899-293133BEFDAA

EVENT 5008The DFS Replication service failed to communicate with partner EKTW2K8FSRV2 for replication group Photos. This error can occur if the host is unreachable, or if the DFS Replication service is not running on the server.

Partner DNS Address: EKTW2K8FSRV2.snpl.net.np

Optional data if available:

Partner WINS Address: EKTW2K8FSRV2

Partner IP Address: 192.168.70.126

The service will retry the connection periodically.

Error: 1722 (The RPC server is unavailable.)

Connection ID: 17ED06AD-C3FD-40E1-ABAB-73139A5C0097

Replication Group ID: E980F065-7465-4523-A899-293133BEFDAA

EVENT 5002

The DFS Replication service encountered an error communicating with partner EKTW2K8FSRV2 for replication group Photos.

Partner DNS address: EKTW2K8FSRV2.snpl.net.np

Optional data if available:

Partner WINS Address: EKTW2K8FSRV2

Partner IP Address: 192.168.70.126

The service will retry the connection periodically.

Error: 1753 (There are no more endpoints available from the endpoint mapper.)

Connection ID: 17ED06AD-C3FD-40E1-ABAB-73139A5C0097

Replication Group ID: E980F065-7465-4523-A899-293133BEFDAA

EVENT 5004

The DFS Replication service successfully established an inbound connection with partner EKTW2K8FSRV2 for replication group Information.

Connection Address Used: EKTW2K8FSRV2.snpl.net.np

Connection ID: 455CB401-0DAF-4BA6-882C-8E0206C3A6A9

Replication Group ID: B4BA1C7A-378E-4DE0-8522-CB9BB9E0B192

Источник

The dfs replication service encountered an error communicating with partner

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

When check repadmin /replsum and netdom query fsmo via command line output :

The system cannot find the file specified.

The command failed to complete successfully.

When I check log in event viewer

The DFS Replication service encountered an error communicating with partner for replication group Domain System Volume.

When I test replicate now domain controller :

Mark the answer if it helps you.

I can’t access DCs

Mark the answer if it helps you.

Might want to check that the DNS is OK and is resolved (both Forward and Reverse).

Also check the health of the Domain Controller with the dcdiag commands.
Dcdiag: How to Check Domain Controller Health

You’ll also reach more DFS Replication experts in the dedicated forum over here:
Windows Server > File Services and Storage

Best regards,
Leon

Blog: https://thesystemcenterblog.com LinkedIn:

Mark the answer if it helps you.

when I check one of the dc with dcdiag the results are as follows :

Directory Server Diagnosis

Performing initial setup:
* Identified AD Forest.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-NameAD4
Starting test: Connectivity
. AD4 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-NameAD4

Starting test: DNS

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