Wrong public network detection + no audio sharing

from Stardock Forums

Good morning,

I'm trying to evaluate switching to Multiplicity, and one of the first problems I ran into is a warning about my network being public when it's not.  Still, things look like they're working fine except when I tried to turn on audio sharing.

I think that this might be related to the wrong detection of a public network, since the audio sharing tab shows "[ ]" under the machine name -- no IP shown.

This machine has a bunch of other network connections (VPN, hyperv), which might be what causes the problem.

Any advice is appreciated.

multiplicity
2,406 views 5 replies
Reply #1 from Stardock Forums Top

Can you post the results of running ipconfig here?

Reply #2 from Stardock Forums Top 
Windows IP Configuration

Unknown adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter Ethernet 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter vEthernet (External Virtual Switch):

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::3641:e818:3e8f:f46b%6
   IPv4 Address. . . . . . . . . . . : 10.10.10.10
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.10.10.1

Ethernet adapter Bluetooth Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter vEthernet (Default Switch):

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::e4af:b847:5ac9:dc72%17
   IPv4 Address. . . . . . . . . . . : 172.25.144.1
   Subnet Mask . . . . . . . . . . . : 255.255.240.0
   Default Gateway . . . . . . . . . :

Ethernet adapter vEthernet (WSL (Hyper-V firewall)):

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::63ee:ebbc:95a2:4c13%30
   IPv4 Address. . . . . . . . . . . : 172.19.16.1
   Subnet Mask . . . . . . . . . . . : 255.255.240.0
   Default Gateway . . . . . . . . . :
Curtains - Customize Windows with additional styles
Reply #3 from Stardock Forums Top

In order to not show pointless IP addresses in the UI, Multiplicity will filter out all Bluetooth, vEthernet and VMWare / VirtualPC Network adapters.

This will be why the IP shown in audio sharing is not there as you have no connections that are live which are not one of those types.

The firewall warning is because your computer is telling Multiplicity that it is not in domain or private mode.  This may be a side effect of your strange networking setup and it may be the firewall is entirely disabled on the actual network adapter in use but we can only use the information the OS tells us which is the current profile isn't one of those modes.

As for why audio sharing isn't working, when you manually enter the IP address of the remote end and press save does it instantly fail or after a few seconds?  Or if that doesn't complain then the other possibility is the machine doing the sending is a device which auto disables the audio circuitry when muted (which is what happens when MP audio is transmitted) 

Reply #4 from Stardock Forums Top
  1. Is the network thing the actual cause of not audio sharing not working?  If so, does it do the filtering based on the name?  (I don't know what made it use the names (it's a WSL setup), but the vEthernet with the 10.10.10.10 IP is my actual connection.)
    If it only affects displaying the IP, then I won't care, of course.

  2. Re the firewall: same question -- is this actually making it not start stuff or is it just a cosmetic effect of showing the warning.  FWIW, in the windows settings, the connection is shown as "Ethernet" and as a Private network (with no way to change it).
    Sidenote: the firewall is active, and has the multiplicity rules added (including the one for the audio port).

  3.  On the sending machine the failure is after a few seconds regardless of IP or name.  AFAICT, it never starts, so muting is not the issue.
Reply #5 from Stardock Forums Top

OK, so after some more quality time with trying out multiple tweaks, I managed to sort it out.

One random SO question said that windows sandbox can lead to duplicate vethernet devices.  Disabling it didn't work.

I eventually tried Hyper-V: in the Virtual Switch Manager I changed my external virtual switch from External to Private, and that seemed to do the trick.

I now have both the audio receiving and the seamless display work (that wasn't working either, which seemed like the same problem).

In the process of doing this I ran into a bunch of bugs & issues, I'll describe some in a different post.