Cannot connect to Secondary Computer

Hello,
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.

Basj,
Stardock Community Assistant

Installation of Multiplicity will add firewall rules for Private and Work networks as long as you are using the OS firewall.

If your network is set to public you will find the firewall blocks Multiplicity because this is what you would expect on an untrusted network, rules are only added for trusted networks.

For obvious reasons we cannot disable AV software when installing and third party firewalls unfortunately may not respect the firewall rules defined by Multiplicity.

I, too, am running the latest versions of Multiplicity and Windows 10, and am having the same problem. I've had Multiplicity since it was Edgerunner, and it's worked fairly consistently through all my versions of Windows until the latest upgrade. 

My primary and secondary PC's are on the same trusted network and subnet, and have Trusted permissions in my firewall (ZoneAlarm, which I've also had for years). It makes no difference which PC I start first, or at the same time, my primary refuses to connect with the secondary unless I stop and restart the Multiplicity Service. I wrote a small batch file to stop and restart the service that I can run manually to connect, but haven't been able to figure how to delay executing it until after Windows is fully booted.

I'll be watching this thread also for some helpful info from tech support.

Thanks!

To youngbar0978, if you'd like to try the service restart batch, here it is. Just save as a BAT or CMD  (without the minus signs) and run as Admin:

---------------------------------

@ECHO.

@ECHO Rebooting Multiplicity.

@ECHO OFF

REM Stop Service

NET STOP "Multiplicity Service"

REM The following is a timer to allow for server RAM to clear after the service has stopped

REM Use the numerical value within the ‘timeout’ command line to control how many seconds the pause will be.

TIMEOUT /t 5 /NOBREAK

ECHO.

NET START "Multiplicity Service"

rem PAUSE

TIMEOUT /t 5

EXIT

-----------------------------------

Hello,

Sorry to hear you are having trouble.

In addition to what Neil noted, nearly all connection issues are resolved after following this guide:

https://forums.stardock.com/486104/multiplicity-support-faq#connectionissues

Sean Drohan
Stardock Support Manager

I created a task in Task Scheduler and delayed running the batch file I wrote by 3 minutes after user logon, and it works. Pretty simple band-aid since I start my PC's in the morning and go make my coffee, and when I get back, it's all good. 

I'll use that fix until I hear something back from Stardock that actually works.

Hope this helps someone.

While we are pleased it works for you but it is a complete mystery to us why you would need to do it at all.

Clearly something on boot is causing MP to not function as it should.  It would be prudent to determine exactly what that is - the process of elimination (via a clean boot), in your cases, would seem the best option. 

Sean Drohan
Stardock Support Manager

I have tried everything in the link you provided in an earlier thread, all to no avail other than giving me an ulcer I don't know what's causing the problem, and have not been able to fix it, so I put a band-aid on it and continue on.

MP starts on both PC's, but my primary just refuses to connect to my secondary, whether it's through ethernet or wifi until the MP service is rebooted.

I should mention that only the secondary PC has to have the MP service restarted, not the primary or both of them.

(Tried to post this yesterday, but kept getting  errors.)

Is there anyway I can get a refund?  Even with the batch files it won’t connect to the secondary computer???  You need to get in touch with Microsoft  Support to figure out what’s going on!!!! 

And how you can mitigate this for future Windows 10 upgrades!! 

THIS NEEDS TO BE FIXED IMMEDIATELY!!

I think I am going to buy a hardware solution so I don’t have to deal with M$ incompetence.

They  screw up these network connections on upgrades, I guess they think it is plugging security holes!!

I ordered my hardware solution.  I am hopeful that I can get a full refund (already requested through the sales vendor)  The older version worked great for years, but purchasing the latest version is buggy and / or Microsoft peer to peer networking is being phased out.  

Microsoft is just too unreliable for peer to peer networking now, especially with emphasis on the cloud, One Drive etc.

Thanks!

Hello,

For refund, please raise a ticket using this link : http://esupport.stardock.com/index.php?/default_import/Tickets/Submit

Thank you,

Basj,
Stardock Community Assistant

There's a new update if anyone is interested, V3.55 Build 00101.