|
|
Peke, can you elaborate in a deeper detail? Re: Windows on first connected LAN/WiFi connection asks if connection is Private or public What do you mean by this? Do you mean the default Windows Firewall asking user to enable MM5 for private/public connections or do you mean something different? What do you mean by "public" connection? What exactly you tested with exact steps? Are you referring issue that MM5 server isn't seen by MMA? If that's the case then SSDP discovery fails (or is disabled), but if other servers are seen in MMA then most likely MM5 is blocked by Windows firewall. Supposing you mean the Windows Firewall blocking private connetions then it is driven by the firewall rules, see the section 2.2.2 here: https://www.mediamonkey.com/support/knowledge-base/mediamonkey-upnp-dlna/mediamonkey-upnp-server-inaccessible/ Threfore MM5 creates own 'MediaMonkey auto-conf' rules that allows the private connetions even if the user did not accept it initially. The problem is that for the 'auto-conf' firewall rules MM5 needs admin access so user needs to accept our UAC prompt. If the prompt isn't accepted then the rules cannot be created. And also note that recently we disabled the 'auto-conf' firewall rules creation for portable installs -- details in 0017209 You can test this by installing MM5 to another foder -- which will result in creating firewall rules for the new install location and you can check the rules in the Windows Firewall, more the section 2.2.2 in the above KB article |
|
|
This bug do not have any relations to Windows Prompt of Public/Private when connecting. Code I supplied Checks Current Windows setting if Connection is Public or Private as if it is public, per definition all incoming connections are blocked (See attached image). So once this code detect that Current active user connection (be that WiFi or LAN) is Public, we can show Notification that MM5 can't share files over DLNA not will be available for WiFi sync. Windows by default on WiFi connection set that first WiFi connection is Private (eg. normal WLAN) and that all rest connections can be treated as Public that isolate PC from other devices on network (There is also option to not ask anymore). As a result of Public network setting, nor MMA nor any other Share Services are seen over network. SSDP and other packets are simply sent to black hole and not responded to avoid non needed notifications, ports appear to be open but they are unreachable. That setting is not affected by firewall rules. Once this is implemented and MM can detect Public Connection Type, we can create new KB ARticle on how to allow MM thru firewall or in section 2.2.2 explain how to do that (most likely with similar picture to one attached). ATM if Conection is set to PUBLIC MM5 can't determine if DLNA/Sync server is visible to other devices on network. HINT: On routers it is called Guest Network, AP isolation or in some more advanced routers you can set option that WiFi devices can't access Intranet (LAN). If needed I can provide you with pictures. bug17917.png (91,353 bytes) |
|
|
I can't find this kind of settings on my Windows 10 laptop, is it something specific to certain Windows versions only? Anyhow, isn't it rather something for KB article? i.e. to expand current: https://www.mediamonkey.com/support/knowledge-base/mediamonkey-upnp-dlna/mediamonkey-upnp-server-inaccessible/ EDIT: It seems item 4) currently there in the KB article ? My "Network and Sharing Center”" looks like this (i.e. no public/private settings as on your screenshot above): |
|
|
Click on Properties and you will get option to select Private/Public like on my picture. When you use example from ~0063437 you can clearly check settings and detect which one is which. Re KB: Like you many other users do not need too be familiar with these settings. It is OK to have it in KB, but it is essential that MM itself warn user of possible issues with corrent settings on a PC. image-2.png (202,008 bytes) |
|
|
Yes, I can see it now on Win11 and acutally am surprised that Public profile is recommended? :-/ image-3.png (28,367 bytes) |
|
|
So yes, definitely moving targe to 5.1 to detect the Public profile and warn the user (to eliminate eSupport requests) As for the KB, seeing it as item 3 here: https://www.mediamonkey.com/support/knowledge-base/mediamonkey-upnp-dlna/mediamonkey-upnp-server-inaccessible/ EDIT: Tested switching to Public profile and I can confirm the issues in 0019537 and also that MM5 server is no longer accessible from MMA then.. EDIT2: BTW: There seem to be also a way how to change the profile from Public to Private programatically, it just needs the UAC/admin privileges: https://learn.microsoft.com/en-us/windows/win32/api/netlistmgr/nf-netlistmgr-inetwork-setcategory |
|
|
I am thinking about a message like: "Your network connection is set to Public. This may cause that your device won't be discoverable by other devices on the network. If you are at home network then you might want to switch to Private profile instead. Do you wish to proceed?" [Yes][No] -- that would be shown once Public profile is detected and our custom firewall rules are about to be added. If the user clicks [No] then no firewall rules and no UAC. If the user clicks [Yes] then UAC will be shown, profile changed from Public to Private and our firewall rules created. |
|
|
The rationale to suggest switching to Private profile is that Network discovery is OFF (by default) on Public networks image-4.png (28,223 bytes) |
|
|
Implemented in 5.1.0.2680 After verification assign to Rusty to review the wording. |
|
|
image-5.png (24,537 bytes) |
|
|
Minor tweaks to language: Your network connection is set to 'Public'. This usually sets your device to not be discoverable by other devices on the network. If you're at home then you might want to switch to 'Private' instead. Do you wish to proceed?" Also, does this dialog appear repeatedly (e.g. if a user has intentionally configured their PC to a public network profile, it would be annoying for this to appear repeatedly)? |
|
|
Wording adjusted... >>Also, does this dialog appear repeatedly (e.g. if a user has intentionally configured their PC to a public network profile, it would be annoying for this to appear repeatedly)?<< No, this isn't shown repeatedly, it is shown only when the firewall exception is about to be written. i.e. on clean install or whenever the '[..] Add Windows firewall exception' checkbox state is manually changed by user. |
|
|
BTW: I wonder whether I should merge the dialog into 5.0.4 even if the dialog text would be untranslated? The rationale it that starting from Windows 11 the default network profile is Public ( https://support.microsoft.com/en-us/windows/make-a-wi-fi-network-public-or-private-in-windows-0460117d-8d3e-a7ac-f003-7a0da607448d ), but network discovery if OFF (by default) on Public profiles. So it will probably will raise a number of eSupport requests (until 5.1 is out). |
|
|
The downside is that it would appear for many users when the wizard is run (i.e. on first install/run). On the other hand it would help many of those users, so probably a good idea. Re-opening to add to 5.0.4. |
|
|
OK, merged to 5.0.4.2683 |
|
|
Verified 2683 according to fix in 0019537 |
|
|
Reverified 2684 |
- Anonymous
