richard39

This morning I had the same issue of seamless dropping the same PC, the only thing I did to restore good operation was drag the icons in the config screen. They were not greyed out before or after, but re-arranging them away from then back to the same layout fixed the issue. I cannot see how it is a network issue, this appears to be a Multiplicity issue. To rule out corrupt files, as they have had many "upgrades" over the years, I'll do a full uninstall and fresh install on th

Hi thanks for that, we don't use KVM normally, I did only to test if that would connect when seamless was not working (trying to rule out network). Testing it right now, invoking and releasing the KVM first time caused the seamless to not resume straight away, it needed the tiles shuffling on the config layout screen to get seamless to come back. The second time, it resumed seamless without intervention or delay. As KVM is not a feature we use much, if at all, I will n

Overnight the issue happened, a couple of other things to note: While KVM worked fine and icon remained solid in config, the seamless desktop was broken. 1. they have Virtual Box Host only adaptors, now disabled but were active (on all 3 machines - so hard to see this was the issue, but disabled to rule them out). The RJ45 is disabled now too on the primary, so only wifi on all machines. 2. flushed DNS on both pri and problem sec, problem remained 3. restart Mu

[quote who="sdRohan" reply="2" id="3815663"] While there were odd poor / lost connection issues I don't remember this being anything close to as persistent to this! If the Multiplicity version is consistent from a reliable state to not, what else has changed (PC, network, etc)? [/quote] Nothing has changed, always have had odd issues and dropped connections, even on ethernet cables, but since last upgrade of this package things routinely bad. <

While there were odd poor / lost connection issues I don't remember this being anything close to as persistent to this! It seems to get fixed if I restart the Primary "processes", but that does not explain why it is always the same machine that is lost, and that restart the processes or even the machine do not help, the problem continues that it will get dropped, not straight away but after 5mins to 10hours. The primary and other secondary both work, the dropped secondary is s