Windows 10 file share access to Server 2012-2019 fails with Access Violation.

Question

I have read many of the postings on Win10 and issues with file shares. My issues are as follows:

I have Server 2012/2012R2 and 2019 (2019 being evaluated)

• Non-Domain
• Local User account setup: UserTest (tested as local user and administrator levels)
• Shared a test folder on each system
• Wins is running on the server and all test systems have Wins pointed correctly.

When I try to access a share from Win10

• In File Explorer, I expand Network
• Servers are present/listed
• When I click on one of the server names, I am prompted to login.
• I try login with server1\UserTest and password
• I try login with server1\administrator and password
• All login test fail with Access Denied

From the 2012R2 server, I can see all of the shares on the 2019 server.

• I can click on one of the 2019 test shares and when prompted for username/password, I enter the same information as under the Win10 testing. It works.

From 2019 to 2012R2, the same results as from the 2012 server.

• I cannot find any issues with the basic server side accounts or file share definitions. I used the Server Manager-File and Storage Service-Shares to define shares.
• Windows Defender/Firewall has Advanced Sharing setting enabled.
• Both 2012 and 2019 will not allow enabling Network discovery. I can click the button but upon saving, Discovery is turned off.

The 2012R2/2019 server is replacing an EOL NAS which has worked well for many years. Win10 access file shares on the NAS (Qnap) just fine. I do intend to install Hyper-V to run a couple of other apps. I did have Hyper-V installed early on in the testing, but with installed with no VMS the server did not appear in the Win10 Network listing. Once I removed Hyper-V, the server appears but cannot be access - Access Denied issue above.

Server 2012R2 is a Standard with GUI. 2019 is Standard with GUI.

You input is appreciated.

Bob

Answer 1

Hi ,

Based on my understanding, Windows 10 cannot access server 2019 and server 2012's shared file. Is that right? Please feel free to let me know if I have any misunderstanding.

Could you access the share via UNC path with \IP address or hostname\share? If not, please post the exact error message , also check SMB client log on windows 10 and SMB server log on server 2012/2019 to see if there are something related for us to troubleshooting.

Best Regards,

Candy

--------------------------------------------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

The Windows 10 system is at 20H2. Both 2012 and 2019 servers are patched fully using Windows Update.

Answer 3

Hi,
Thanks for the reply. Your assumption is correct. I am trying to mount shared folders located on either my 2012 server or my test 2019 server. Both servers run Standard. The 2019 server was just installed for evaluation so it is unlicensed.

For testing, I created a file share via the browser server/file and share management giving full control to a test account Bobm. I did the same on the 2012 server. [I have not used the 2012 server for years to actually share files as that was done on the Qnap NAS only.]

From a windows 10 system, mounting a share using the Map Network Drive function or using net use commands fail to both servers. I entered a mix of syntax statements. \s2012\test with credentials for s2020\bobm with password. Same syntax for \2019. IP address version \192.168.0.2\bobm and the same for the 2019 server. And \s2012.test.net\bobm with credentials. same for the 2019 server. In all cases, the command execution seems to pause for a bit then returns Access denied. From the command line, the error message is System error 5 has occurred. Access is denied.

I cannot Net View with server as both return Access Denied from this command.

The file explorer lists the 2019 server under Networks but as above, access to view shares is denied.

I did check the SMB logs on both 10 client and 2019 server. None of the Client or Server lots (connectivity or security) seem to have anything of use in them. A lot of background information and warnings but no login or access errors. Looking at the SMB Server Audit log on the 2019 server does shows that the 2012 server is reported to be using SMB1 protocols. Are there setting that need to added to windows 10 or either server to use other versions of SMB?

Additionally, I used a Windows 8.1 laptop and successfully mounted both test directories, one on S1 and one on S2 so it appears access from older windows systems works. I was able to create directories and files as a test. On S1 I also created a test iSCSI virtual disk, defined it for access, mounted it on the 8.1 system and it works fine.

I will test iSCSI from the windows 10 client today.

I am still able to access shares on the Qnap NAS from both windows 10 and 8.1. It is only shares from windows server that are failing.

Neither server is running in a domain. I do plan to re-add hyper-v to the 2019 server for testing at some point. I did have it installed but removed it when I discovered I could not access file shares.

Answer 4

Hi. Problem identified and fixed. Following your questions, I looked into many of the SMB error log entries. The Information message about network timeout led me to investigate issues on the server and my win10 desktop. Initially, I found no issues and my security software was not reporting issues either. The network seemed to be running correctly so I focused on the security software. The initial investigation showed no reported issues. I went back to the network and cleared all of the interface configurations, disabled all devices except for 1 device and tried to access the share again. This time when I went into the security management software, there were errors noted that several protocols were blocked because they did not have device specific (server in this case) rules. I created rules for SMB access from my desktop to server and everything works now.

Going through your questions help my investigation.

This issue can be closed.

Bob