Nelesh_N
asked on
Ping times between AD replication partners
I have a couple WAN sites whose DC in continuously showing KCC event problems.
Will these response times cause these issues? What is the acceptable response times for replication partners?
Reply from 163.202.149.2: bytes=32 time=29ms TTL=120
Reply from 163.202.149.2: bytes=32 time=21ms TTL=120
Reply from 163.202.149.2: bytes=32 time=23ms TTL=120
Reply from 163.202.149.2: bytes=32 time=22ms TTL=120
Reply from 163.202.149.2: bytes=32 time=74ms TTL=120
Reply from 163.202.149.2: bytes=32 time=14ms TTL=120
Reply from 163.202.149.2: bytes=32 time=22ms TTL=120
Reply from 163.202.149.2: bytes=32 time=17ms TTL=120
Reply from 163.202.149.2: bytes=32 time=29ms TTL=120
Reply from 163.202.149.2: bytes=32 time=47ms TTL=120
Reply from 163.202.149.2: bytes=32 time=34ms TTL=120
Reply from 163.202.149.2: bytes=32 time=25ms TTL=120
Reply from 163.202.149.2: bytes=32 time=46ms TTL=120
Reply from 163.202.149.2: bytes=32 time=35ms TTL=120
Reply from 163.202.149.2: bytes=32 time=237ms TTL=120
Reply from 163.202.149.2: bytes=32 time=258ms TTL=120
Reply from 163.202.149.2: bytes=32 time=322ms TTL=120
Reply from 163.202.149.2: bytes=32 time=89ms TTL=120
Reply from 163.202.149.2: bytes=32 time=101ms TTL=120
Reply from 163.202.149.2: bytes=32 time=268ms TTL=120
Reply from 163.202.149.2: bytes=32 time=145ms TTL=120
Reply from 163.202.149.2: bytes=32 time=40ms TTL=120
Reply from 163.202.149.2: bytes=32 time=31ms TTL=120
Reply from 163.202.149.2: bytes=32 time=27ms TTL=120
Reply from 163.202.149.2: bytes=32 time=53ms TTL=120
Reply from 163.202.149.2: bytes=32 time=66ms TTL=120
Reply from 163.202.149.2: bytes=32 time=38ms TTL=120
Reply from 163.202.149.2: bytes=32 time=34ms TTL=120
Reply from 163.202.149.2: bytes=32 time=23ms TTL=120
Reply from 163.202.149.2: bytes=32 time=31ms TTL=120
Reply from 163.202.149.2: bytes=32 time=34ms TTL=120
Reply from 163.202.149.2: bytes=32 time=17ms TTL=120
Will these response times cause these issues? What is the acceptable response times for replication partners?
Reply from 163.202.149.2: bytes=32 time=29ms TTL=120
Reply from 163.202.149.2: bytes=32 time=21ms TTL=120
Reply from 163.202.149.2: bytes=32 time=23ms TTL=120
Reply from 163.202.149.2: bytes=32 time=22ms TTL=120
Reply from 163.202.149.2: bytes=32 time=74ms TTL=120
Reply from 163.202.149.2: bytes=32 time=14ms TTL=120
Reply from 163.202.149.2: bytes=32 time=22ms TTL=120
Reply from 163.202.149.2: bytes=32 time=17ms TTL=120
Reply from 163.202.149.2: bytes=32 time=29ms TTL=120
Reply from 163.202.149.2: bytes=32 time=47ms TTL=120
Reply from 163.202.149.2: bytes=32 time=34ms TTL=120
Reply from 163.202.149.2: bytes=32 time=25ms TTL=120
Reply from 163.202.149.2: bytes=32 time=46ms TTL=120
Reply from 163.202.149.2: bytes=32 time=35ms TTL=120
Reply from 163.202.149.2: bytes=32 time=237ms TTL=120
Reply from 163.202.149.2: bytes=32 time=258ms TTL=120
Reply from 163.202.149.2: bytes=32 time=322ms TTL=120
Reply from 163.202.149.2: bytes=32 time=89ms TTL=120
Reply from 163.202.149.2: bytes=32 time=101ms TTL=120
Reply from 163.202.149.2: bytes=32 time=268ms TTL=120
Reply from 163.202.149.2: bytes=32 time=145ms TTL=120
Reply from 163.202.149.2: bytes=32 time=40ms TTL=120
Reply from 163.202.149.2: bytes=32 time=31ms TTL=120
Reply from 163.202.149.2: bytes=32 time=27ms TTL=120
Reply from 163.202.149.2: bytes=32 time=53ms TTL=120
Reply from 163.202.149.2: bytes=32 time=66ms TTL=120
Reply from 163.202.149.2: bytes=32 time=38ms TTL=120
Reply from 163.202.149.2: bytes=32 time=34ms TTL=120
Reply from 163.202.149.2: bytes=32 time=23ms TTL=120
Reply from 163.202.149.2: bytes=32 time=31ms TTL=120
Reply from 163.202.149.2: bytes=32 time=34ms TTL=120
Reply from 163.202.149.2: bytes=32 time=17ms TTL=120
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This is normal ping response over Internet. The problem should be packet losts - do you have any ?
Log on to one of the DC's and run a command prompt and type replmon.
Add all the DC's in your Forest/Domain.
Respond back with any errors that you are receiving.
The ping response times look OK.
Also,
Send a Ping with the optional parameter -l 4096 to increase the packet size that you are pinging with.
Add all the DC's in your Forest/Domain.
Respond back with any errors that you are receiving.
The ping response times look OK.
Also,
Send a Ping with the optional parameter -l 4096 to increase the packet size that you are pinging with.
KCC errors are not big error, you have to check which DC is replicating to which dc & is the correct connection objects are created or not.
Also, verify sites & subnet mapping. Check link created for selecting replication partners.
Run repadmin /syncall /A/E/P/D
Above command will sync all the dc,if error comes with any DC will be seen.
Also, verify sites & subnet mapping. Check link created for selecting replication partners.
Run repadmin /syncall /A/E/P/D
Above command will sync all the dc,if error comes with any DC will be seen.