Windows Server 2012 R2: Which version of the SMB protocol (SMB 1.0, SMB 2.0, SMB 2.1, SMB 3.0 or SMB 3.02) are you using?

Note: This blog post is a Windows Server 2012 R2 update on a previous version focused on Windows Server 2012.


1. Introduction

With the release of Windows 8.1 and Windows Server 2012 R2, I am frequently asked about how older versions of Windows will behave when connecting to or from these new versions. Upgrading to a new version of SMB is something that happened a few times over the years and we established a process in the protocol itself by which clients and servers negotiate the highest version that both support.


2. Versions

There are several different versions of SMB used by Windows operating systems:

  • CIFS – The ancient version of SMB that was part of Microsoft Windows NT 4.0 in 1996. SMB1 supersedes this version.
  • SMB 1.0 (or SMB1) – The version used in Windows 2000, Windows XP, Windows Server 2003 and Windows Server 2003 R2
  • SMB 2.0 (or SMB2) – The version used in Windows Vista (SP1 or later) and Windows Server 2008
  • SMB 2.1 (or SMB2.1) – The version used in Windows 7 and Windows Server 2008 R2
  • SMB 3.0 (or SMB3) – The version used in Windows 8 and Windows Server 2012
  • SMB 3.02 (or SMB3) – The version used in Windows 8.1 and Windows Server 2012 R2

Windows NT is no longer supported, so CIFS is definitely out. Windows Server 2003 R2 with a current service pack is under Extended Support, so SMB1 is still around for a little while. SMB 2.x in Windows Server 2008 and Windows Server 2008 R2 are under Mainstream Support until 2015. You can find the most current information on the support lifecycle page for Windows Server. The information is subject to the Microsoft Policy Disclaimer and Change Notice.  You can use the support pages to also find support policy information for Windows XP, Windows Vista, Windows 7 and Windows 8.

In Windows 8.1 and Windows Server 2012 R2, we introduced the option to completely disable CIFS/SMB1 support, including the actual removal of the related binaries. While this is not the default configuration, we recommend disabling this older version of the protocol in scenarios where it’s not useful, like Hyper-V over SMB. You can find details about this new option in item 7 of this blog post: What’s new in SMB PowerShell in Windows Server 2012 R2.


3. Negotiated Versions

Here’s a table to help you understand what version you will end up using, depending on what Windows version is running as the SMB client and what version of Windows is running as the SMB server:

OS Windows 8.1 
WS 2012 R2
Windows 8 
WS 2012
Windows 7 
WS 2008 R2
Windows Vista 
WS 2008
Windows 8.1
WS 2012 R2
SMB 3.02 SMB 3.0 SMB 2.1 SMB 2.0 SMB 1.0
Windows 8
WS 2012
SMB 3.0 SMB 3.0 SMB 2.1 SMB 2.0 SMB 1.0
Windows 7
WS 2008 R2
SMB 2.1 SMB 2.1 SMB 2.1 SMB 2.0 SMB 1.0
Windows Vista
WS 2008
SMB 2.0 SMB 2.0 SMB 2.0 SMB 2.0 SMB 1.0
SMB 1.0 SMB 1.0 SMB 1.0 SMB 1.0 SMB 1.0

* WS = Windows Server


4. Using PowerShell to check the SMB version

In Windows 8 or Windows Server 2012, there is a new PowerShell cmdlet that can easily tell you what version of SMB the client has negotiated with the File Server. You simply access a remote file server (or create a new mapping to it) and use Get-SmbConnection. Here’s an example:

PS C:\> Get-SmbConnection

ServerName   ShareName  UserName            Credential          Dialect   NumOpens
----------   ---------  --------            ----------          -------   --------
FileServer1  IPC$       DomainName\UserN... DomainName.Testi... 3.00      0
FileServer1  FileShare  DomainName\UserN... DomainName.Testi... 3.00      14
FileServ2    FS2        DomainName\UserN... DomainName.Testi... 3.02      3 
VNX3         Share1     DomainName\UserN... DomainName.Testi... 3.00      6
Filer2       Library    DomainName\UserN... DomainName.Testi... 3.00      8

DomainCtrl1  netlogon   DomainName\Compu... DomainName.Testi... 2.10      1

In the example above, a server called “FileServer1” was able to negotiate up to version 3.0. FileServ2 can use version 3.02. That means that both the client and the server support the latest version of the SMB protocol. You can also see that another server called “DomainCtrl1” was only able to negotiate up to version 2.1. You can probably guess that it’s a domain controller running Windows Server 2008 R2. Some of the servers on the list are not running Windows, showing the dialect that these non-Windows SMB implementations negotiated with this specific Windows client.

