DFSR RPC replication errors 5014 1726 with large files over VPN

i have similar issue ryan in reply http://social.technet.microsoft.com/forums/en-gb/winserverfiles/thread/6d49fd71-2236-4fcb-9763-bf1c03459ee8 cited below. start additional thread here because other 1 related windows server 2003 (r2) , i'm (as ryan) on windows 2008 r2 x64. here first of post ryan:

i've got same problem on 2008 r2 dfsr server. 

the spoke server has 2x intel 1 gigb on-board nics in active/standby teamed configuration.

the hub server (running on vmware using 10gbit vmnet3 nic driver) logs dfsr event 5014 every 2-15mins (usually around 5mins).

the spoke server not log event.

replication running slowly. initial sync/replication. had re-configure replication folder because of lost dfsr database on spoke server. 

could teamed nic on spoke causing error on host?

a note: last time did initial sync on folder processed @ 30k files , hour. time it's doing few hundred and hour.

another note: hub server has several replication groups , connections several spoke servers. none of other connections have problem, none of other spoke servers physical servers or have teamed nic.

thank help.

as stated above problem similar. i'm testing dfsr betweet 3 meshed 2008 r2 x64 servers installed sp1. servers on 3 different sites , connected via asynchronous vpn based on avm fritzbox 16mbin down , 1mbit up. vpn connections works stable (ping -t on netbios names, dns records , ips works charme between hosts , without problems when copying large files, e.g. 10 1gb files via robocopy). dfsr works fine smaller files, in 1 replication group used replicating larger compressed media files (like e.g. avis, vobs or mgeps) testing scenario produces 5014 events followed 5004 events at regular intervals between 5 min , 1 hour. detailled error 1726 (rpc failed) , blows dfsr debug low several mbs errors 1753 , 1726 that:

20110803 11:47:31.932 3792 down 7139 bandwidththrottler::prepareforshutdown preparing shutdown. rgid:55b28e92-8670-42f4-a616-a2ca6e8ccb01 rgname:xxx connid:2c0227f0-96db-41a7-abdd-fc48efc707f8 ptr:0000000005b66980 20110803 11:47:31.932 3792 inco 5777 inconnection::connectnetwork new connection connid:{2c0227f0-96db-41a7-abdd-fc48efc707f8} transport:0000000000000000 unghosttransport:0000000000000000 20110803 11:47:31.932 3792 inco 5780 inconnection::connectnetwork connid:{2c0227f0-96db-41a7-abdd-fc48efc707f8} fatalremoteerror:0 20110803 11:47:31.932 3792 inco 6837 [warn] inconnection::reconnectasync failed connect, (attempts: 142) connid:{2c0227f0-96db-41a7-abdd-fc48efc707f8} error: + [error:9027(0x2343) inconnection::connectnetwork inconnection.cpp:5783 3792 c der remotepartner hat einen fehler gemeldet.] + [error:9027(0x2343) downstreamtransport::establishconnection downstreamtransport.cpp:4123 3792 c der remotepartner hat einen fehler gemeldet.] + [error:9027(0x2343) downstreamtransport::establishconnection downstreamtransport.cpp:4045 3792 c der remotepartner hat einen fehler gemeldet.] + [error:1753(0x6d9) downstreamtransport::establishconnection downstreamtransport.cpp:4045 3792 w in der endpunktzuordnung sind keine weiteren endpunkte verfügbar.] 20110803 11:47:32.946 3264 down 4186 [error] downstreamtransport::establishsession failed on connid:{4583f6f7-f287-40b2-8f41-0698331e79ab} csid:{35a28383-b1fd-467e-b5b0-950a3ee53ef2} rgname:xxx error: + [error:9027(0x2343) downstreamtransport::establishsession downstreamtransport.cpp:4179 3264 c der remotepartner hat einen fehler gemeldet.] + [error:1722(0x6ba) downstreamtransport::establishsession downstreamtransport.cpp:4179 3264 w der rpc-server ist nicht verfügbar.] 20110803 11:47:32.946 3264 inco 2862 inconnection::processerrorstatus reconnecting on remote error. connid:{4583f6f7-f287-40b2-8f41-0698331e79ab} state:connected error: + [error:9027(0x2343) downstreamtransport::establishsession downstreamtransport.cpp:4200 3264 c der remotepartner hat einen fehler gemeldet.] + [error:9027(0x2343) downstreamtransport::establishsession downstreamtransport.cpp:4179 3264 c der remotepartner hat einen fehler gemeldet.] + [error:1722(0x6ba) downstreamtransport::establishsession downstreamtransport.cpp:4179 3264 w der rpc-server ist nicht verfügbar.] 20110803 11:47:32.946 3264 inco 4034 inconnection::reconnect connid:{4583f6f7-f287-40b2-8f41-0698331e79ab} state:connected 20110803 11:47:32.946 3264 inco 4053 [warn] inconnection::reconnect resetting connection. connid:{4583f6f7-f287-40b2-8f41-0698331e79ab} xxx fatal error:[error:1722(0x6ba) downstreamtransport::establishsession downstreamtransport.cpp:4179 3264 w der rpc-server ist nicht verfügbar.] 20110803 11:47:32.946 3264 inco 7715 inconnection::schedulereconnect connid:{4583f6f7-f287-40b2-8f41-0698331e79ab} state:reconnecting 20110803 11:47:32.946 2152 inco 5972 inconnection::disconnect state:reconnecting connid:{4583f6f7-f287-40b2-8f41-0698331e79ab} 20110803 11:47:32.946 2152 inco 5985 inconnection::disconnect transport:0000000008aa52d0 unghosttransport:0000000000000000 20110803 11:47:32.946 2152 down 5558 downstreamtransport::prepareforshutdown ptr:0000000008aa52d0 20110803 11:47:32.946 2152 down 7139 bandwidththrottler::prepareforshutdown preparing shutdown. rgid:4041de95-aea8-45be-b539-c7da194749dc rgname:xxx connid:4583f6f7-f287-40b2-8f41-0698331e79ab ptr:0000000008aa53e0 20110803 11:47:32.946 2528 down 2833 asyncrpchandler::processreceive completion. connid:{61bced33-eda0-45ec-ac29-6a37ce43d5e6} csid:{00000000-0000-0000-0000-000000000000} reqtype:asyncpollrequest reqstate:completed status:1726 ptr:0000000000191290 20110803 11:47:32.946 2528 down 2858 [error] asyncrpchandler::processreceive failed on connid:{61bced33-eda0-45ec-ac29-6a37ce43d5e6} csid:{00000000-0000-0000-0000-000000000000} reqtype:asyncpollrequest reqstate:completed status:1726 error: + [error:9027(0x2343) asyncrpchandler::receiveasyncpoll downstreamtransport.cpp:2199 2528 c der remotepartner hat einen fehler gemeldet.] + [error:9027(0x2343) asyncrpchandler::receiveasyncpoll downstreamtransport.cpp:2141 2528 c der remotepartner hat einen fehler gemeldet.] + [error:1726(0x6be) asyncrpchandler::receiveasyncpoll downstreamtransport.cpp:2141 2528 w der remoteprozeduraufruf ist fehlgeschlagen.]

