Indirect synchronization setup with no synchronizers on servers

In another thread that is getting very long, jacksonmacd suggested a
method for using indirect synchronization in a scenario where remote
PCs have synchronizers but the server does not.

OK. Let's pursue that suggestion. General setup: Four LANs that are
connected via WANs. One LAN server is the main server for the entire
setup and is where I've been told I can place all of may application
files.

Assume Jet Synchronizer is installed on user PCs. Assume that it
CANNOT be installed on any server. Assume further that we have to use
one of the user's remote PCs as the indirect sync hub for each LAN.

I don't understand the messaging in this setup. The problem with any
PC on the LAN is that you can't see it. You can only see the servers.
So does this mean that:

1) there needs to be a dropbox on a server contained within each LAN.
Each user of the app will have a synchronizer. That synchronizer will
send messages to the common dropbox located on the LAN server. Or is
the suggestion to use direct synchronization for computers within each
LAN. If I can get IT to approve synchronizers, then I would want to
use indirect synchronization. After the beating I've taken about
possibly using direct syncing why would I want to use it between remote
PCs within the same LAN, when indirect syncing is a viable option.

2) The designated user's machine on each LAN is the one that will
initiate the syncing of the dropbox message(s) with the replica farm on
the respective LAN server. However, presumably this user is also using
my app. Can his/her synchronizer handle both tasks (i.e. sending
messages from the PC to the server dropbox and syncing the messages in
the server common dropbox with the replica farm on the LAN server?).
If so, why can't any user's synchronizer do this. After all, all user's
synchronizers are sending messages to the common dropbox on the LAN
server (unless the idea was to use direct syncing within each LAN).

3) Then we need to synchronize the replica farms on each individual LAN
with the replica farm on the main server for this entire setup (the
central server for this setup of LANs). How is this initiated?


I think I can see how the topology works on this, but I'm unclear on
how the synchronizers will work since there are none on the LAN servers.

.

Relevant Pages

  • Re: Homegrown synchronization
    ... Further IT has not approved the Jet Synchronizer for use and it ... Show them the Jet Replication security update. ... concerned about mass deletions bloating the replicated backend. ... the backup/compact/update server backend app. ...
    (microsoft.public.access.replication)
  • Re: Indirect synchronization setup with no synchronizers on servers
    ... Replica Manager to be installed at all. ... trust any LAN, except the LAN where the file server is that stores my ... remote PCs have synchronizers but the server does not. ... There is no difference between a synchronizer operating on replicas ...
    (microsoft.public.access.replication)
  • Re: Win2003 Server & WinXP Pro - What kind and how many CALs are requi
    ... How many users have you got and how many will be working on the PCs at the ... > and serving as a network file server. ... > are currently successfully running on 2 different machines on the LAN. ...
    (microsoft.public.windows.server.setup)
  • Re: Remote Desktop Connect to client wont work
    ... You say you have tried this from the server, and I assume it did not work ... I suppose that RWW and VPN have ports open and forwarded to the ... LAN Server. ... If it works inside the LAN then the local PCs ...
    (microsoft.public.windows.server.sbs)
  • Re: Indirect Synchronization without Synchronizer on Server
    ... Can a synchronizer on a remote machine grab a message from a dropbox on ... a server; said server not having a synchronizer on it. ...
    (microsoft.public.access.replication)