I have a new Central server and numerous primaries. Some are over good links some bad, so i have some throttling taking place over the bad ones to ensure we dont hog the link. We seem to be seeing that in some instances, usually when we have a package distributing to all site distribution points but not always that way we seem to get some aspects of traffic getting missed ? Effectively take this scenario we have a package going to all site servers distriibution points about 6 primaries from my central server and then someone adds a machine to a collection at Central. This should be replicated to one of my primaries that handles that clients site. waiting even after the packages have reached destination shows me that the collection has not received the change. To force it i have to take that machine out and put it in again. It happenned once or twice and i thought nothing of it but it is happening more and more ? I dont see any errors in Replication manager logs, is it due to the properties of the sender log that say how many times to retry if it fails ? However i thought it would just queue the request up if there were no senders available ? Although i dont think this is the case ? Any help much appreciated

The site concerned has no restrictions bandwidth wise in those settings going up or coming down they are both in the same datacentre, so its not that im afraid.