Access to Admin Share on Windows 10 c$ fails when connecting from Windows 7
up vote
0
down vote
favorite
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: \win10testc$ /user:win10testmyadmin
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_MACHINESOFTWAREMicrosoftWindowsCurrentVersion
PoliciesSystemLocalAccountTokenFilterPolicy = 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?
windows-7 networking windows-10 network-shares smb
asked Nov 19 at 6:24
Erik
4041720
add a comment |
up vote
0
down vote
favorite
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: \win10testc$ /user:win10testmyadmin
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_MACHINESOFTWAREMicrosoftWindowsCurrentVersion
PoliciesSystemLocalAccountTokenFilterPolicy = 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?
windows-7 networking windows-10 network-shares smb
asked Nov 19 at 6:24
Erik
4041720
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
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: \win10testc$ /user:win10testmyadmin
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_MACHINESOFTWAREMicrosoftWindowsCurrentVersion
PoliciesSystemLocalAccountTokenFilterPolicy = 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?
windows-7 networking windows-10 network-shares smb
asked Nov 19 at 6:24
Erik
4041720
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: \win10testc$ /user:win10testmyadmin
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_MACHINESOFTWAREMicrosoftWindowsCurrentVersion
PoliciesSystemLocalAccountTokenFilterPolicy = 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?
windows-7 networking windows-10 network-shares smb
windows-7 networking windows-10 network-shares smb
asked Nov 19 at 6:24
Erik
4041720
asked Nov 19 at 6:24
Erik
4041720
asked Nov 19 at 6:24
Erik
4041720
asked Nov 19 at 6:24
Erik
4041720
asked Nov 19 at 6:24
Erik
4041720
4041720
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1376610%2faccess-to-admin-share-on-windows-10-c-fails-when-connecting-from-windows-7%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
