As Hansmiller mentioned below, adding SMB// before the hostname/address works for me (eg. SMB//192.168.1.1 or SMB//SERVERNAME)

I've a tab s2 android and tried for hours to connect to my w10 machine with all updates installed. Gave up. Two days later it just works. FM.

I managed to find a solution to this.
All you need to do is to set the network profile as "Private" and then it works from solid explorer without issues.

It works for me after maybe 12 hours of trial and error over a 3-day period.

Remote host name: Enter your IP address as is. (do ipconfig and find IPv4 Address)
Port Number: 445 (I only knew this from one of the other websites. I figured it should have been the listening port for my IP, but nope)
Path: Blank
Display Name: Computer Name (shown as name when doing nslookup on your IP address)
Username and password authentication selected
Username as shown in the path in CMD after the /
Password was tricky, because it's not my Windows password which uses a 4-digit pin. It also is not my gmail address associated with the account. It was a third password that I often use elsewhere; I may have gotten lucky on this try. One thing to note is that I did use this password to create my LAN (different from my wifi password, so maybe that's what it used???)
SMB2 selected

Hi I’m new to this what it is I’ve got a android box and 4K FireStick I’m trying to transfer files between the two devices I’ve got solid explorer on both devices I’ve noticed Dropbox and mediafire work but google drive does not want to no I’ve tried FTP and LAN / SMB but I’m not really sure on how to set it up I know you have to put your IP address in but that’s about it could someone explain how to transfer files from my android box to my Firestick I was using es file explorer but nothing works on it cloud doesn’t work comes up with a error message on screen

I also had a network communication error result when trying to connect to a Seagate-419D4A NAS drive when using the default SMB2 setting.
I was able to connect using SMB1 (see option under Advanced in setup sequence).

Thanks for the help.

For me it works. You just need to create new user in Windows 10 and use it via Solid Explorer. It's Windows 10 which fucked Guest users via SMB2.

I don't know how exactly it is in English, but you need to right click on start menu > computer management >users and workgroups > users > right click anywhere in right panel > new user > edit username and password as you like and also check user can't change password and password never expire.

In Solid Explorer login via this username and password. Voila.

I'm getting the same issue on the latest version of Solid Explorer - Connecting to a Synology DS218J over SMB 2.

This issue does not occur using other file managers (FX, X-Plorer and ES File Explorer Pro)

Are there any plans to get this issue fixed? - It's a shame, as in terms of the interface and functionality this has the potential to be the best file manager for Android now that ES has gone.

Many thanks

UPDATE!

The previous message can be amended with this...after writing it, I tried the SMBv1 and that worked straight away....I do have an old version of windows and I guess what is new is that Solid now supports a later version by *default* and can't infer the OS (to select a desired protocol) that's understandable but any coder would write a simple bit of code to allow all the versions to be tried IF the default version fails.

Get it done guys.

Just installed it on my new phone and it is failing to connect to my fileshares that the previous version worked fine on. After i finally found how to edit the autoscanned setting adding "SMB//" before the server name DOES NOT WORK..Why can't they just leave well enough alone? I paid for this app precisely because it allowed remote connections to my file shares now my money is wasted??Just installed it on my new phone and it is failing to connect to my fileshares that the previous version worked fine on. After i finally found how to edit the autoscanned setting adding "SMB//" before the server name DOES NOT WORK..Why can't they just leave well enough alone? I paid for this app precisely because it allowed remote connections to my file shares now my money is wasted??Just installed it on my new phone and it is failing to connect to my fileshares that the previous version worked fine on. After i finally found how to edit the autoscanned setting adding "SMB//" before the server name DOES NOT WORK..Why can't they just leave well enough alone? I paid for this app precisely because it allowed remote connections to my file shares now my money is wasted??

If someone is still having trouble connecting, simply enter the

SMB//

command before the address of the server you want to connect to.

Having the same problem. My Windows 10 PC has SMBv1 enabled. I can access it over wi-fi with my windows 7 laptop. I used to be able to access the W10 PC with my Android phone using Solid Explorer, but recently that feature has stopped. Switching back and forth between SMB1 and SMB2 does not fix the problem. I suspect something got broken with a recent Solid Explorer update.

I have the same problem but interestingly this problem seems to be more complicateted. I have two NAS in my network. My phone can connect to both with SMB v2 but my tablet can only connect to one of them with SMB v2 for the other one I have to use SMB v1. A different file explorer on my tablet connects to both with SMB v2. So my guess the problem is within the solid explorer!

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 :)