Upggraded to 4 Pro and have numerous issues

Seamless Display Issue

Hi Guys,

I have just upgraded to 4 Pro for KVM and Seamless Display, to sort out other issues I used the bat file from your site and cleaned down 3 of my PC's. Installed on primary PC and on one secondary PC and setup Seamless which is working fine, sound and control.

I have added the secondary PC to Seamless Display but hen I try to connect to it I am getting

'Unable to connect to STRIX: Connection failed due to not being on the same subnet....'

They are as far as I can see, Seamless works and Audio sending/receiving works so does this not suggest they are on the same subnet?

Also when trying to add the secondary PC to KVM I am told the passwords are not matching, they are, every encryption key and passwords have been set to the same.

Am I missing something, please advise.

3,036 views 8 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. 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

Reply #3 Top

Ahhh, now another issue the remote PC now tells me that it can's find a 'computer with the name provided' to send audio to and yet Seamless is working, I have tried the name and the IP, both with the same message

Reply #4 Top

If the PCs are connected via a mixed connection medium (some wireless, some Ethernet), can you test with them all on Ethernet?

Sean Drohan
Stardock Product Lifecycle Manager

Reply #5 Top

all PC's are connected via ethernet and all have IP's starting 192.168.1. and all are connected to the same switch.

I have installed Multiplicity onto my third PC am getting on that one when I try to add it to KVM the same message of subnet and yet the second PC does let me use KVM.  Both of them (PC's) will not let me use the Seamless Display with the same message of not on the same subnet.

I am at my wit's end....

Reply #6 Top

Quoting 2l8m8Basher, reply 5

all PC's are connected via ethernet and all have IP's starting 192.168.1. and all are connected to the same switch.

I have installed Multiplicity onto my third PC am getting on that one when I try to add it to KVM the same message of subnet and yet the second PC does let me use KVM.  Both of them (PC's) will not let me use the Seamless Display with the same message of not on the same subnet.

I am at my wit's end....
End of 2l8m8Basher's quote

If you open a command prompt and type 'ipconfig' on each PC, are you seeing multiple subnets in the results?  With your switch, are you employing a VLAN or any type of proxy, firewall, or VPN appliance along your network?

Sean Drohan
Stardock Product Lifecycle Manager

Reply #7 Top

Hi @sdrohan

Another issue is when trying to connect to Secondary 1 KVM I am told "Multiplicity was able to connect, but your encryption key setting is incorrect. The key must be the same." They are all the same, on all PC's I use the same key, I have changed them a number of times to try and connect it and get the same message every time.

So breakdown is this

Secondary 1:

KVM: Yes
Seamless: Yes
Seamless Display: No

Secondary 2:

KVM: No
Seamless: Yes
Seamless Display: No

Below are the config's for each machine, let me know if you see anything please.

Main PC ipconfig:

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : lan

   IPv6 Address. . . . . . . . . . . : 2a00:23cc:c42b:9b00:d341:5c0e:17e9:6484

   IPv6 Address. . . . . . . . . . . : fd78:4c15:7f9d:0:7141:8092:fc77:9f8a

   IPv6 Address. . . . . . . . . . . : 2a00:23cc:c42b:9b00::179

   Temporary IPv6 Address. . . . . . : 2a00:23cc:c42b:9b00:80d5:f1ec:f047:da6a

   IPv6 Address. . . . . . . . . . . : fd78:4c15:7f9d::179

   Temporary IPv6 Address. . . . . . : fd78:4c15:7f9d:0:80d5:f1ec:f047:da6a

   Link-local IPv6 Address . . . . . : fe80::a99b:6a6f:f6b3:888f%2

   IPv4 Address. . . . . . . . . . . : 192.168.1.179

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . : fe80::2641:feff:fe4f:4710%2

                                       192.168.0.249

                                       192.168.1.254

 

Secondary 1

Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix  . : lan

   IPv6 Address. . . . . . . . . . . : 2a00:23cc:c42b:9b00::a2a

   IPv6 Address. . . . . . . . . . . : 2a00:23cc:c42b:9b00::c7c

   IPv6 Address. . . . . . . . . . . : 2a00:23cc:c42b:9b00:f16:7152:c534:7144

   IPv6 Address. . . . . . . . . . . : fd78:4c15:7f9d::a2a

   IPv6 Address. . . . . . . . . . . : fd78:4c15:7f9d:0:6c5f:4844:ec1f:1034

   Temporary IPv6 Address. . . . . . : 2a00:23cc:c42b:9b00:796d:4f53:2272:6d82

   Temporary IPv6 Address. . . . . . : fd78:4c15:7f9d:0:796d:4f53:2272:6d82

   Link-local IPv6 Address . . . . . : fe80::870b:f8ad:9554:9c38%16

   IPv4 Address. . . . . . . . . . . : 192.168.1.125

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . : fe80::2641:feff:fe4f:4710%16

                                       192.168.1.254

 

Secondary 2

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : lan

   IPv6 Address. . . . . . . . . . . : 2a00:23cc:c42b:9b00::95

   IPv6 Address. . . . . . . . . . . : 2a00:23cc:c42b:9b00:80c5:6a70:6b4e:7d90

   IPv6 Address. . . . . . . . . . . : fd78:4c15:7f9d::95

   IPv6 Address. . . . . . . . . . . : fd78:4c15:7f9d:0:71e0:af25:d0ed:1fff

   Temporary IPv6 Address. . . . . . : 2a00:23cc:c42b:9b00:b90b:c8b6:497f:6f6c

   Temporary IPv6 Address. . . . . . : fd78:4c15:7f9d:0:b90b:c8b6:497f:6f6c

   Link-local IPv6 Address . . . . . : fe80::ea36:2ec8:b513:fb27%15

   IPv4 Address. . . . . . . . . . . : 192.168.1.95

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . : fe80::2641:feff:fe4f:4710%15

                                       192.168.1.254

Reply #8 Top

OK, I might have got a work around, although still a major bug in my eyes.

I ran the uninstall bat file supplied by Star Dock. I then restarted my PC and then did a clean instal, left the password as default and KVM and Seamless worked, changed the password and then the fun began.....