I too had the same issue on one Server 2016 file share. I made an adjustment to our Windows DNS local host which appears to have solved this issue. I noticed, in the DNS, that there was some old computers, long since removed from our network, with the
same IP entry as that file host. I nuked the bad DNS entries for the old systems. Waited for DNS propagation. I then, for good measure, added the file server in the local hosts file. I removed the mapped drives from the local workstations, rebooted, and
allow the Group Policy to re-add the mapped drives. Worked great after several workstations, several reboots.
Might not work for you, but this has been my troubleshooting experience.
Astarr