I'm trying to run pandoc, on Windows, against a file on a network share.  I'm calling the executable within a Powershell prompt, but the same behavior happens in CMD.  I have tried calling

pandoc "\\network\path\to\file.md"

and changing to the UNC folder in Powershell and calling

pandoc .\file.md

and get the same error message: "openBinaryFile: does not exist (no such file or directory". 

My hunch is that pandoc doesn't support UNC paths, but I haven't been able to find a quick explicit answer as to whether this should work or not.  If it isn't supported I'll give up and move on, but if it is - what might I be doing wrong?