Cannot see Minimserver anymore for UPNP/DLNA

[streamer99]

I, too, get an error message trying to edit these in File Station. However, they can be adjusted using SCP (WinSCP) which gives the necessary access peculiarly denied in File Station. I had forgotten that when I first came up against this issue of the accented characters a few years ago with much earlier software versions, I was not knowledgeable enough to obtain any access to the faulty files on the NAS (which would not even permit file deletion of these) and in many cases made a second corrected upload while leaving the problem files in place. Although it had the desired effect, in many cases the versions which were correctly formed in File Station then had peculiar characters displayed in windows.
The presence of the mismatched characters did not cause a problem when using HQ Player as the file manager but recently I have had occasion to use some other software players bringing MinimServer back into the picture.

[simoncn]

Windows uses the Windows-1252 character set for encoding accented characters in filenames. The NAS uses the UTF-8 character set. When copying a file from Windows to NAS or vice versa, it is important to use a method that translates filename characters between these encodings correctly.

If you are able to rename or delete these problem files, your rescan time should be much quicker. If you still have UPnP discovery issues after doing this, please post back here or in a new thread.

I think the reason this issue shows up in MinimServer but not in HQPlayer is that MinimServer is written in Java, which strictly enforces compliance with platform character set encoding rules.

[streamer99]

After quite a lot of work, my minimsever log file is now free of errors. There are still lots of warnings but I have not understood from the previous correspondence that warnings were a problem.
Nevertheless, having done this, I find that using MConnect on iphone, the Synology audio server is seen within about 10 seconds but MinimServer is taking >7 minutes to appear unless rescanning is done in which case it appears after maybe 20s but this is then required repeatedly after playing music.

[simoncn]

A warning means the file could be read but there was a problem with the tagging. An error means the file could not be read.

Fixing the errors should make a rescan go faster but will not fix UPnP network discovery problems.The difference in discovery times between MinimServer and the Synology audio server means something in your network is blocking M-SEARCH UPnP discovery messages sent by mconnect (see this post). Doing a MinimServer rescan sends an "alive" message and mconnect will receive this message.

The M-SEARCH problem could be caused by your router or some other network component. The Synology audio server is discovered more quickly because it sends very frequent "alive" messages as a workaround for possible network discovery problems. MinimServer can't do this because it uses the ohNet stack for UPnP communication and ohNet doesn't have an option to do this.

Have you tried powering all your network equipment off, then powering it all back on? This sometimes clears UPnP discovery problems.

[streamer99]

Thank you. On reviewing my network again, a small and insignificant looking switch that I had more or less forgotten was configurable had a single setting applied - igmp snooping.
You won't be surprised that unsetting that seems to have done the trick.
A few years ago we had BT TV which used multicast and required some igmp snooping settings when used with non-BT router and this may be the reason for the setting I had forgotten.