Multiplicity 2.0 With Computers Connected Wirelessly

from Stardock Forums

I am typically a 'hard wired' guy when it comes to my home network, however, I've recently found a use for Multiplicity 2.0 with an older device that I've upgraded and planned to use wirelessly.  I've read that it can be done, but so far my primary machine (the master computer) has been unable to detect the wireless device on my network.

It is using XP Service Pack 3, while my other machines are variations of Windows 7 64-bit.  Is there something I am doing wrong here?

Thanks.

multiplicity
4,694 views 4 replies
Reply #1 from Stardock Forums Top

I think its because Windows 7 won't pickup the older machine. There are a lot on network compatibility issues between win xp and win 7.

 

Reply #2 from Stardock Forums Top

Quoting MXDuke, reply 1

I think its because Windows 7 won't pickup the older machine. There are a lot on network compatibility issues between win xp and win 7.

 
End of MXDuke's quote

 

I'm having the same issue, but they are both Windows 7 machines. No old machines in the mix. Thoughts?

The Political Machine 2024
Reply #3 from Stardock Forums Top

Quoting geothefaust, reply 2
I'm having the same issue, but they are both Windows 7 machines. No old machines in the mix. Thoughts?
End of geothefaust's quote

I assume you mean that when you try to add a Secondary that MP is not finding it, yes?

If you disable the firewalls (Windows and 3rd party, AV included) on ALL machines, is it found then?  They are both on the same subnet, yes?

Reply #4 from Stardock Forums Top

Quoting sdRohan, reply 3


Quoting geothefaust, reply 2I'm having the same issue, but they are both Windows 7 machines. No old machines in the mix. Thoughts?

I assume you mean that when you try to add a Secondary that MP is not finding it, yes?

If you disable the firewalls (Windows and 3rd party, AV included) on ALL machines, is it found then?  They are both on the same subnet, yes?
End of sdRohan's quote

 

Hey Rohan! Thanks for your reply. I appreciate it.

 

Yes, that is correct. When I added another Secondary, MP was not finding it. Which I thought weird because I have other computers connecting to my primary just fine, and they are all hardwired as well.

 

I had all third party software disabled, but not Windows firewall. They are all on the same subnet.

 

I found a solution late last night. I'll post it here as to help others. I tried to delete the exception for Multiplicity in Windows firewall. But removing it was disabled. So I went to "Windows Firewall with Advanced Security", and removed any inbound and outgoing exceptions for Multiplicity. Then removed any values/keys in the registry for Multiplicity (by searching for and removing anything related to "Multiplicity", "Stardock" and "EdgeRunner").

Reboot, reinstall MP, reboot, allow MP exception in Windows firewall. Good to go.