Here is a good starting point to fixing this.
Have a look at Windows Desktop Experience on the server. In most cases you server does not know what to do with WebDav, which is was SharePoint uses to publish content as UNC paths.
You will find that it works 100% form a normal desktop but the path will fail on the server.
You can add the features with PowerShell in Server 2012
Add-WindowsFeature Desktop-Experience;
Add-WindowsFeature InkAndHandwritingServices;
Here is a post with pretty pictures. I personally prefer the pictures.