SQL 2000 Transactional over VPN

Tech-Archive recommends: Fix windows errors by optimizing your registry

We have a 10 GB database replicating to a disaster recovery site using
transaction replication.

We are using SQL Server 2000 SP3a (8.00.760)

When we tried to recreate the subscription this past weekend, it would not
initialize. It would take between 10-11 hours to complete the initialization
and it failed 7 times.

All of the failures occurred between 8 & 9 hours into the initialization.

There are 134 articles and it populated all but the last 20 tables several
times, but kept failing.

It appears that the failure occurs when the VPN resynchronizes.

The error message is

General network error. Check your network documentation.
(Source: <servername> (Data source); Error number: 11)

The retry error is

SQL Server does not exist or access denied.
(Source: <servername> (Data source); Error number: 17)

1) Why doesn't a subscription initialization pick up where it left off
instead of starting all over again?

2) What agent profile settings could be changed in the agent to avoid having
it start all over again?
e.g., -QueryTimeOut
-LoginTimeOut
-PollingInterval

.

Relevant Pages