Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Windows 10 Cannot Access Windows 7 Admin Shares

I've posted this question at Spiceworks with no luck.  Then it hit me that PDQ utilizes admin shares so I'm hoping someone in this community may have more insight.  

In our business, we do a lot of admin work using the built in admin shares. PDQ Deploy will obviously not run if we cannot access the admin shares.  A Windows 10 PC cannot connect to a Windows 7 PC's Admin Share without issuing the following commands to first disable SMBv2/3 on the Windows 10 PC:

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled

This solution works but is very problematic for us as we want to disable SMBv1 all together. Any help with this issue would be appreciated.

0

Comments

4 comments
Date Votes
  • Why are you disabling SMBv2/3 on Win 10 and not forcing SMBv2/3 on your windows 7 clients? Seems like you are going about tackling your problem backwards to me.

    0
  • Sadly, that doesn't work.  I removed SMBv1 support from both Windows 10 and Windows 7.  I still cannot connect unless I re-enable SMBv1..

    0
  • I have SMBv1 completely disabled on all of my Windows 7 desktops as well as the Windows 10 desktops and have no issue hitting the Admin Share on any of my machines.

    I also administrate all of my machines from a Windows 10 machine.

    Is there a possibility that you have some SMB settings setup in a GPO somewhere?

    I disabled mine via GPO but the following article was helpful in my venture to kill SMBv1.

    https://support.microsoft.com/en-us/help/2696547

    0
  • After a few months, I've finally stumbled across a solution:

    Set GPO: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network server: Server SPN target name validation level to Off.  Then run gpupdate /force and reboot. 

    If set to Not Configured, the problem exists.

    https://social.technet.microsoft.com/Forums/en-US/46a0b743-091b-484e-a6f4-ed727e77eb97/windows-10-1703-access-denied-to-c?forum=win10itprosecurity 

    0