Multiplicity won't connect after removing ZoneAlarm AV+Firewall
My primary is a desktop running Win11Pro x64 using Defender AV and firewall. My secondary is a Win10Pro x64 laptop that was running an old version of ZoneAlarm. I decided to uninstall the ZA and stick with Defender on the laptop, but after removing ZA and rebooting, my primary could no longer connect to the secondary. When I tried to connect, I would get the error message that the secondary was not turned on, the network was down, firewall wasn't configured correctly, etc. I rebooted both machines again, and still had the same problem. Deleted the secondary and tried to add it back in, but that wouldn't work either (it couldn't find anything to connect to).
I tried various firewall settings, making sure that Multiplicity was allowed access through the firewall, and still no joy. After messing around with it and googling for any suggestions, I finally gave up after a couple of hours and DL'd and installed a newer version of ZA just to see what would happen. It wasn't even finished with the installation when the message popped up on my primary that Multiplicity was connected. Didn't have to do anything else, it worked just like it used to before I uninstalled the older version of ZA.
I've been using Multiplicity since it was owned by EdgeRunner (and maybe one company before that, but not sure) and haven't run into anything quite like this. Any thoughts, or suggestions on how to get around using ZA as the fix for making Multiplicity run as it should? I'd just as soon get rid of it if I can.
TIA,
SCTom