I currently try to figure out why the following command to access my Windows 10 Pwo (Version 1607) "server" fails when executed from a Windows 7 Pro workstation, whereas it works when executed from another Windows 10 Pro Workstation as a client:
net use q: \\win10test\c$ /user:win10test\myadmin
The details: win10test is the "server" which has Admin shares enabled. myadmin is a local user that has administrative privileges. Also, UAC is completely disabled on the server. In addition, the registry key to fix the wellknown UAC remote restrictions is set as follows:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion \Policies\System\LocalAccountTokenFilterPolicy = 1 (REG_DWORD (32-bit))
What I also tried is to enable or disable the different SMB versions, currently SMBV1 and V2/3 are enabled on both clients as well as servers.
All my clients that I try to connect to the Windows 10 server are located in the same local subnet. What I observe now is the following behaviour:
every Windows 10 client (I have multiple test systems in my network) can access the "server" using the net use command without any problems.
every Windows 7 client fails with the following message:
System error 5 has occurred. - Access is denied.
I do not have a good explanation for this behaviour. Can anybody provide more hints what to try?
Another hint: Currently, I observe this behaviour only in the Windows 10 1607 LTSB version, but I am not really sure if that si the culprit.