works for a while (hours) then starts dropping the connection between two systems

WTF???

from Stardock Forums

This has happened multiple times/days without any changes made on either the primary or secondary system. Both are running the exact same version (downloaded once, used twice) so that's not the source. Both are on my local WIFI network (802.11AC connections) and both have solid internet/network connections.

For whatever reason, multiplicity will run for some days without issue, then I'll have days where it runs ok for hours only to start dropping then reconnecting, then dropping the connection for extended periods. Both systems are NOT sleeping, on AC power (not doing any power saving on either) and otherwise fine. It's to the point where I'm ready to simply remove the product and be done with it. Which is sad since I do like what the product does, WHEN it actually works properly.

Over the past 30 minutes I've lost track of how many times I've seen the message (on the primary) about it connection lost, then connected again. Only to lose it again a short time later (seconds to minutes, not consistent there).

I am running the very latest release. Both computers (laptops) are running Windows 10 Pro (1803). This has happened on earlier versions of Windows 10 as well.

I do have the IP of the secondary system in the settings of the primary, which is stable. I've removed the secondary completely from the setup at times, added it like it's a new system connecting, and that hasn't made any difference (problem ALWAYS returns).

For AV protection, I'm running the latest version of Kaspersky Internet Security (at this time, looking to go to either Avira or Sophos Home Premium soon(ish). Which is up to date and I'm NOT seeing any errors listed there. I have my local network/IP range set to be trusted there. I've even excluded the multiplicty folder from KIS so it has no chance of messing with it. No change.

I'd love to have a setting that fixes this. OR have an update that fixes this issue. At this point, if neither happens, I'll be removing the product completely and tossing it out. I've already stopped using Fences since it was more annoying than useful (so I wasted that money).

multiplicity
7,089 views 10 replies
Reply #1 from Stardock Forums Top

This piss-poor behavior continues to happen. This morning, my secondary system went to screen saver for a few seconds and the lose/reconnect barrage happened all over again. It continued to happen over the following ~30 minutes before it appears to have calmed down. I don't know of ANY place this could be considered 'normal' or 'acceptable' behavior of software. Especially when the software is PAID for. I also fail to understand how a software company can NOT have an actual support structure and forces people to report issues in a forum.

As I mentioned before, I'm about ready to shit-can all of the software from Stardock. I'll also let everyone I know (and meet in the future) to NOT even consider getting anything from Stardock. Unless this issue can be resolved (this week at the latest).

I'm also getting ready to jettison Kaspersky Internet Security due to their completely unhelpful support people. I had to figure out where setting changes needed to happen to resolve an issue I was having with a web client (target is on my local network).

I'm in the IT field, so there are more than a good number of people that I can inform about these software flaws (make no mistake, these ARE flaws) so they know to NOT get these products.

Reply #2 from Stardock Forums Top

Both are on my local WIFI network (802.11AC connections) and both have solid internet/network connections.
End of quote

Do you still have issues if you connect them via Ethernet?

Multiplicity - Control multiple PCs using one keyboard and mouse
Reply #3 from Stardock Forums Top

Neither have native ethernet ports. Both have 802.11AC wireless. They're connected to a high end 802.11AC router/WAP. One of the systems only has ONE USB3 connection on it. So IF I was to use wired networking, I'd sacrifice that connection in order to do so.

 

IMO, trying to blame wireless networking these days is lame. MAYBE if I was running 802.11b or g that MIGHT be viable. But, both of these systems are within 3' of the WAP/router. Plus the problem starts, happens for a while, then [sometimes] goes away. IF it was related to the wireless, it would happen constantly, every time the systems were in use.

Reply #4 from Stardock Forums Top

For S&G's I TRIED to use the ethernet adapters/dongles I have on both systems. There's NO way (that I could see) to change the setting for the secondary system to it's wired IP address. As such, it would NOT connect to that system no matter what. So going over the wire is 1000% useless. Unless there's a way to allow it to use the different IP address, that's pointless.

As I mentioned in my post from early today, the problem happened this morning (for a while) then it stabilized.

I'm still on the verge of tossing this software and never returning. Pretty sad when you purchase a product that works for a while, but when it starts to have issues, the 'support' person's first comment is to try and blame your wireless connections. Never mind how it actually works for a while before FAILING, then works for a while, before failing AGAIN.

At this point, I wish I had never spent money on the product.

Reply #5 from Stardock Forums Top

An intermittent issue like this is almost certainly something external to Multiplicity.