as far can see problem dfsr tries throttle down replication speed, rpc fails due e.g. many open connections or that. problem tried came across here in forum or searching google, simple don't rid of continous errors preventing replication of larger files.

here list of things tried , more details:

1. reinitialize whole replication group in order make sure database not corrupted (removing members , readding them force initial replication primary member following http://support.microsoft.com/kb/961879)
2. switched off rdc in order make sure there no compression problem compressed avis, mpegs or vobs
3. preeseeding replication group robocopy following http://blogs.technet.com/b/askds/archive/2010/09/07/replacing-dfsr-member-hardware-or-os-part-2-pre-seeding.aspx. after initial replication had finished problem still occured on new large file
4. checked block hole router following http://support.microsoft.com/kb/159211
5. changed mtu setting of ethernet connection based on "ping -f vpn-partner -l xxx" test 1386 (max value unfragmented packets) following http://support.microsoft.com/kb/900926 
6. tried suggestions concerning disabletaskoffload, enabletcpchimney, enabletcpa , enablerss http://qa.social.technet.microsoft.com/forums/en/winserverfiles/thread/d27bd902-034e-4230-9516-0ede42308193, of them not applicable win 2008 r2. tried corresponding netsh commands netsh int ip set global taskoffload=disabled, netsh int tcp set global rss=disabled, netsh interface tcp set global autotuninglevel=disabled , netsh int tcp set global chimney=disabled without success.
7. also followed http://qa.social.technet.microsoft.com/forums/en/winserverfiles/thread/3778427a-a594-4f1d-9c97-d8d1e6a56a83, there no additional security layer besides windows firewall between hosts. 
8. checked staging folder size (currently 75gb) following http://social.technet.microsoft.com/forums/en-us/winserverfiles/thread/d540be96-99cd-43d7-b817-693d6e7e05ea/ quotas (currently deactivated whole drive).
9. also installed newest hotfixes dfs http://support.microsoft.com/kb/968429/ had "an unexpected network error occurred." problem when accessing larger files windows 7 clients. , of course ... still no success 5014, 1726 problem.

so, i'm looking forward suggestions solving tricky problem.

hi,
 
thank question.

i trying involve familiar topic further @ issue. there might time delay. appreciate patience.
 
thank understanding , support.

---

technet subscriber support in forum |if have feedback on our support, please contact tnmff@microsoft.com.

Windows Server  >  File Services and Storage