If you just want to find the version of SMB running on your own computer, you can use a loopback share combined with the Get-SmbConnection cmdlet. Here’s an example:

PS C:\> dir \\localhost\c$
Directory: \\localhost\c$

Mode                LastWriteTime     Length Name

----                -------------     ------ ----
d----         5/19/2012   1:54 AM            PerfLogs
d-r--          6/1/2012  11:58 PM            Program Files
d-r--          6/1/2012  11:58 PM            Program Files (x86)
d-r--         5/24/2012   3:56 PM            Users
d----          6/5/2012   3:00 PM            Windows
PS C:\> Get-SmbConnection -ServerName localhost
ServerName  ShareName  UserName            Credential          Dialect  NumOpens
----------  ---------  --------            ----------          -------  --------
localhost   c$         DomainName\UserN... DomainName.Testi... 3.02     0


You have about 10 seconds after you issue the “dir” command to run the “Get-SmbConnection” cmdlet. The SMB client will tear down the connections if there is no activity between the client and the server. It might help to know that you can use the alias “gsmbc” instead of the full cmdlet name.


5. Features and Capabilities

Here’s a very short summary of what changed with each version of SMB:

  • From SMB 1.0 to SMB 2.0 - The first major redesign of SMB
    • Increased file sharing scalability
    • Improved performance
      • Request compounding
      • Asynchronous operations
      • Larger reads/writes
    • More secure and robust
      • Small command set
      • Signing now uses HMAC SHA-256 instead of MD5
      • SMB2 durability
  • From SMB 2.0 to SMB 2.1
    • File leasing improvements
    • Large MTU support
    • BranchCache
  • From SMB 2.1 to SMB 3.0
    • Availability
      • SMB Transparent Failover
      • SMB Witness
      • SMB Multichannel
    • Performance
      • SMB Scale-Out
      • SMB Direct (SMB 3.0 over RDMA)
      • SMB Multichannel
      • Directory Leasing
      • BranchCache V2
    • Backup
      • VSS for Remote File Shares
    • Security
      • SMB Encryption using AES-CCM (Optional)
      • Signing now uses AES-CMAC
    • Management
      • SMB PowerShell
      • Improved Performance Counters
      • Improved Eventing
  • From SMB 3.0 to SMB 3.02
    • Automatic rebalancing of Scale-Out File Server clients
    • Improved performance of SMB Direct (SMB over RDMA)
    • Support for multiple SMB instances on a Scale-Out File Server

You can get additional details on the SMB 2.0 improvements listed above at

You can get additional details on the SMB 3.0 improvements listed above at

You can get additional details on the SMB 3.02 improvements in Windows Server 2012 R2 at


6. Recommendation

We strongly encourage you to update to the latest version of SMB, which will give you the most scalability, the best performance, the highest availability and the most secure SMB implementation.

Keep in mind that Windows Server 2012 Hyper-V and Windows Server 2012 R2 Hyper-V only support SMB 3.0 for remote file storage. This is due mainly to the availability features (SMB Transparent Failover, SMB Witness and SMB Multichannel), which did not exist in previous versions of SMB. The additional scalability and performance is also very welcome in this virtualization scenario. The Hyper-V Best Practices Analyzer (BPA) will warn you if an older version is detected.


7. Conclusion

We’re excited about SMB3, but we are also always concerned about keeping as much backwards compatibility as possible. Both SMB 3.0 and SMB 3.02 bring several key new capabilities and we encourage you to learn more about them. We hope you will be convinced to start planning your upgrades as early as possible.


Note 1: Protocol Documentation

If you consider yourself an SMB geek and you actually want to understand the SMB NEGOTIATE command in greater detail, you can read the [MS-SMB2-Preview] protocol documentation (which covers SMB 2.0, 2.1, 3.0 and 3.02), currently available from In regards to protocol version negotiation, you should pay attention to the following sections of the document:

  • 1.7: Versioning and Capability Negotiation
  • 2.2.3: SMB2 Negotiate Request
  • 2.2.4: SMB2 Negotiate Response

Section 1.7 includes this nice state diagram describing the inner workings of protocol negotiation:


Note 2: Third-party implementations

