Search
Forum Home | Login
Frustrated99
Frustrated99
Join Date 05/2025
0

Frustration with 4.01

Unable to connect

June 22, 2025 9:10:34 PM from Stardock ForumsStardock Forums

Today I wanted to use the KVM on a system on the same network. The password and the encryption has not changed. I made sure of that because when I attempted to connect to it I got the following. I have no idea why this software is having issues.  It is using the IP address to connect to the Ryzen2700 and that is the remote machine's IP address.  I winded up just walking over to the machine and doing what I needed to do on it. 

Both computers are Windows11 Pro. Both are private networks. I did a TEST in the KVM on the main computer to the Ryzen and it failed saying the encryption key was incorrect. The thing is the key has not changed since I installed this software. I checked both the password and the encryption key and they are correct. 

Is there an issue if the remote system has a MS update ready to be applied but is waiting for a reboot? Because I rebooted the remote computer by walking over to it and as soon as I did that I was able to KVM over to it.  I had previously tried rebooting the Primary Computer but that did nothing to solve this issue. 

 

multiplicity
Search this post
Advanced Search
Subscription Options
Reason for Karma (Optional)
Successfully updated karma reason!
Frustrated99
basj
Join Date 03/2001
+1659 sdemployee
Reply #1 June 22, 2025 11:36:46 PM
from Stardock ForumsStardock Forums

Hello,
Sorry to hear you are having issues. Need to clarify, you're using Multiplicity 4 or Mutliplicity 4 Pro?

Thank you,
Basj,
Stardock Community Assistant.

Reason for Karma (Optional)
Successfully updated karma reason!
Frustrated99
Frustrated99
Join Date 05/2025
0
Reply #2 June 23, 2025 12:57:14 AM
from Stardock ForumsStardock Forums

Sorry the Pro 4.01  version

Reason for Karma (Optional)
Successfully updated karma reason!
Frustrated99
basj
Join Date 03/2001
+1659 sdemployee
Reply #3 June 23, 2025 1:11:13 AM
from Stardock ForumsStardock Forums

Please review this thread and see if help with your issue. Try it and report back.

  1. https://forums.stardock.com/535352 
  2. https://forums.stardock.com/532032 

Thank you,

Basj,
Stardock Community Assistant

Reason for Karma (Optional)
Successfully updated karma reason!
Frustrated99
Frustrated99
Join Date 05/2025
0
Reply #4 June 23, 2025 9:00:08 AM
from Stardock ForumsStardock Forums

As I indicated in my initial post, I followed all the suggestions. Multiplicity was trying to connect via the remote machine;'s IP address. I had tried disabling IPV6. The encryption key was the same on both computers, as was the password.  Both computers were using the LAN here and both had the network configured as Private. Only after rebooting the remote computer after it installed a MS update did the connection work. 

This is not the first time this inability to connect has happened, with the result that I spend more time trying to figure out what the heck the issue is. I just tried it this morning and the connection worked without an issue. It seems Multiplicity likes to frustrate me and let me down when I need to really use it. 

 

Reason for Karma (Optional)
Successfully updated karma reason!
Frustrated99
basj
Join Date 03/2001
+1659 sdemployee
Reply #5 June 23, 2025 9:02:59 AM
from Stardock ForumsStardock Forums

Hello,
I have forwarded 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.

Basj,
Stardock Community Assistant

Reason for Karma (Optional)
Successfully updated karma reason!
Frustrated99
sdRohan
Join Date 10/2012
+726 sdsupport
Reply #6 June 23, 2025 9:06:01 AM
from Stardock ForumsStardock Forums


Is there an issue if the remote system has a MS update ready to be applied but is waiting for a reboot? Because I rebooted the remote computer by walking over to it and as soon as I did that I was able to KVM over to it.  I had previously tried rebooting the Primary Computer but that did nothing to solve this issue. 

Its difficult to say but rebooting the PC has it working and subsequent connection attempts have worked, yes?

If this is not a frequent occurrence, perhaps we just chalk it up to a one time thing, Frustrated99?

Sean Drohan
Stardock Product Lifecycle Manager

Reason for Karma (Optional)
Successfully updated karma reason!
View all recent posts
Mark all posts as read Delete cookies created by the forum Return to Top
Stardock Forums v        Server Load Time:   Page Render Time:
Facebook Twitter YouTube Google+