alejohnny

Join Date 10/2024

Unknown protocol error with Seamless Display

Hi,

I'm on Trial testing Multiplicity 4 BETA 1 and I'm getting the error: Connection failed due to an unknown protocol error.

I already tried to mess with the encoding settings, but no success.

Seamless Control is working with no problems (using right now to type this message).
It's a fresh installation of Multiplicity in both computers, never used/installed Multiplicity before.
Already tried to restart the secondary computer (didn't try the Primary computer, but already restart service and processes).
Secondary computer is a fresh Windows 11 installation.

Where can I get logs?

multiplicity

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

Hello,

Hello,
Sorry to hear you are having issues. I have forward 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

Successfully updated karma reason!

Did it show this more or less instantly or after say 4+ seconds?

Successfully updated karma reason!

Quoting Neil Banfield,

reply 2

Did it show this more or less instantly or after say 4+ seconds?

Not instantly, shows about 4 to 5 seconds after the "Connecting to" message.

Successfully updated karma reason!

That almost certainly means the firewall on the primary is blocking port 30568 or the primary has an ARM processor or very old AMD/Intel 64 bit processor.

Successfully updated karma reason!

Quoting Neil Banfield,

reply 4

That almost certainly means the firewall on the primary is blocking port 30568 or the primary has an ARM processor or very old AMD/Intel 64 bit processor.

Oh no, so the cause is the firewall port blocked, as I wasn't able to send audio to my primary because of the port blocked (message saying that the port 30567 is blocked).

And it's not possible for me to create an allow rule, as my primary is my work computer and firewall settings are all GPO based.

Is there any chance to change the incoming port to the secondary (my personal laptop, so I can open the port from there) to circumvent this?

Anyway, thanks for the help!

Successfully updated karma reason!

I installed Multiplicity on my desktop computer and set a Primary, also tried to use Seamless Display with my secondary and I'm getting the same error.

I already disabled Firewall on both computers and still got the same issue (4-5 seconds in Connecting to screen and have the Connection failed due to an unknown protocol error).

So, maybe is not related to the firewall port.
Also, my primary computer (desktop) has a Ryzen 5 computer, and my secondary (Laptop) has a 12 gen Intel processor.

Both with Windows 11, fresh new installation.

Successfully updated karma reason!

I have the same issue. I added an rule on my firewall (ESET), but still get the error.

Successfully updated karma reason!

Quoting N1c01448,

reply 7

I have the same issue. I added an rule on my firewall (ESET), but still get the error.

Can you try switch your primary as your secondary and vice versa and test if works?

Yesterday I tried and works, so I'm not sure if it's a firewall issue.

With the BETA 2 there's an error code 3 on my case.

Successfully updated karma reason!