More information. The problem looks to be associated with primary, as connections reestablish immediately after reboots/shutdowns/suspends to RAM on the secondary. Or to put it another way, I only get connection problems after rebooting/shutting down the primary.
I've been able to get connections working reliably now. Every morning, I drag the secondary off the grid, wait 5 seconds, and then drag it back on. It connects almost immediately.
Follow up: the machines have now connected; it took around an hour.
So, on the first day of using Multiplicity 4 Pro I encountered the loop twice. I executed "Flush DNS Cache" and it went away; however, I've been encountering connection problems since: On day two, my machines connected immediately but the cursor was a bit laggy. On days three and four (today) the cursor has been stable, but I've really struggled to make the initial connection after reboot of the two machines. On day three it took around ten minutes, and today I've bee
Thanks for getting back. Primary (Desktop): Windows 11 version: 24H2 (OS Build 26100.2605) Secondary (Latop): Windows 11 version: 23H2 (OS Build 22631.4602)
Follow up: restarting the secondary fixed the issue, but it started to happen again (almost) exactly an hour later.
I've just bought Multiplicity v4 pro and I'm getting this issue. I managed to get my desktop connected to my laptop (using WIFI) and everything worked well for an hour or so. But now I'm getting alternating messages on primary: complaining about a "wrong passcode" first, and then the "secondary did not respond in time".