Wireless connections are extremely prone to interference and Multiplicity will detect drops when a packet response is not obtained within 6 seconds.  Should this happen it will disconnect and perform a reconnect cycle.  The fact that it tells you this does not mean Multiplicity is to blame simply that something caused the network layer to not respond correctly and Multiplicity attempts to reconnect.  The fact it takes some time to reconnect also points to an external to MP factor probably network related. 

The only other possibility is if one end is doing something that's using up basically 100% of the cpu which means MP doesn't get a chance to respond in a reasonable timeframe or if one end is actually going into always on sleep mode where it will in fact pretend to be on but saves so much power it will not respond in a reliable manner.

Your experience, whilst frustrating, is not a typical experience with Multiplicity and hopefully we can help you to find the cause and thus a solution.

Reply #6 from Stardock Forums Top

Neither system has high CPU usage when this happens. In fact, there's PLENTY of resources on both systems. I've even gone so far as to NOT run ANYTHING other than the OS (along with MP) on the secondary system. Router/WAP is on the same desk as BOTH systems. MIMO router (Linksys EA8500). The fact that MP won't allow me to change the IP address for the secondary system is a big issue IMO.

I'm NOT using shitty hardware here. OS is Win10 Pro (1803) on BOTH systems.

Also, this behavior happens for a while, once it kicks off, then APPEARS to stabilize for at least a while. The flips between connected and NOT are rapid (maybe a couple of seconds apart) and happen in a barrage.

You guys can keep blaming the wireless network all you want, but I'm calling BS on that. Especially when I have all of four devices on my wireless network, and ALL of them are in the same room when I'm doing this. Plus, two of them are idle 99% of the time when I have the issue (one being my cell phone, so it's using very little WiFi when running).

Since Stardock seems to take the attitude of "our shit doesn't stink" and is really not very helpful, I'm one step closer to kicking it to the curb and trying one of the other solutions (free). I have a higher tolerance of FREE software than something I've paid for. IF I'm paying for a product I [at the very least] expect it to have actual support in place for the product. NOT finger pointing.

Reply #7 from Stardock Forums Top

Something else... I powered on the secondary system. Task Manager is showing it's idle (>5% CPU load, 27% RAM usage, NO network traffic) and guess what... MP CANNOT F'ING CONNECT TO IT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Tried to connect from the main in the settings of MP... It claims it can, but then it drops it a second or two later. Secondary system is STILL IDLE!!!!!!!!!!!!!!!!!!!!!!!!! 0Kbps network traffic in TM. So, claiming CPU or network traffic is the fault is BS. It also cannot seem to stay connected when Windows Update is running. Another BS move since the product should use very little network bandwidth. I even trimmed down the clipboard settings to just allowing files to be copied between. Since I wasn't doing that, it shouldn't use any network. IF it does, then THAT'S A FLAW IN THE PRODUCT!!!!!!!!!!!!!!!!!!

The wifi connection on the secondary system shows 866.5Mbps speed. Same as the primary system. SO claiming it's a wifi speed issue is also BS!!

Oh, and after SEVERAL MINUTES of NOT connecting, now it seems to have connected. NO change in the system resources used, or any other settings on either system. IF anything, I got an email on my cell phone (that's the only thing that happened between).

Reply #8 from Stardock Forums Top

You people keep screaming about using a wired connection for this product. BUT there's no F'ING way to change the F'ING IP address the product wants to use to connect to the secondary system. WTF!!!!!!!!!!?????????????????????????!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! How the ever loving HELL are you supposed to use a different connection when it's LOCKED into using the first one???? Even uninstalling and then installing again doesn't F'ING change that!!!!!!!!!!!!!!!!!!!!!!!!!!

I've added the second IP address into my AD server's DNS records, plus set the DHCP given as a reservation. A ping (from the other computer) replies back with the wired address 100% (0% loss). So that's working... But the product is too F'ING STUPID to take that (even when NOT checking the box to use the wireless address)...

Reply #9 from Stardock Forums Top

Assuming you originally used machine name, you just create a new connection but instead of using the name you enter the wired IP address for the name.  Then put this on the Multiplicity grid instead of the original connection.

Windows will automatically pick the right network interface to use to connect to it (in theory)

Regarding it looking up IP addresses, it uses the address Windows returns to it.  It is capable of using more than one BUT it will use the first one that succeeds as they are treated as a priority order and if you see the wireless one in the dialog for 'always use this IP' then that is the IP address that is being returned.

Reply #10 from Stardock Forums Top

Adam, you can add a PC by IP, instead of hostName, like so: