---
title: "Multiplicity Connection issues 101"
canonical: "https://support.stardock.com/space/SHC/1287946260/Multiplicity%20Connection%20issues%20101"
format: markdown
---
NOTE: If you are using 'WebRoot' as an Anti-virus product, disable (remove is preferred) and try again.  For reasons unknown (and only addressable by them), WebRoot will prevent MP from working properly consistently.

NOTE::  You cannot connect to a Windows XP machine via KVM mode.  The errors will be that that it is a firewall issue or that KVM mode is not enabled.

NOTE: All testing should be done via Ethernet (not wireless) and directly connected to a single router.  Also, if used, any VPN connection should be disconnected.

Ensure you have the latest and same version of MP software installed on each machine; one as a Primary another as a Secondary.  You can check your version on the 'Help' or 'About' tab in MP.  You can get the current version on your account page:

[https://www.stardock.com/support/productkeyretrieval](https://www.stardock.com/support/productkeyretrieval) 

Next (and important), try rebooting every MP machine, as well as the connected router, and testing the connection again:

Seamless: 

![image](media://a28a2a50-713a-4bfa-b3e3-5b7253e84727)

KVM:

![image](media://440529a4-9dcb-4b26-8de2-7b4f23e548dc)

If that fails, and as a test, shut of Windows Firewall (as well as any other AV \ Firewalls you may use):

![image](media://3f8c5326-2c99-4952-bcb4-fed8088b8df0)

Try your connection again.

If it works, turn the Windows firewall back on, download the following file (on all MP PCs), and run the included batch file:

[https://cdn.stardock.us/support/uploads/MPPortFix.zip](https://cdn.stardock.us/support/uploads/MPPortFix.zip)

If that works, it was a firewall port issue.

If that fails, you need to check that the firewall profile you are using is set for Domain, Home or Private, NOT Public.

![image](media://2e6b9a72-b496-4e5c-a3d5-9aa6bd35a457)

Changing Windows network type should you need to:

Win7:

[http://windows.microsoft.com/en-us/windows/choosing-network-location#1TC=windows-7](http://windows.microsoft.com/en-us/windows/choosing-network-location#1TC=windows-7) 

Win8:

[https://www.youtube.com/watch?v=KRBXOuCWk18](https://www.youtube.com/watch?v=KRBXOuCWk18) 

Win10:

[https://tinkertry.com/how-to-change-windows-10-network-type-from-public-to-private](https://tinkertry.com/how-to-change-windows-10-network-type-from-public-to-private) 

If that still fails, remove the Secondary connection completely:

Seamless:

![image](media://7829f4db-4ac5-4024-a075-38795d117ab4)

KVM:

![image](media://625f4274-20a4-4085-a72c-1570dd33d0c5)

Then re-add the connection by the Secondary's IP instead of the host name