Hello! Over the last three weeks I was setting up a local file server for a school that I work for. The server runs on Linux but every other PC runs on Windows. Setting up SMB and WSDD were easy as usual, but when time to engrave files over the network came (using Windows' "Network Discovery" feature) Lilypond always threw a "can't find file" error. Powershell's "Test-Path" could find the files, but Lilypond (through Frescobaldi or directly from Powershell) couldn't. I've spent almost two to three days googling the reasoning behind this error, especially because it also happened to REAPER while reading some sample libraries. Today I came across a thread from 2018 (\include command and local network folders <https://lists.gnu.org/archive/html//lilypond-user/2018-04/msg00313.html>) that "solved" my issue: mapping the network drive to a letter (ex.: How do I map a network drive in Windows? <https://kb.netgear.com/19864/How-do-I-map-a-network-drive-in-Windows>) instead of using the server name or it's IP address. Since it was a very frustrating issue, I guess it is worth repeating some useful information. Windows always seems to surprise me, albeit in a bad way...
TL;DR: always map network drives to letters.
