Multiplicity 4 fails clipboard and file copy on Win 11 **SOLVED**

Hello,

Sorry to hear you are having issues. I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience. Thank you.

Basj,

Stardock Community  Assistant

This would typically be a firewall issue.

When copying data from machine B to machine A, a connection is made from A to B.  This is typically the reverse of mouse/keyboard data so a firewall blocking can cause this to fail.

Another possibility is you have a tool on the secondary which is blocking Multiplicity from being able to determine what machine to contact.  Tailscale is known to break this even when not in use.  We are planning to tweak how we send data for that to try and address that in an update but it requires a protocol change..

Do either of these explain the problem?

We will look into the leak.

Thank you for your response. The issue is now RESOLVED, with solution below.
(Pre-History; Multiplicity v4 installed on Primary with network on Private (always), same with secondary computers, but regardless of that, remote control worked fine but file copying was erratic.)

Using the Powershell code in SOLUTION, I found this on my primary computer

Multiplicity Service                                           True   Inbound  Allow Domain, Private
Multiplicity Clipboard                                         True   Inbound  Allow Domain, Private
Multiplicity Audio Service                                     True   Inbound  Allow Domain, Private
Multiplicity Application (clipboard)                           True   Inbound  Allow Domain, Private
Multiplicity Remote Screen Service                             True   Inbound  Allow Domain, Private
Multiplicity Application (Remote screen control)               True   Inbound  Allow Domain, Private
Multiplicity Application (Remote screen control)               True   Inbound  Allow Domain, Private
Multiplicity Remote Screen Service                             True   Inbound  Allow Domain, Private
Multiplicity Application (Remote screen control)               True   Inbound  Allow Domain, Private
Multiplicity Application (Remote screen control)               True   Inbound  Allow Domain, Private
Multiplicity Application (main)                                True   Inbound  Allow Domain, Private
Multiplicity Audio Service                                     True   Inbound  Allow Domain, Private
Multiplicity Service                                           True   Inbound  Allow Domain, Private
Stardock Multiplicity 4                                        True   Inbound  Allow          Public
Stardock Multiplicity 4                                        True   Inbound  Allow          Public
Stardock Multiplicity 4                                        True   Inbound  Block         Private
Stardock Multiplicity 4                                        True   Inbound  Block         Private

There is NO good reason why Multiplicity is Blocked, but I ask Stardock to consider a tool that checks and reports the Firewall settings of their product. 

On a clean install on a private network, the firewall should be set to Allow, not Block. Also brief user instructions can be included that make fixing the issue easy OR an in-app Multiplicity only Firewall setting changer would do wonders.

SOLUTION;

To those who need help to check/fix your blocked Multiplicity firewall settings under Windows, do this;

First check your firewall settings on all computers (Primary and Secondary) with Powershell;

Get-NetFirewallRule |
Where-Object {
    $_.DisplayName -match 'Multiplicity|Stardock|Multi|MPRDP' -or
    $_.Description -match 'Multiplicity|Stardock'
} |
Select-Object DisplayName, Enabled, Direction, Action, Profile |
Format-Table -AutoSize

If you see Block entries related to your PRIVATE connection (not Public, unless you want that), do this;

Step-by-step GUI method
Press Win + R
Type: wf.msc, Press Enter
In the left pane, click: Inbound Rules
In the middle pane, click the Name column to sort alphabetically.
Find: Stardock Multiplicity 4
There are two inbound block rules, so check each one.
Double-click the first Stardock Multiplicity 4 rule.
On the General tab, look for: Action
Change it from: Block the connection
to: Allow the connection
Click Apply, Click OK.
Repeat the same thing for the second Stardock Multiplicity 4 rule.
Close Windows Defender Firewall with Advanced Security.
Restart Multiplicity, or reboot the machine if Multiplicity still does not connect.

Enjoy the fix.