I have Multiplicity 2 on my two Win7 machines and an XP machine.  The XP machine cannot be seen or see the other two computers (either as a secondary machine or a primary machine). 

It worked fine with Multiplicity 1.26.  

The XP machine's firewall is set to allow Multiplicity 2 through (as a program, no matter the ports), the same way Multiplicity 1.26 was set up.

The two Win7 machines work with no problems at all.  Other programs (like Splashtop) connect fine between the Win7 machine and the XP machine.

Assistance in how to fix this would be greatly appreciated.


EDIT: It seems to be the firewall on the XP machine, even though it should be set properly.


Comments
on Jul 24, 2012

EDIT: It seems to be the firewall on the XP machine, even though it should be set properly
You adjusted the XP firewall manually and all is well?  Was there an entry in the rules at all?

on Jul 24, 2012

I had to turn *off* the XP firewall.  It looked like there was a rule added, plus I added a second one myself.  It was no-go until I turned the firewall completely off.

It's the stock XP firewall.  It's a computer I can't install another firewall on, as well, so I have no choice.

So, with the firewall off, M2 works perfectly.  With the firewall on, it can't see or be seen by other computers with M2.

on Jul 26, 2012

Do you have a second nic or second virtual nic installed such as one from virtual box. I have found that to be a common problem with the windows firewall where it assigns a rule to the wrong nic or in my case the virtual nic

on Jul 31, 2012

No.  It's a single port with a single IP, no virtual nics. 

As mentioned, with 1.26, it was fine.  I did send in a support ticket with added information from the Stardock Info tool, so hopefully that'll help track things down.