john61

Join Date 09/2015

Seamless and KVM not connecting

Been at this for a hand full of hours now all out of options. It was working - not sure what happened but just stopped being able to connect to a secondary laptop that's sitting right next to me.

For the life of me, I cannot connect from my primary to secondary either through Seamless or KVM. Both running same versions.

The secondary is a work laptop that connects to my home network and connects to my work network via DirectAccess. This is set up as the secondary along with KVM being enabled

The primary is my main PC that's only connected to my local home network.

Tried disabling AV scanners, firewall on both machines. Uninstall and reinstall. Folder and executable exclusions. Both machines have the network set as private. Tried both Wifi and LAN connection. Every time I try and check the connection, keep getting the failed to connect message asking to check firewall settings, computer name, IP address. I've also tried the MPPortFix.bat file with no luck.

Any help would be greatly appreciated.

Advanced Search

Subscribe to this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

Hello,
I have forward your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Meanwhile please check this guide for Connection Issue FAQ https://forums.stardock.com/486104/multiplicity-support-faq#connectionissues

Basj,
Stardock Community Assistant

Successfully updated karma reason!

Hello,

Sorry to hear you are having trouble.

The secondary is a work laptop that connects to my home network and connects to my work network via DirectAccess. This is set up as the secondary along with KVM being enabled

I assume 'DirectAccess' is this:

https://en.wikipedia.org/wiki/DirectAccess

If so, is it at all possible to try without that connected?

If not, ensure that 'split tunneling' is enabled:

https://directaccess.richardhicks.com/2018/05/14/directaccess-selective-tunneling/#:~:text=DirectAccess%20uses%20split%20tunneling%20by%20default.%20Optionally%2C%20it,inspect%20and%20monitor%20Internet%20traffic%20from%20field-based%20clients.

And try connecting to the Secondary by its IP (home one, not the VPN) instead of hostname:

Sean Drohan
Stardock Support Manager

Successfully updated karma reason!

Thanks for the quick response Sean.

You are correct with Direct Access. However, not sure if we're on Forced Tunneling or Selective (Split) Tunneling. However, in order for the laptop to connect to Direct Access, Windows firewall 'has' to be enabled. Disabling it would drop the Direct Access connection, which is something I already tried. Kill 2 birds with one stone - Disable Firewall and disconnect from DA.

As for the IP, DA uses IPV6 so I never used that before. Only tried with the PC name as well as the local IP (192.xxx)

Last night, I also make sure Network discovery and file sharing was enabled on the secondary.

Still get failed to connect

Successfully updated karma reason!

It was working - not sure what happened but just stopped being able to connect to a secondary laptop that's sitting right next to me.

Mid use or after a discon \ reconnect?

If you demote your primary to a secondary (deactivate it in the process), promote your secondary, can you connect then?

Sean Drohan
Stardock Support Manager

Successfully updated karma reason!

Yes. That seems to work. Setting the laptop as the primary and my 'original' as secondary, able to see it, access and connect Seamless and KVM.

Successfully updated karma reason!

Quoting john61,

reply 5

Yes. That seems to work. Setting the laptop as the primary and my 'original' as secondary, able to see it, access and connect Seamlessly and KVM.

Then that indicates it's a firewall issue.

With yours being directly tied to DirectAccess, this might be something your IT people need to look at.

Sean Drohan
Stardock Support Manager

Successfully updated karma reason!