Issue with New Install and Reconfig of Primary and Secondary Machines
from 
Stardock Forums
Stardock Forums
Hello,
I have been running Multiplicity 1.05 in the following configuration successfully for quite some time.
System A - Secondary Machine Running XP Pro (standard port, no password, windows firewall disabled)
System B - Primary Machine Running XP Pro (standard port, no password, windows firewall disabled)
I have recently replaced System A with a new Machine System C. As part of this replacement I have changed the configuration for Primary and Secondary display as follows:
System B - Secondary Machine Running XP Pro (Standard port, no password, windows firewall disabled)
System C - Primary Machine Running XP Pro (Standard port, no password, windows firewall disabled)
In this configuration Primary System C can never establish connection to Secondary System B. The two systems can ping each other, browse shared files, etc. System C even lists System B as an available machine for secondary connection, but when I go into the configure menu and select "OK" I get the following error:
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
For kicks I decided to flip the configuration around and make B the primary again. So the setup looks like this:
System C - Secondary Machine Running XP Pro (Standard port, no password, windows firewall disabled)
System B - Primary Machine Running XP Pro (Standard port, no password, windows firewall disabled)
In this scenario, the setup works. I don't any error messages and I get mouse and keyboard support on both boxes. When I go back to making B the secondary and C the primary I get the error message I listed above.
In browsing these forums, I see a common troubleshooting item is to check that multisrv32.exe is running on the secondary machine. I am at work at the moment and can't check for that. I will do so tonight. Are there any other troubleshooting steps I can take? The systems are NOT running any other type of software fire wall.
Thanks
I have been running Multiplicity 1.05 in the following configuration successfully for quite some time.
System A - Secondary Machine Running XP Pro (standard port, no password, windows firewall disabled)
System B - Primary Machine Running XP Pro (standard port, no password, windows firewall disabled)
I have recently replaced System A with a new Machine System C. As part of this replacement I have changed the configuration for Primary and Secondary display as follows:
System B - Secondary Machine Running XP Pro (Standard port, no password, windows firewall disabled)
System C - Primary Machine Running XP Pro (Standard port, no password, windows firewall disabled)
In this configuration Primary System C can never establish connection to Secondary System B. The two systems can ping each other, browse shared files, etc. System C even lists System B as an available machine for secondary connection, but when I go into the configure menu and select "OK" I get the following error:
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
For kicks I decided to flip the configuration around and make B the primary again. So the setup looks like this:
System C - Secondary Machine Running XP Pro (Standard port, no password, windows firewall disabled)
System B - Primary Machine Running XP Pro (Standard port, no password, windows firewall disabled)
In this scenario, the setup works. I don't any error messages and I get mouse and keyboard support on both boxes. When I go back to making B the secondary and C the primary I get the error message I listed above.
In browsing these forums, I see a common troubleshooting item is to check that multisrv32.exe is running on the secondary machine. I am at work at the moment and can't check for that. I will do so tonight. Are there any other troubleshooting steps I can take? The systems are NOT running any other type of software fire wall.
Thanks
WinCustomize Forums
