I had the same problem after updating Windows 10. This is what I did to fix it:
1. Select (press and hold) the LAN connection of the Win10 PC (under Network tab in ES Explorer. If you deleted it, scan again to get the connection).
2. Select "Edit Server" option.
3. Enter your Computer name in the "Domain" textbox in FULL CAPITALS!!. Don't change any other thing.
4. OK, and enjoy the SMB re-connection in ES File Explorer!!
I joined this forum just to thank waddles for this solution. I had removed the '@gmail.com' bit from the username, but that did not work. I essentially gave up on SMB from my Android device since this issue cropped up in May. I had just removed the password protection, but I didn't really like that option. The 'whoami' is what did it. In 'devicename\XXXXX', it is the XXXXX as the username that allows you to access shared folders through ES File Explorer.
I read this entire thread, and I must say, the reading comprehension here is astonishingly poor. The OP and several people after him laid out the exact same problem, and they were told time after time to login with the windows credentials, and that it was idiot-proof. It simply wasn't working. I hope I don't have to return here in the future, cause that's a very poor way of responding to someone's question.
waddles - thanks again, man. Brilliant idea!
Control Panel\All Control Panel Items\Network and Sharing Centre\Advanced sharing settings
All Networks
Turn OFF password protected sharing
worked for me in similar circumstances with ES File Explorer
WOW, what a heated discussion this has become. IMHO, some the comments are "Very" unnecessary and are "Very" Narrow Minded and not exemplify of a so called "PRO" (especially when he/she is "WRONG").
That said, I have searched the web for the last week for a solution to this Android Phone sharing issue with ES File manager and, my preferred Android file manager Zenui Android File Manager. Despite other user claims that they have no problem, I did. I have a mixed bag of PC configurations (various versions of Win10 and some Win7, some Win7 upgraded to Win10) on a private local network. Even though I have my file/folder/drives that I want shared set and have Password Protected sharing turned off, I cannot access any Win10 configured PC with my Android File manager other than PUBLIC folders.
Good news is that I have stumbled onto what I feel is the solution for the present time. It adds one additional step to the normal steps we take to share our files on our networks. We need to add a security exception in file/drive/folder properties. I encourage everyone still struggling with this Windows 10 issue to take a look... It's Titled "Es File Explorer has no permissions". Be sure when making the settings suggest here to insure you check the inheritance block so all sub-folders are shared...
Link is - http://www.allpcstuff.com/es-file-ex...ions-solution/
After seeing waddles' suggestion about using the first 5 characters, I was able authenticate for one of my computers, but not all.
Waddles' suggestion gave me a very good lead into what user name should be used.
You can find the correct username by opening command prompt and typing echo %username%
If you're using the correct user name and are still having issues connecting, it's likely that you have a security permissions issue on the directory or your ip/server name is wrong. If you're connecting with an admin user, you don't have to explicitly share folders. You will have access to the administrative shares by only providing the server name/IP and not specifying a directory. If you do want to connect to a particular administrative share, you can provide servername/c$ where c is the drive letter.
in my case the problem was on the android side, because i could access the shared files from other computers.
here's how i fixed it:
1- in windows open properties of the folder you want to share, then sharing and advanced sharing
2- give a share name you can remember(also don't use spaces)
3- on android open up es file manager. left pane, network and then lan
4- scan can't find it so don't bother. add manually by "(computername)/(share name)". ip doesn't work. btw, even though you don't use a password you have to provide your username
Created an account just to thank you @waddles !!!
I had this issue from March, ever since I upgraded from galaxy S6 to S7. Initially, I thought it was the new phone that caused the issue. But then I tried my tablet (which always worked with ES File Explorer and LAN), and even that had stopped working. I gave up all hopes of ever being able to use smb to access my files, and switched over to AirStream, but alas! AirStream servers are down since a week, and I was back to square one.
And today I stumbled upon this topic. Read through 5 pages of typical forum drama, and empathized with the OP, feeling his pain and misery. And then on the 5th page, there's this post by waddles!
Thank you waddles!
-thankyouwaddles
I registered just to share my solution.
My problem actually similar but a little bit different to the original one.
I was using Windows 7 server + Ez File Explorer on multiple Android devices.
Then I updated to Windows 10, some of my folder stop sharing. After a couple tests, I found that all the shares I created with external HD stop working, but the ones that I shares through internal HD still works. (As I used local accounts).
After I found this thread, and go through every single reply, I found one of the reply suggested to use Solid Explorer. That does not work for me as well but it gives me an error (0xC0000205). So I googled the error code, and I found this post:
smb - Hudson Windows service slave launch causes SmbException - Stack Overflow
In there it talks about changing the IRPStackSize (https://support.microsoft.com/en-us/kb/285089)
So follow the link and add the new IRPStackSize DWORD in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
and set the value to 50 works for me. Hope this helps other people.
If all else fails try changing the registry value for the following file to "1"
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\SMB1
This worked for me on Windows 10 Version 1703 and ES File Explorer Pro.
Quote