Hello again. I've not yet asked Bitdefender about this because I may have fixed it. I found that there were already a couple of rules set up in the Bitdefender Firewall. Listed were rules for multiplicityconfig.exe and multipl2.exe. In each case, those executables are allowed to use any port, network, protocol or IP address.
The example in the troubleshooting guide I referred to in my earlier response just says "Multiplicity Service" and a port number. I then had a bright idea... I went and checked the Bitdefender Firewall set up for the secondary. That has an additional rule for multisrv.exe, so I added an identical rule to the master's list of exceptions and it worked to the extent that if I put the master to sleep and then woke it, everything was fine. I shall have a confirmation in the morning when I wake up both systems. All being well it will be 'problem solved'. Fingers crossed...
Many thanks for your help. If it's not fixed, I still have a lot of other leads to follow up from the links you sent me.
Brian
