Unable to use mouse on 2nd pc when using wireless screen projection

Windows 10 dual screen projection issues

Using the latest version of Multiplicity on both my main Window 10 Pro PC and my Windows 10 Home laptop.  I primarily use Ethernet for both and have very minimal issues using it in this manner however there are times when I want to project a screen on my main pc to my laptop (using it as a dual screen) in addition to my Ethernet I turn on both Wireless cards.

Once I make the connection to the laptop and drag my screen from main pc to laptop I am unable to use Multiplicity to interact with the projected screen which is show on my laptop.  If I unload Multiplicity on the main pc, I am able to use my mouse as expected on the laptop but this is counter intuitive.

I'm not sure if there are any issue using Multiplicity with both Ethernet and WiFi enabled or if it's just confused by the virtual screen. 

I was unable to find any other posts or discussions surrounding this issue, if there are any fixes please advise. I'd appreciate any suggestions :)

14,948 views 7 replies
Reply #1 Top

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.

Basj,
Stardock Community Assistant

+1 Loading…
Reply #2 Top

While its difficult to follow exactly what you are doing, you may want to make your connections with IP instead of hostname when multiple NICs are involved, example:

Sean Drohan
Stardock Support Manager

 

+1 Loading…
Reply #4 Top

I just made the change suggested and am using the IP address associated with the Ethernet.  Unfortunately it didn't work.  What happens is the functionality of the mouse stops working immediately when the 2nd screen appears.  The only way I am able to disconnect the WiFi displays session is by using the touch screen.

I'm not sure what info I can provide to make it more clear, as you stated "its difficult to follow exactly what you are doing".  I tried to be very clear and detailed in my original description of the problem.   Please let me know what else you may need to be able to recreate this issue on your end.

Reply #5 Top

Quoting Digivix5673, reply 4

I just made the change suggested and am using the IP address associated with the Ethernet.  Unfortunately it didn't work.  What happens is the functionality of the mouse stops working immediately when the 2nd screen appears.  The only way I am able to disconnect the WiFi displays session is by using the touch screen.

I'm not sure what info I can provide to make it more clear, as you stated "its difficult to follow exactly what you are doing".  I tried to be very clear and detailed in my original description of the problem.   Please let me know what else you may need to be able to recreate this issue on your end.
End of Digivix5673's quote

The issue, that the cursor works but will not interact with the desktop (if that is indeed what you are seeing), reads like this, and its fix:

https://forums.stardock.com/486104/multiplicity-support-faq#movemousesecondary

Sean Drohan
Stardock Support Manager

Reply #6 Top

Sean, I reviewed the link you provided and then I performed the following steps, which unfortunately did not resolve the issue.

  1. I made sure the firewall on domain, public and private profiles was off, on my main pc and secondary laptop
  2. From main pc I made a connection to my laptop using the Connect feature.  WiFi is turned on both machines.  In addition, I have the IP address associated with the Ethernet specified in Multiplicity
  3. Once the connection is made, the desktop from my main pc is extended and visible on the laptop.  This is the point where the mouse cursor disappears on both screens and no matter how fast, slow and in every direction, the cursor never becomes visible.

  4. Since the laptop is touch screen I can exit the session and all mouse functionality returns as soon as the secondary screen is no longer being projected onto it.
Reply #7 Top

Well, that was my last idea.  I just cant reproduce your environment to test with I am afraid.

Sean Drohan
Stardock Support Manager