Enter your idea, suggestion or describe your problem

Update SMB protocol

Is there any chance of updating the SMB implementation? My server logs indicate Solid Explorer is requesting NT LM 0.12, which was introduced in Windows XP. I'm lowering my security settings to allow a connection for now, but it would be lovely not to have to do that. :<

815 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Paul shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
completed  ·  AdminKrzysztof Głodowski (Owner, NeatBytes) responded  · 


The latest beta of Solid Explorer has support for SMB v2, which is going to replace the old SMB v1 client. For test purposes, the client is available as a separate item in the connection wizard. After the final release, it’s going to be integrated back into one SMB client.

In order to join the beta, please visit this link: https://play.google.com/apps/testing/pl.solidexplorer2

Please note, that despite many tests, the new SMB client may still be unstable. Please use with caution. Any feedback will be very appreciated.


Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
  • Edd commented  ·   ·  Flag as inappropriate

    v2 stopped working for me also after last update of Windows 10 Build 1803 Spring Creators.
    Works fine with ES Explorer

  • Anonymous commented  ·   ·  Flag as inappropriate

    v2 is broken for me connecting to Windows 10 and Apple TimeCapsule.
    v1 works just fine for both.

  • Ross commented  ·   ·  Flag as inappropriate

    Win10 - Was working but recently it stopped, ES still working?

  • dk commented  ·   ·  Flag as inappropriate

    Smb2 not working in beta or normal version. Using Windows 10. Other file browser apps like FX and x-plore work fine.

  • OS commented  ·   ·  Flag as inappropriate

    I just dld Solid Explorer 2.4 and signed up as beta tester. But I still can't find the SMB button in "New" or anywhere else. How to I connect to my PC via SMB with SE2.4??

  • Suitcase commented  ·   ·  Flag as inappropriate

    Hello, Using SMBv2 in the latest stable update.
    Can connect to my PC with existing connections with SMB v1 enabled, but swapping to v2 gives "A problem occured with network communication".

    Obviously the credentials etc are fine as they work in SMB v1.
    Creating new SMB v2 connections has the same issue.

    Connecting to W10 Pro 1709 build.

  • Anonymous commented  ·   ·  Flag as inappropriate

    We dumped ES for Solid Explorer and found we cannot connect to our win10 machine (surface pro).
    - As a check, we went back and tried a network scan using ES. It recognised win 10 but prompted to download an smb2 module.

    We don't get that option with Solid Explorer. Can you tell me if the beta solves this?


  • Anonymous commented  ·   ·  Flag as inappropriate

    The main reason I got SE was for this exact feature but I'm not enabling 1.0 on my OS. This update is welcome.

  • Martouf commented  ·   ·  Flag as inappropriate

    Cannot connect to Windows 10 system without at least SMB2. Must update ASAP!

  • louiscar commented  ·   ·  Flag as inappropriate

    So I have to say I got an answer from KG finally who says SMB 2 is being developed so here's hoping that SE is still alive and kicking

  • Gleb Samsonenko commented  ·   ·  Flag as inappropriate

    Already a half of the year this issue exists and still not fixed.

    Just forget about this app and use X-plore - SMB 2.0 works fine.

  • Peralta commented  ·   ·  Flag as inappropriate

    Yes! I'm facing this issue and it's really bothering me. For now I'm testing FX and it works because the app UPDATED the protocol, in fact they even show us in the config allowing us to choose between v1.0 and 2.0. What are you guys waiting for?

  • louiscar commented  ·   ·  Flag as inappropriate

    Yes very true however, for either of those reasons I'd expect him to inform the community, (particularly those that paid him), that he is no longer able to continue with the project.
    Of course he may be in ill and I hope that isn't the case however, Neatbytes is a company and so I'd think it fairly likely that someone elze would be able to convey the information that the project cannot continue.

← Previous 1 3

Feedback and Knowledge Base