Merge Replication over internet Problem: Couldn't propagate schema to the subscriber.

Yesterday I posted my problem on the group I would like to explain it
a bit so that I be able to make things more clear.
1. I have set up a Sql server as publisher/Distributor.
2. Setup MSDE as subscriber
3. Login mode to publisher/subscriber/Distributor is Sql Server
Authentication
and Login Name is SUPERVISOR.
4. Setup a merge pull replication over internet, using FTP snapshot to
be
downloaded from my FTP site 61.11.103.3
5. After all this setting I ran merge agent at the subscriber site
(owner of
the agent is SUPERVISOR)using sp_start_job stored procedure.
6. Following is the list of message that I can see in Job history of
merge
agent.
A. Connecting to Subscriber.
B. Connecting to Distributor.
C. Initializing.
D. Connecting to Publisher.
E. Retrieving publication information.
F. retrieving subscription information.
G. Snapshot files will be downloaded via FTP.
H. connecting to FTP site '61'11.103.3'
I. The subscription has been marked for reinitialization,
reinitialization
will occur next time you synchronize this subscription.
J. The Schema script '\\IM19\C$\Program Files\Microsoft Sql
Server\MSSQL\Repldata\FTP\IM19_FTP_REPL_FTPREPL\20 050110104749
\FTPDB_1.sch'could not be propagated to the subscriber.
K.Process could not retrieve file
'IM19_FTP_REPL_FTPREPL\20050110104749
\FTPDB_1.sch' from FTP site 61.11.103.3
L. The schema script could not be propagated to the
subscriber,Access denied:
File not Found.
M. The job failed. The job invoked by supervisor,the last step was
step 1.
Plz help me out, Hilary has mentioned in reply to my last mail to
change owner of the merge agent to 'Sa' but this is not working out
still I m getting the same problem.
Its very urgent and important too..
Ruchir,
Based on the error message it seems ftp login doesn't have the permission to
access the snapshot folder share on your distributor box. Please make sure
that ftp login has read permission to your snapshot folder. You can verify
it by using the ftp get cmd for your ftpdb_1.sch file.
thanks - Deepak
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ruchir" <ruchirdhar@.gmail.com> wrote in message
news:88216eb7.0501102129.51fa8110@.posting.google.c om...
> Yesterday I posted my problem on the group I would like to explain it
> a bit so that I be able to make things more clear.
> 1. I have set up a Sql server as publisher/Distributor.
> 2. Setup MSDE as subscriber
> 3. Login mode to publisher/subscriber/Distributor is Sql Server
> Authentication
> and Login Name is SUPERVISOR.
> 4. Setup a merge pull replication over internet, using FTP snapshot to
> be
> downloaded from my FTP site 61.11.103.3
> 5. After all this setting I ran merge agent at the subscriber site
> (owner of
> the agent is SUPERVISOR)using sp_start_job stored procedure.
> 6. Following is the list of message that I can see in Job history of
> merge
> agent.
> A. Connecting to Subscriber.
> B. Connecting to Distributor.
> C. Initializing.
> D. Connecting to Publisher.
> E. Retrieving publication information.
> F. retrieving subscription information.
> G. Snapshot files will be downloaded via FTP.
> H. connecting to FTP site '61'11.103.3'
> I. The subscription has been marked for reinitialization,
> reinitialization
> will occur next time you synchronize this subscription.
> J. The Schema script '\\IM19\C$\Program Files\Microsoft Sql
> Server\MSSQL\Repldata\FTP\IM19_FTP_REPL_FTPREPL\20 050110104749
> \FTPDB_1.sch'could not be propagated to the subscriber.
> K.Process could not retrieve file
> 'IM19_FTP_REPL_FTPREPL\20050110104749
> \FTPDB_1.sch' from FTP site 61.11.103.3
> L. The schema script could not be propagated to the
> subscriber,Access denied:
> File not Found.
> M. The job failed. The job invoked by supervisor,the last step was
> step 1.
>
> Plz help me out, Hilary has mentioned in reply to my last mail to
> change owner of the merge agent to 'Sa' but this is not working out
> still I m getting the same problem.
> Its very urgent and important too..

Merge Replication not working after 1st Sync

I am really stuck on this, if anyone has some insight into this problem
any help would appreciated...
I'll try to explain what is happening the best I can:
We have a server running Windows Advanced Server 2000 (SP4) w/ SQL
server 2000 (SP3a) (from now on Server A). I have a publication on this
machine with dynamic filters (Changing the HOST_NAME()). The
publication is sending the snapshots to another machine (desktop
machine). The Mobile agent is in the same machine as the snapshots.
The mobile application is syncing fine when hitting Server A. The sync
is done Asynchronously.
Then we have Server B. Running Windows Server 2003 (SP1) w/ SQL 2000
(SP4), same publication w/ dynamic filter however the snapshots and the
mobile agent are in this server.
The mobile application will sync the 1st time but any subsequent syncs
will not work. I check on the Replication monitor and it tells me that
the Merge was a success but the mobile application will not execute the
download table callback, it will execute the Sync callback 5 times and
not proceed in executing the download table callback.
If I change the configuration on the mobile app to point to Server A
the sync will work just fine but, if I change it back to Server B the
sync will work once then it will stop working.
Anyone have some suggestions for troubleshooting?
Update on the situation, it turns out the Sync works fine, what's
going on is that when I sync to Server A, the average sync time is 3
minutes for 2000 rows, on Server B it's taking 45 minutes to sync 1000
rows, any ideas on how to improve/troubleshoot the situation?
I also ran profiler but I have no clue what to search for. In profiler
I couln't find any issues or unless I am not looking for the right
things. Can someone tell me what I can look for in profiler if there
is anything to look for?
Specs for Server A:
CPU: 2 Pentium 3 (550 MHz each)
RAM: 3 GBs
OS: Server 2000 Advanced (SP4)
SQL 2000 SP3
Specs for Server B:
CPU: 2 Xeon Dual-Core (2.8 GHz each)
RAM: 4 GBs
OS: Server 2003 (SP1)
SQL 2000 SP4