Thanks Mike,

I realized I didn't mention two things in the design:

- There are two subscribers on this publication (so 2 distrib.exe): one is the matter of concern, and is local to the publisher, in the same room (both in London).

- The second one is based in Germany, subscribing to the same amount of data, and runs perfectly with no latency and a 600 cmds/sec rate.

Both distributors are running under the same profile, and the only difference in their parameters is that the distrib for the remote subscriber uses SQL authentification (-SubscriberLogin + -SubscriberPassword), whereas the local one uses integrated authent on behalf of the SQL Agent account.

This is nonsense I know.

The other factor is that the publication was created with @immediate_sync = 0 to avoid the snapshot agent to create an entire snapshot each time it resynchronizes the subscribers. (when I add a article or when I change a column in an article, remember the publisher is SQL 2000).

Thanks

David B.