Windows 10 Version 20H2 and SMBv1

Alan Koop 41 Reputation points
2021-05-20T15:35:29.823+00:00

I know that SMB1 is not a secure protocol but I have a need to be able to connect to an older NAS device that contains install files for my company. I have enable SMB1 client in Windows 10 features and had not issues access the NAS devices on numerous laptops. I am now setting up a new laptop running Windows 10 Version 20H2 and I enabled the SMB1 client, rebooted the laptop but I still cannot connect. I can ping the device, I can even connect to a different share on the NAS via NFS but not SMB1. I verified the SMB1 is enabled via Powershell but I cannot figure out why I cannot connect.

Anyone have any ideas?

Windows 10 Network
Windows 10 Network
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Network: A group of devices that communicate either wirelessly or via a physical connection.
2,385 questions
0 comments No comments
{count} votes

Accepted answer
  1. Gary Nebbett 6,111 Reputation points
    2021-05-21T19:27:23.353+00:00

    Hello @Alan Koop ,

    Your client seems to have RequireSecuritySignature set to True (the PowerShell cmdlet Get-SmbClientConfiguration will show you the current state).

    Out-of-the-box, this value is set to false. I just set it to true on my PC with the command "Set-SmbClientConfiguration -RequireSecuritySignature $True" and now my PC behaves like yours (i.e. skips the SMB_COM_NEGOTIATE(114) step).

    You could try setting RequireSecuritySignature to false and repeating the test. Let us know what happens.

    Gary


7 additional answers

Sort by: Most helpful
  1. Kapil Arya 8,211 Reputation points MVP
    2021-05-21T06:28:40.353+00:00

    Hello,

    Using SMBv1 is obviously not recommended due to security issues. Check if you've SMBv2 enabled with this command:

    Get-SmbServerConfiguration | Select EnableSMB2Protocol

    If not, try enabling it and see if it helps you to resolve the issue.

    Regards.

    0 comments No comments

  2. Candy Luo 12,751 Reputation points Microsoft Vendor
    2021-05-21T07:12:48.21+00:00

    Hi ,

    Before going further, I would appreciate your help in clarifying the following situations:

    1.When you cannot connect to old NAS from windows 10 20H2, what's the exact error message? Post the exact error message to help us identify the issue.

    2.How did you connect to old NAS? Via \IP address or \hostname?

    3.Please check SMBclient log on your windows 10 20H2 to see if there something related for us to do 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.


  3. Alan Koop 41 Reputation points
    2021-05-21T13:57:32.627+00:00

    Here is the Event Log Entry
    Log Name: Microsoft-Windows-SmbClient/Audit
    Source: Microsoft-Windows-SMBClient
    Date: 5/21/2021 9:43:31 AM
    Event ID: 32002
    Task Category: None
    Level: Information
    Keywords: (4)
    User: SYSTEM
    Computer: ComputerName.Domain.Name
    Description:
    The local computer received an SMB1 negotiate response.

    Dialect: Smb2DiagReasonNotSpecified

    SecurityMode 0x3203

    Server name: \XXX.XXX.XXX.XXX (NAS IP ADDRESS)

    Guidance:
    SMB1 is deprecated and should not be installed nor enabled. For more information, see https://go.microsoft.com/fwlink/?linkid=852747.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-SMBClient" Guid="{988c59c5-0a1c-45b6-a555-0c62276e327d}" />
    <EventID>32002</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x100000000000004</Keywords>
    <TimeCreated SystemTime="2021-05-21T13:43:31.5745611Z" />
    <EventRecordID>18</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="10252" />
    <Channel>Microsoft-Windows-SmbClient/Audit</Channel>
    <Computer>ComputerName.Domain.Name</Computer>
    <Security UserID="X-X-X-XX" />
    </System>
    <EventData>
    <Data Name="Reason">0</Data>
    <Data Name="Dialect">5</Data>
    <Data Name="SecurityMode">12803</Data>
    <Data Name="ServerNameLength">13</Data>
    <Data Name="ServerName">\NAS IP ADDRESS</Data>
    </EventData>
    </Event>

    0 comments No comments

  4. Alan Koop 41 Reputation points
    2021-05-21T14:38:07.14+00:00

    I cannot enable SMBv2 on the NAS it is an older device. We only use this to store install files and use it like this. Normally I enable SMBv1, attach to the NAS install the needed applications, then disconnect and disable SMBv1.

    If I try to access the NAS using either \hostname or \IP Address it says Windows cannot access \hostname Error code: 0x80070043

    I am able to ping the device and we have a second older NAS device that is giving me the same issue but on that NAS NFS is enabled so if I use \hostname it returns the NFS share, so I know it is not a DNS issue.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.