This problem can be solved with Intralink. However, the way licensing (is this a word?) and Intralink work you would have to pick one of the databases to be the only database and you would have to remain connected all the time. Then, you would check in and out while setting the common space status and updating as necessary.
Even better is a product offered free (yes free) from PTC for current maintenance customers. I have only used it once for a single part so I can't vouch for how well it works or any potential limits it might have in terms of file size or number. What you do is set up a project and share it through PTCs server. As far as I can tell it is best suited for projects and not for full time use. However, with careful management it might work for you. Just use it for active projects while keeping legacy files on one of the servers acting as the master.
This is the website where you can check it out:
We are currently working with our manufacturing facility in a
> different state, and as it stands now, they have a "copy" of our
> instruments database on their server, and we have one on ours.
>
> Theoretically, if either of us make changes to files, we are supposed
> to FTP the files to each other so that each database stays in synch.
> Needless to say, the databases have now become different, and it is
> not as easy as picking one to be the master, we need to do a
> comparision on assemblies, parts, drawings, familiy tables, etc so
> create a most up to date master database.
>
> Does anyone have experience with how to do this with Intralink?
>
> Thanks
>
> Mike