There are several implementations of the SMB protocol from someone other than Microsoft. If you use one of those implementations of SMB, you should ask whoever is providing the implementation which version of SMB they implement for each version of their product. Here are a few of these implementations of SMB:

Please note that is not a complete list of implementations and the list is bound to become obsolete the minute I post it. Please refer to the specific implementers for up-to-date information on their specific implementations and which version and optional portions of the protocol they offer.

You also want to review the SNIA Tutorial SMB Remote File Protocol (including SMB 3.0). The SNIA Data Storage Innovation Conference (DSI’14) in April 22-24 2014 is offering an updated version of this tutorial.

Comments (37)
  1. JoseBarreto says:


    Dialect 1.5 is a valid SMB 1 dialect and many implementations (including older versions of Windows) use it.

    You see, we released many Windows versions that supported SMB1 over the years, but I did not spend any time on the blog to detail the many 1.x dialects…

    1. soder says:

      Wow, comment reply after 3,5 years hahah.. wonder if poor MartinJ was still waiting for that reply

    2. @JoseBarreto,

      Not to my knowledge.

      SMB1 dialects were named, not numbered, and there is no “SMB 1.5” dialect string listed in any of the official documentation.

      “SMB 1.5” is probably a tag that someone at Microsoft provided in order to identify the “NT LM 0.12” dialect, which is the dialect of SMB1 that has been in use since WindowsNT was released. There is, in SMB1, no higher level dialect than “NT LM 0.12”.

      It is possible that the Get-SmbConnection command displays “SMB 1.5” to indicate a particular set of advanced Capabilities that have been negotiated. Even though the dialect name hasn’t changed since WindowsNT, there have been changes and additions made to that dialect. That’s why [MS-SMB] was written as an addendum to [MS-CIFS] rather than a stand-alone document.

      So, no. Dialect 1.5 is *not* a valid SMB1 dialect. Although it is displayed, it doesn’t actually exist.

      Chris -)—–

  2. Andre Muraro says:

    wow.. You are working on this since SMB 2.0.. 🙂

    It's amazing the improvements made since there. I really enjoy each one

  3. MartinJ says:

    Hello Jose,

    So, what does it mean, when it return SMB Dialect = 1.5?

    We get this from a Windows Server 2003 SP2 DFS server, that has folder targets to an EMC NAS.

    What is 1.5? Is it DFS specific or NAS specific?

  4. stevo says:

    Great Post!  But how do you check this on a windows 7 and 2008r2 session since only 8 and 2012 have get-smbconnection cmdlet?

  5. JoseBarreto says:


    For Windows versions previous to Windows 8, you need to use packet capture program like Network Monitor, Message Analyzer or Wireshark to look into the packets and figure out the dialect. I recommend Message Analyzer, which is a free download from Microsoft.

    No easier way I know of, unless someone wrote a specific tool for it.

  6. Anonymous says:

    In this post, I'm providing a reference to the most relevant content related to Windows Server 2012

  7. Anonymous says:

    Pingback from Como usar o Compartilhamento baseado em SMB3 para Banco de Dados SQL | Marcos Dias

  8. Anonymous says:

    Pingback from Como usar o Compartilhamento baseado em SMB3 para Banco de Dados SQL | Marcos Dias

  9. Anonymous says:

    Pingback from ????????? PC????????????

  10. Anonymous says:

    Pingback from TI Especialistas Usando um compartilhamento de rede para o SQL Server

  11. Anonymous says:

    In this post, I’m providing a reference to the most relevant content related to Windows Server 2012

  12. Anonymous says:

    Introduction Windows Server 2012 R2 introduced a new version of SMB. Technically it’s SMB version 3.02

  13. Anonymous says:

    Introduction Windows Server 2012 R2 introduced a new version of SMB. Technically it’s SMB version 3.02

  14. Anonymous says:

    Hi, Matthew Walker here, I’m a Premier Field Engineer here at Microsoft specializing in Hyper-V and Failover

  15. Anonymous says:

    Almost all SAP products are now supported on Windows 2012 and SAP are in the process of certifying Windows

  16. Anonymous says:

    In the not far back point in time, there was a blog done by Matthew Walker that we felt needed to also

  17. Anonymous says:

    このポストは、9 月 29 日に投稿された Azure File Storage, now generally available の翻訳です。

    マイクロソフトはこのたび、Azure File

  18. Ian Brogden says:

    The table shows older OS negotiate to SMB1, but the state diagram has no option for this. Is this just because out of scope of the document?

  19. Maurizio says:

    Great post! Well done!!!


  20. winyl says:

    Thus all is not true. I can without problem access user/password protected smb shares on windows 10 1511 machine. But the other way around I get error: The user has not been granted the requested logon type at this computer. Which is windows 7 computer. And I have gpedit in Access this computer from network added Users,Administrator,Everyone. Have run on both Windows 7 and Windows 10 sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi and
    sc.exe config mrxsmb20 start= auto to ensure all smb protocols are available. But still can’t connect from windows 10 to windows 7 shares although I type in existent user/pass on windows 7 at windows 10 machine. W10 throws: The user has not been granted the requested logon type at this computer. Why? Does W10 can’t auto downgrade to sm2.1 to communicate with widows 7, and windows 7 can access smb3.0 on Windows 10?!?

  21. Simon M says:

    This is still the best article around for SMB, but please can you update to include SMB3.1.1, Windows 10, & Server 2016 ? Many thanks!

  22. PJD_BE says:

    From build 14921, 14926 and 14936 (Insider RS2 preview), I have no more acces to my share XP (SMB 1.0). Do you think thatt SMB is the problem ????

  23. MichaelL says:


    Will you update this excellent post related to Windows 10 and Windows Server 2016?

  24. Marek says:

    Hi Jose
    I’d like to explain using of dialect 1.5. In my environment even SMB 1 driver is not loaded on WIn2k12 R2 I can connect from/to Win 2k3 and I see dialect 1.5 is used. How it works? How can I disable dialect 1.5 on Win 2k12 R2?

    1. Chris says:

      Hi Marek,
      At an administrative command prompt, run “sc query srv” to see whether the SMB1 drivers are running. Srv (SMB1) could be set to automatic start and running, even though the LanmanServer service does not have it as a Dependency.
      To disable SMB1 you can set Srv service to disabled with “sc config srv start=disabled”.

  25. Rivka says:

    Does it means that PC’s with NT OS are not exposed to the WannaCrypt Attack?

  26. Hello,
    I have found files on my android which i cannot access because it says it needs to unlock SMB2. This is the first article thatvi have read that explains what this means and i would like to know if you can give advice as to how to proceed with that process or report such findings, as i did not initiate the protocol myself.
    Any advice would be greatly appreciated.

  27. Richard says:

    Nice article, well written and concise. Thanks for the information.


  28. Nagarjun Jermely says:

    A very good article indeed!

    Windows 2012 server supporting SMB3 version is make much difference in the market!
    Cheers to Microsoft team!

  29. Nagarjun Jermely says:

    Get-SmbConnection in Poweshell is not working and posting the below error,

    “The term ‘get-SmbConnection’ is not recognized as the name of a cmdlet, function, script file, or operable program.”

  30. Ananth says:

    Good Post!
    we have NAS on 2012 and its using SMBv1 and we want to disable it for WannaCry/ Petya , but all our PROD shares are running on this, how do we go about it is there any other option to go

  31. Jozef Lutin-Smet says:

    Is it possible to link a client using SMB1 to a server using SMB3

  32. Chris Hertel says:



    As you know, I *did* spend a lot of time documenting the many SMB1 dialects, so please pardon me if correct your comments.

    First, there never was a dialect known as “CIFS”. The name was originally intended to apply to the dialect of SMB to be released with Windows 2000, but that never actually happened. There is no SMB1 dialect string that includes the substring “CIFS”. Also, by the time the official specifications were written, the name “CIFS” was being applied to SMB as used in WindowsNT (yes, really). The SMB dialect in Windows 2000 and above was the *same dialect* (no change to the dialect string), but any additions or changes were specified in [MS-SMB] instead of [MS-CIFS].

    If you take a look at the SMB1 dialect strings supported by modern Windows (including the most recent, if you enable it), the highest-order dialect string is “NT LM 0.12”, which is the same dialect offered by WindowsNT. “NT LM 0.12” is the highest level dialect of SMB1. See: and [MS-CIFS; 1.7].

    There is also, I’m afraid, no such thing as SMB 1.5. It is not indicated in either [MS-CIFS] or [MS-SMB], and SMB2/3 doesn’t use dialect strings. (Besides, SMB2/3 numbering starts at 2.) The few reports I can find that show the 1.5 dialect indicate that it is reported in the output of the get-SmbConnection command. This is probably a bug in that command.

    “CIFS” is a myth.
    “SMB 1.5” is a bug, at best.

    Chris -)—–

Comments are closed.

Skip to main content