Windows 10 having issues with Access Bassed Enumeration share.

We are having an issue with an Access Based Enumeration share on a Windows 2012 R2 server with Windows 10 users.   The share is set up with Domain Users having Full Control on the share (have also tried with Everyone Full Control as well)   NTFS permissions are set on the subfolders and files.   We have no issues with users on Windows 7, however, when a Windows 10 user accesses the share (this is the only share with Access Based Enumeration, all other shares work fine) They received a message that the \\SERVERNAME\FOLDER is not accessible, Capture.PNG
If the user clicks on this share 3 times, the first two times will result in this error message, the third time the folder will open and the user can see the folders they have NTFS permissions to access.   They can also type in \\SERVERNAME\SHARE\Sub folder and have no issues accessing them.  This happens on any user who is not a member of the Domain Admin group and only when logging into a Windows 10 machine, they have no issues when logged into Windows 7.
Vincent BuggAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DonNetwork AdministratorCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<If the user clicks on this share 3 times, the first two times will result in this error message, the third time the folder will open and the user can see the folders they have NTFS permissions to access.>>

 That sounds like it is related to connections being dropped:

https://support.microsoft.com/en-us/help/297684/mapped-drive-connection-to-network-share-may-be-lost

Jim.
0
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
There also is an issue with GPO's which are set to "replace" rather than "update" connections:

https://community.spiceworks.com/topic/1139165-windows-10-losing-mapped-drives?page=2

 which causes a disconnect.

Jim.
0
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

McKnifeCommented:
So this happens on all win10 machines? If so, please take a clean, virgin win10 machine (maybe a VM) and test again with no software, especially no AV software installed.
0
Vincent BuggAuthor Commented:
Thanks for the input, I will check the GPO settings Jim.  McKnife, I did do a reload of WIndows 10 one one laptop, and also created a Windows 10 VM for another use, but I did try to access the share and it happens there as well.   Hopefully the GPO settings will help.
0
McKnifeCommented:
Since this is not about mapped drives (but UNC paths instead), I don't see how this is even connected, so no, it won't work.

If it really happens on a perfectly clean client, it's now the time to create a perfectly clean server with just one share and ABE turned on. Try that.
0
Vincent BuggAuthor Commented:
Donald, that is the exact message, but the opposite scenario, according that article, it doesn't work in Windows 7, but does work in Windows 10.  We are having the exact opposite.  I went ahead and set the permissions like the article says and it did resolve the issue.  Thank you!
0
McKnifeCommented:
"it did resolve the issue"
Vincent, your comment is confusing me.
Is it solved? The article does explicitly say these steps are not required on win10, so it should not help.
0
Vincent BuggAuthor Commented:
Yes, the issue was resolved by following  the instructions in the article, even though the article says it's a fix for Windows 7, it did resolve it for Windows 10.
0
McKnifeCommented:
Interesting. Then please mark the corresponding suggestion as solution.
0
DonNetwork AdministratorCommented:
Per the Author "  I went ahead and set the permissions like the article says and it did resolve the issue.  Thank you! "
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 10

From novice to tech pro — start learning today.