Can't connect to laptop

from Stardock Forums
I just downloaded the Multiplicity trial and have installed and configured my desktop as the primary and my laptop as the secondary.

My desktop can see the laptop when I use Windows Explorer and browse the network (they are in the same workgroup), but Multiplicity does not detect it. I tried added a "custom" connection, specifying the local IP of the laptop, but it still can't connect.

I get the following message:

"Connection test failed

If you have not yet installed... (it's installed)

If you have installed, are you sure... (settings have all been checked)

Error: Unable to contact machine (Firewall?). You should ensure your firewall allows multipl.exe and multipl32.exe access to the network and that port 30564 is open."

I'm using Windows Firewall, and I've added both multipl.exe and multipl32.exe to the allowed list.

The only weird part of my configuration is that I have two routers. The primary desktop is connected to a D-Link router. The laptop is wireless, connecting through a Netgear router that is connected to the D-Link.

As I said, both computers are able to share folders and printers, and I can browse the network from either one. But for some reason, I can't get Multiplicity to connect. Any suggestions?

thinkdesk
2,727 views 5 replies
Reply #1 from WinCustomize Forums Top
I have the pro version so YMMV.

Firewall on router(s)?
Allowing MULTISRV32.EXE in Windows firewall?
Allowing TCP port 30564 in Windows firewall?

I had to check all those things to get my MP to work.

Posted via WinCustomize Browser/Stardock Central
Reply #2 from Stardock Forums Top
Ah... forgot to allow the port. Thanks! It's working. By the way, Multiplicity is REALLY COOL!
Groupy 2 - Organize multiple applications into grouped tabs on your Windows desktop
Reply #3 from WinCustomize Forums Top
The pro is s-o-o much better. Copying files and folders back and forth changes everything.

Posted via WinCustomize Browser/Stardock Central
Reply #4 from Stardock Forums Top
I may have spoken too soon. I had to reboot the primary, and now I can't connect again. All the settings are still correct, and oddly, when I run the Troubleshooter from the primary, it says:

"Multiplicity was able to connect to this machine without any problems."

Yet it isn't connecting, and if I go to configure it fails with the same message I originally posted.

This looks really cool, if I can just get it working consistently.
Reply #5 from WinCustomize Forums Top
Did the primary maintain the same IP address? (although that shouldn't matter)

I think I had the same thing happen once. It was like the secondary was bound to the primary and wouldn't connect again.

Reboot secondary and see what happens.

Posted via WinCustomize Browser/Stardock Central