Upgrade to windows 10 => net use access denied (error 5)

uchon01

Commendable
Aug 14, 2016
3
0
1,510
Hello
I have a lab (test environment) at home with several computers and I am testing automatic (CMD) scripts on them.
I just upgraded several of the computers from windows 7 to windows 10.
At the main computer (Windows 7) there is a shared directory where all the files and scripts that I test, exist.
I have created a special user (with password) on the main computer to be the only user that is able to access these files.
When I run the scripts from the computers, I use the "net use X: \\_MAIN_COMPUTER_\_SHARE_ /user:_MAIN_COMPUTER_\_SPECIAL_USER_ _PASSWORD_" command to login to the main computer.
When I run it from computers with non Windows 10 OS there is no problem (login + copying + executing). But on the new upgraded Windows 10 computers I get the "System Error 5 has occurred. Access is Denied".
I have read in other places questions, answers and articles, but I could not find a problem like mine. (Most of the problems address a problem where the main computer was the one upgraded to Windows 10.)
Can someone please help me?
Thank you
Udi
 
Hello uchon01

I was wondering if you already tried un-sharing and then re-sharing the folder and re-applying the Shared and NTFS permissions on it?

Also, can you please confirm if you checked if any of the firewall settings need to be reconfigured accordingly?

Before going any further, I assume that the upgraded computers are able to communicate with each other and with the main Windows 7 computer, i.e. they are pinging properly.

On the Windows 10 computers, please check if the Network discovery and File and printer sharing services are turned on and the computer is using the Home or Work Network (Private) profile.

Although it has nothing to do with normal sharing, if not already done yet, can you please try enabling administrative shares on all the Participating Windows 10 Computers and also on the main Windows 7 Computer from the registry, and see if that does the trick?

Feel free to report back for any further assistance.

Cheers!! :)
 


Hi viveknayyar007.

Thank you for your answer.
1. I have tried creating from scratch the sharing and permissions. Although I thought it wouldn't help since the other computers are using the share with no problems
2. The firewall settings I will check only tomorrow (the lab is closed for today). Any suggestions on what to check especially?
3. All the computers (including the main) have ping between them.
4. The network discovery is on, although I don't remember about file and printer sharing (check that tomorrow). Also the network is defined as Home.
5. Can you please help me with a fast registry reference regarding the administrative shares?

Thank you and I will let you know immediately when I check all of your suggestions
Udi
 


Hello again uchon01

I will try to answer your questions in as simple language as possible.

However, before we try any other solution, can you please check if you can access the shared folder from within the GUI, i.e. by typing the UNC path (\\) followed by the shared folder name in the Run command box?

If you can't access the shared folder from the GUI either, please check the answers below:

"2. The firewall settings I will check only tomorrow (the lab is closed for today). Any suggestions on what to check especially?"
Generally, Network discovery and File and printer sharing are related to the firewall settings. By default, Windows Firewall blocks all incoming packets and monitors (but allows) the outgoing ones. If you don't have any third-party firewall installed on your PC and are using Windows Firewall only, you can try turning it off altogether and see if the issue is resolved. If you can access the shared folder via command line, we can then isolate the problem and resolve it. :)

"5. Can you please help me with a fast registry reference regarding the administrative shares?"
From Windows 7 onward (or probably from Windows Vista), the Administrative Shares have been disabled from the registry itself. In fact, to be more precise, there's no entry in the Windows Registry to allow Administrative shares. To know more about Administrative Shares, you can click this link. Therefore, in order to access the hidden network shares, a new 32-bit DWORD value named LocalAccountTokenFilterPolicy must be manually added to the Windows Registry that enables the Administrative Shares.

Considering this, as an administrator, it is sometimes good to enable Administrative Shares in both Windows 7 and Windows 10.

Hope this helps. Cheers!! :)
 


Hello viveknayyar007.

I turned off the firewall (I don't have a third party) but it did not help (same result).
I tried the GUI access with the same result
I have already tried the LocalAccountTokenFilterPolicy solution (plus restart) before writing here (did not help).
I have also tried the UAC solution (also did not help)

I believe that the solution is somewhere on the Windows 10 computers and not on the main computer (other OS can connect without any problem)

Thank you.
Udi
 

TRENDING THREADS