I installed a new server for one of my clients a few months back (new Windows 2012 Server). At the time, all of their local workstations were running Win 7 with no issues.
Now, one of the desktops was upgraded to Win 10 and the user intermittently gets the error shown in attachment (the other PCs in their office running Win 7 do not get this error). The user says all he has to do is click "OK" and then they can access the mapped drive, but the error keeps returning from time to time and they want it fixed.
What could have changed in Win 10 and also what can be done to resolve the issue?