Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, March 26, 2018 5:11 PM
With the latest Creator Update, I can no longer access file shares in the Windows 10 machines from either of our remote subnets. The VPN, Firewall, and Router are all configured and unchanged. File sharing works for the non-Creator update machines as well as the 2012 Server, but not for the machines which are on Windows 10 version 1709 (though it worked on all of them proir to the 1709 update). Also, the files shares work fine on the local subnet in each location.
I assume that there was some new security feature added which is blocking the file share across remote subnets, but I cannot find any information on it. Is there some setting or configuration change that I can change to make this work?
All replies (3)
Tuesday, March 27, 2018 4:49 AM
Hi,
I found someone else who found the problem and a fix (for me anyway).
https://tech.nicolonsky.ch/windows-10-1709-cannot-access-smb2-share-guest-access/
MS has an article now to.
Essentially 1709 disables unauthenticated access to shares using SMB2. There is a GPO that can easily be flipped to fix the problem if setting up auth isn't an option. Here is the policy in question.
Computer configuration\administrative templates\network\Lanman Workstation "Enable insecure guest logons"
Best Regards,
Tao
Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, March 27, 2018 4:04 PM
I'm afraid that isn't my problem. I am not trying to use guest access but attempting to connect to a file share using a windows network account. However, it does not even give me the option to enter the credentials. Instead the result is as if the computer is not at all accessible, though it is. I can remote desktop to it, I can access the file shares from the local subnet, and I can access file shares on any system which is not running Windows 10 Version 1709.
The only error message that I get is that \<servername> is unavailable.
Tuesday, April 3, 2018 2:16 AM
We haven’t heard from you for a couple of days, have you solved the problem?
Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact [email protected].