Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Windows 10 client to Server 2012 mapped drive intermittent access error

  • Please log in to reply
1 reply to this topic

#1 sunmicroman


  • Members
  • 1 posts
  • Local time:05:34 AM

Posted 10 December 2015 - 04:18 PM

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?



Attached Files

BC AdBot (Login to Remove)


#2 sflatechguy


  • BC Advisor
  • 2,266 posts
  • Gender:Male
  • Local time:07:34 AM

Posted 13 December 2015 - 02:40 PM

Is network discovery turned on? Can the user navigate to the mapped drive using \\nameofmappeddrive without getting the error message? Have you tried removing and creating the mapping to see if that resolves it?

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users