I too temporarily enabled SMBv1 and connected. I also tried other file explorers, and they all connected through SMBv2, but by using the SMB prefix.

My SMBv2 share can now be accessed by adding a new connection in the following format:

[local username]@SMB://[IPv4 Address] OR [account email]@SMB://[IPv4 Address]

I wonder is the DEVs abandon the apps project or what?
The most updates version is making quite number of error and FTP/SMb connection was having issues..

I was able to establish a connection from my Android phone to my Windows 10 netbook after enabling SMB 1 under "Turn Windows features on off." This of course creates a security issue. I had no luck at all with the Asus or ES file managers, but I did not spend a lot of time trying them. I submitted a bug report with logs to Neatbytes about the SMB 2 issue. So far I have received no response other than useless FAQ excerpts.

just doesnt play nice with mac

ASUS file manager worked perfectly, first attempt.

App abandoned by the developer, it would seem.

Same here. Really disappointed I paid for this.

Have any of you tried disabling the Master Password setting? It worked for me. And I put it again and iis still working. Seems like an update broke the Master Password, but it can be easily fixed by removing it and setting it up again. At least it did for me... Hope it helps :)

Hello, with the last update LAN/SMB connection is also broken for me. I don't find the shared folders of my computers nor add new ones.

However, I can do it with other file managers. And I have not changed anything in my smb.conf file.

Please, could you take a look to this issue? Thank you very much.

I have also run into the same issue trying to access network shares on my Mac. smb v2 doesn't let get past the last screen. smb v1 adds it to my list of storage but kicks me out if I try to access it.

I'm also seeing this. SMBv2 can't complete the setup process. v1 can, but then fails to connect after trying for ~10 seconds.

Yeah still happening for me too. It was working when the 2.0 was first released then maybe an update or something messed it up.

I just paid for the full version of Solid Explorer and I have the same problem.

facing the same

I've been having issues with SMB2 lately as well. Hopefully this gets fixed soon.

Ok

I have the same problem described. I've been trying to troubleshoot this problem for 3 days with 3 different computers and smb2 doesn't work no matter how I configure my network. I even turned on smb1 to see if that worked, it did. So I installed FX explorer from the play store and guess what it works with the smb2 protocol! So it is definitely Solid Explorer causing the problem. Sad I really like this app but right now it is unusable.
What for a fix.

Thought the above error occured because of SMB2 not being supported but now that we got 2.3.7 with SMB2 support it still occurs. Could we get a fix pleeease?

Is this fixed? Please i think its an important problem... could somebody give us some fix?

I'm experiencing same issue here :(. I have paid version and tested that ES explorer connects to share just fine. Please help!