showstopping Project Server/collaborative editing problems

i am suffering extreme frustration with collaborative editing.

i have now got a separate project server working and two client machines (running same studio version of Resolve - 17 beta 9) can both open a project stored on that project server. i have opened both relevant ports (ie 5432 and 50059) on all three machines, and even tried switching all the firewalls off (very briefly), but still the following happens:

if the creator of the project has the project open, then i can open that project on my desktop, but i cannot edit it (it has collaboration enabled). either way, after 21 seconds i get a blocking popup message which says:

"Cannot Enable Collaboration - Please ensure that the machiens are not connected using a VPN [they are not] and that DaVinci Resolve is not being blocked by the system firewall."

as mentioned i have even tried switching all firewalls off, so i think this is not the issue. if the project creator does not have their project open then i can even edit the project for 21 seconds and save the work - before i get the same error message, and once i click OK, the project disappears from screen (though it is still safely on the project server - with my new edits).

also, the messaging system does not seem to work properly at all. this may or may not be linked to the the other problems.

has anybody else actually got two projects working simultaneously on two different machines so that they can be edited and not constantly crash/disappear?

thanks, julian

[Shrinivas Ramani]

Julian,

What are the IP addresses for each machine? And for the project server? Can I check if they're on the same subnets? If the project server (or one of the other machines) has multiple ethernet interfaces, can I check if the correct one i being used by postgreSQL?

For collaboration projects, it is important that the project be set in collaboration mode before it starts to be used.

Regards
Shrinivas

thanks for your reply, Shrinivas. for reasons i cannot explain, the timeout problem stopped the next morning, and so far, thank goodness, it hasn't come back.
i have now installed v17 production version, but this was after the problem went away.
i did have a real struggle with ports and the windows firewall, but i think i have a good arrangement now. my remaining worry is that the situation will not be stable, but i will discover that in the coming days.
julian