Via AWS I spun up a Windows Nano Server node. I can manage this from a management server in the same VPC.
 
Using Powershell, I can access the Nano server, add the server to my network domain, create a sheduled task, create a local user group and add a domain user to it, assign user privileges to allow users in this group to run scheduled tasks.
 
This scheduled task shoud read and write to locations on our networked SAN, which lives in the same VPC.
 
But the Nano server does not allow access to the SAN.
 
if I use the Powershell Test-Path cmdlet, specifying the UNC path to a location on the SAN, it complains that access has been denied.
 
And yes, the domain user has complete access to the locations on the SAN.
 
I also tried mapping a drive letter with net use: same result.
 
I have read every document by Microsoft and every blog post and StackOverflow post I thought relevant. Only 1 other person described the same problem, and has no solution. They were on a forum for Docker, and the Docker team discovered this is a problem with Nano, and not with Docker.
 
In my set-up, I don't use containers, I don't use Docker. I guess AWS runs this Nano instance in Hyper-V, but that is outside of my reach.
 
The Samba firewall ports are open and active (File and Printer Sharing).
 
Have you encountered this problem? How did you fix it?
 
One way I can work around this problem is by reading and writing to the Nano server itself. However, I fear that such would …