MinimServer Forum
Kazoo doesn't see MinimServer when using 2 network adapters on the same subnet - Printable Version

+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: Support (/forumdisplay.php?fid=4)
+--- Thread: Kazoo doesn't see MinimServer when using 2 network adapters on the same subnet (/showthread.php?tid=7461)

Pages: 1 2


Kazoo doesn't see MinimServer when using 2 network adapters on the same subnet - eseb63 - 27-01-2025 23:48

hello,
i would like to test minimserver features, so i installed it on a synology NAS but i encounter some issues to use with some control points/renderers (on Windows 10).

for the moment, i use foobar2000 as upnp renderer (with old foo_upnp plugin).

for the control points, i tried :
- dbPowerAmp "Asset Control" : it recognizes MinimServer and plays on Foobar
- Linn Kinsky : MinimServer is found and a room is created with Foobar

these products are quite old, sometimes abandonned, so i tried the more recent Linn Kazoo, but it didn't work :
issue 1 : no room
issue 2 : MinimServer is not found

issue 1 : i read that kazoo needs openhome compliant renderer ; i installed BubbleUpnp Server and created an openhome renderer for Foobar ; but Kazoo doesn't recognize it ... (it is well seen by Kinsky)

issue 2 : i installed minimWatch to see if it would find MinimServer : it didn't either (the icon is greyed).

i restarted PC, NAS, software, disabled the firewall : nothing changed.

i endly disabled the 4G Box, and it solved the issue 2 : Kazoo and MinimWatch find MinimServer on the NAS (the issue 1 remains).
If enabled again, MinimServer is not found anymore.

i have two network adapters on my PC :
- one is connected to an ADSL box which handles the local network (DHCP active)
- another is connected to a 4G box, to boost internet because the ADSL box is very slow (DHCP inactive)
- the two boxes are on the same subnet : 192.168.1.0
- a setting in windows gives priority to the 4G box connection.

MinimWatch log:
MinimWatch 2.2 update 116, Copyright © 2012-2024 Simon Nash. All rights reserved.
Java™ SE Runtime Environment (build 1.8.0_441-b07)
Java HotSpot™ 64-Bit Server VM (build 25.441-b07, mixed mode)
Platform default charset is windows-1252
System platform is windows-x64
UPnP port 9791 has been selected
Single subnet 192.168.1.0 has been selected
Startup complete


any idea
- to make Minimserver found while using 4g connection?
- to make Kazoo recognize Foobar room ?

thanks in advance for the reply


RE: Kazoo don't see MinimServer when using 2 network adapters on the same subnet - Peter@57m - 28-01-2025 08:12

In Kazoo Settings under App Settings there is the ability to select the Subnet. Is the correct one selected?


RE: Kazoo doesn't see MinimServer when using 2 network adapters on the same subnet - eseb63 - 28-01-2025 10:56

(28-01-2025 08:12)Peter@57m Wrote:  In Kazoo Settings under App Settings there is the ability to select the Subnet. Is the correct one selected?

yes, it's 192.168.1.0


RE: Kazoo doesn't see MinimServer when using 2 network adapters on the same subnet - stefano_mbp - 28-01-2025 11:02

Check if Windows Network type is Private


RE: Kazoo doesn't see MinimServer when using 2 network adapters on the same subnet - simoncn - 28-01-2025 12:33

MinimWatch uses the ohNet stack for UPnP support. ohNet can only use one network adapter for each subnet. If there is more than one network adapter on the same subnet, ohNet makes an arbitrary selection of which adapter to use. It sounds like ohNet is selecting the 4G adapter for MinimWatch to use. The only way to ensure that ohNet selects the ADSL adapter is to put the ADSL adapter and the 4G adapter on different subnets. This applies to Kazoo as well because Kazoo also uses the ohNet stack.

Kinsky supports both UPnP/DLNA renderers and OpenHome renderers. Kazoo supports OpenHome renderers only. If foo_upnp is creating a UPnP/DLNA renderer, Kazoo will not see it as a room. You can work around this by using BubbleUPnP Server to create a proxy OpenHome renderer for the foo_upnp renderer.


RE: Kazoo doesn't see MinimServer when using 2 network adapters on the same subnet - eseb63 - 28-01-2025 13:09

(28-01-2025 11:02)stefano_mbp Wrote:  Check if Windows Network type is Private

Windows Network type is private


RE: Kazoo doesn't see MinimServer when using 2 network adapters on the same subnet - eseb63 - 28-01-2025 13:24

(28-01-2025 12:33)simoncn Wrote:  MinimWatch uses the ohNet stack for UPnP support. ohNet can only use one network adapter for each subnet. If there is more than one network adapter on the same subnet, ohNet makes an arbitrary selection of which adapter to use. It sounds like ohNet is selecting the 4G adapter for MinimWatch to use. The only way to ensure that ohNet selects the ADSL adapter is to put the ADSL adapter and the 4G adapter on different subnets. This applies to Kazoo as well because Kazoo also uses the ohNet stack.

i hoped it would exist another fix, i'll try to do so...

(28-01-2025 12:33)simoncn Wrote:  Kazoo supports OpenHome renderers only.
...
You can work around this by using BubbleUPnP Server to create a proxy OpenHome renderer for the foo_upnp renderer.

that's i did as said in my initial post : BubbleUPnp Server creates the OPenHome renderer for foo_upnp renderer, but Kazoo doesn't recognize it (Kinsky does)


RE: Kazoo doesn't see MinimServer when using 2 network adapters on the same subnet - simoncn - 28-01-2025 14:00

(28-01-2025 13:24)eseb63 Wrote:  that's i did as said in my initial post : BubbleUPnp Server creates the OPenHome renderer for foo_upnp renderer, but Kazoo doesn't recognize it (Kinsky does)

Apologies for missing that. There might be a problem when BubbleUPnP Server is used with foo_upnp that doesn't occur when BubbleUPnP Server is used with other UPnP/DLNA renderers. You could contact the author of BubbleUPnP Server (he is also the author of foo_upnp) to ask about this.


RE: Kazoo doesn't see MinimServer when using 2 network adapters on the same subnet - eseb63 - 28-01-2025 15:38

(28-01-2025 14:00)simoncn Wrote:  There might be a problem when BubbleUPnP Server is used with foo_upnp that doesn't occur when BubbleUPnP Server is used with other UPnP/DLNA renderers. You could contact the author of BubbleUPnP Server (he is also the author of foo_upnp) to ask about this.

thanks for this information...

i changed the 4G network adapter subnet : Kazoo and MinimWatch now find MinimServer when using the two adapters ; thanks for the advice.

PS : does exist a recent alternative to Kazoo (for Windows 10), fully compatible with MinimServer ?


RE: Kazoo doesn't see MinimServer when using 2 network adapters on the same subnet - eseb63 - 28-01-2025 17:11

my issue with Kazoo and Foobar renderer is solved.

before asking to the author, i made other investigations and found this :
https://groups.google.com/g/problacasbo/c/tMecjx9pAoU/m/qFPiJd-RCgAJ
we can read : "Note: if you have installed BubbleUPnPServer on Windows, you cannot run Linn Kazoo on the same computer. You will need to install Kazoo on a different computer or use a phone or tablet for the controller."

so, i stopped the BubbleUPnPServer service on my PC, installed BubbleUPnPServer on the NAS, created the openhome renderer for the Foobar renderer from the NAS and ... Kazoo instantly recognized it.

i will test MinimServer now ...

PS : does exist a recent alternative to Kazoo (for Windows 10), fully compatible with MinimServer ?