ROCK.
Win 11, i9 10900k, 32GB
I have the exact same issue as this.
My Roon client latches on to 192.168.137.1, which is the interface for Microsoft Virtual Adapter (for hotspot I guess), and does not connect.
How can I force/teach Roon client in Win11 to use the correct interface/IP?
What happens if you turn off Mobile hotspot sharing in Windows Network Settings?
I do not have it ON - not sure why you would assume otherwise?
Windows by default enables a LAN called Microsoft Wi-Fi Direct Virtual Adapter. I disabled the adapter, but relying on disabling a default Windows feature for Roon to work correctly does not seem like a good idea.
It appeared it was active based on your description above. I have my Roon Remote W11 PC connected via WiFi and do not have an option for an MS virtual adapter; the virtual adapter is used exclusively in Windows to share a computer’s WiFi with other devices.
If you deactivate it, does your W11 PC connect to your Roon Server? What is the IP address of the ROCK?
If you go to Control Panel → Network and Internet > Network Connections, you will see the adapter. I have 4 Win 11 devices, and it shows up everywhere. Most of them has a fresh Win 11 installation, without manufacturer bloatware, which is why I said it appears to be a default Windows feature.
Note that the adapter - Microsoft Wi-Fi Direct Virtual Adapter exists even with Hotspot disabled, and disabling the adapter seems to break the Hotspot feature.
I understand, a few other Windows features like “Projecting to this PC” also keeps this adapter enabled, and as such, disabling a default feature to make Roon work does not seem like a good idea.
Roon connects reliably after disabling the said adapter, as there is now only one active network interface available. Without that adapter disabled, it is a hit or miss.
ROCK is at 192.168.1.10, and this particular Win11 device is at 192.168.1.229.
Please keep in mind that usage is not standard nor supported. Roon is not built to work across subnets. If you have it working then that is outside the supported usage of Roon and is considered Tinkering. Roon is built to work only on a single subnet.
Moved this topic to the Tinkering category where other users may be able to provide assistance with this configuration.
that is incorrect. How is it relevant what my other endpoints are, when the issue is with Win 11 PC in the same LAN as ROCK?
Can you move it back to support rather than washing your hands off a bug by incorrectly tagging it as tinkering?
If you go to Control Panel → Network and Internet > Network Connections, you will see the adapter. I have 4 Win 11 devices, and it shows up everywhere. Most of them has a fresh Win 11 installation, without manufacturer bloatware, which is why I said it appears to be a default Windows feature.
Note that the adapter - Microsoft Wi-Fi Direct Virtual Adapter exists even with Hotspot disabled, and disabling the adapter seems to break the Hotspot feature.
I understand, a few other Windows features like “Projecting to this PC” also keeps this adapter enabled, and as such, disabling a default feature to make Roon work does not seem like a good idea.
Roon connects reliably after disabling the said adapter, as there is now only one active network interface available. Without that adapter disabled, it is a hit or miss.
ROCK is at 192.168.1.10, and this particular Win11 device is at 192.168.1.229.
Please move the ticket back. The ROCK and the Windows box are in the same LAN. It should not matter that other endpoints are not.
This is an issue with Windows machines that have Docker or VMs enabled. I also had this problem. It has nothing to do with using subnets in the network architecture.
This is easy to solve: Provide an option in the UI to select the network adapter to use under Windows.
Comment to prevent thread from closing
Hi @Priyanku_Baruah,
Please see our response here: Roon on Windows 11 uses the wrong network adapter
Roon will attempt to connect via all available network interfaces visible to the server - the option to hard-select a single adapter when multiple are available is something you’d need to add in Feature Suggestions, where other users can vote.