Windows 10: Samba access from Android device stopped working

I can confirm that turning off password protection in the Windows 10 network sharing center does give me access, but only to certain folders, and not to any files, in for example the user desktop, and not to my external harddrive (which also worked just a few months ago).

I tried the power shell commands to enable and disable the various samba settings in Windows 10, but they did not have an immediate result.

 

Interesting observation, I missed that...Thanks

 

eeobet if you want help, do not complain, because your post will get buried in the deepest reaches of the sitr, never to be seen or heard of again.

Also posting in all Cap's will make you to be ignored and again your post will disappear into the nether regions.

The ES File Manager app is very easy to use. You find the computer in Network neighborhood, click on it and just add the username and password. There is nothing else that you have to do. Also Password protection does not need to be disabled.

Maybe try reading the instructions on it.

Also Window 10 has had an issue of the fact that Microsoft locked out Guest Access, which gives an error about protocols not found, which causes the app to not work.

So stop telling us that we are wrong and start listening. Jimbo has been doing this stuff just as long as I have. He added in on what I posted, even though I had to go in and correct some things.

At this point the answeting is over and you are now on your own to do as we stated in making the apo work.

 

I do not hook up my Nexus tablet to a computer, unless I am going in and deleting temp files that the OS cannot remove. It is the most idiot proof app that I have found and I love it.

 

I'm having exactly the same problem since I updated Windows with last update a few hours ago. Es File Explorer keeps asking me for my user and password. I'm pretty sure that last update broke something, but no idea what can be.

The problem seems to have something to do with that discussed here: Windows 10 1511 Network Browsing Issue - Page 6 - Windows 10 Forums

 

This is happening to me as well. I am running ES File Explorer on my Android (Blackberry Priv) and on my Nvidia Shield Tablet and both can't connect to my Windows 10 box. The funny thing is that I can connect to my 2nd Windows 10 box. The differences are, one has a Microsoft Account for a login, and the other has just a local account (this is the one which shares work)

I did Windows updates like you guys and that too is when this began.

I did notice that today there was an update to es File Explorer, however this did not fix the issue. So there is something within Windows 10. I will keep a look out incase someone can come up with the fix.

thanks

 

The Windows update which caused all the headache's is KB3140768

For now, I have uninstalled it from Windows 10 and rebooted. Now ES File Explorer can brown SMB shares again!

hopefully Microsoft will fix this update in the future.

Hope it works for you!

 

Solved: thanks @accordv6, your experience helped to shed light on the matter, the solution is to go to settings, accounts, you will then see the option to opt to log in with a local account ( instead of your outlook account) , choose this. It will require you to sign out and create an account profile (but now without an outlook.com suffix, more like we had in earlier windows releases) after this is done, you will use this as your default log in. After logging back in, with your new credentials, you will be able to access your shares as before, with your new credentials. Worked for me. Cheers

 

I don't see that like a solution, I don't want to create a different account than my outlook account. There should be another way.

 

@Alohos on the contrary I see it as a step in the right direction with regards to security, for instance i really don't use my outlook.com mail for any other thing outside of logging into my pc, if it were my gmail account for instance, I won't like my credentials being saved on different devices to connect to my shares, this could be sniffed by someone who will in turn have full access to all my personal mails.

 

I didn't want to create a local profile myself, so like I said, I just removed the single Windows update for now. I think that this is much safer than having to do anything with accounts etc. Hopefully Microsoft will fix this patch soon.

 

Mmmm, strange. From my S5 Lollipop phone I can access shares from all my comps and my Linux based NAS.

One PC is a standard 1511 586, fully updated, incl KBnnnn786 and two other up-to-date Insider comps.

All were on MS accounts.

 

See Windows 10: Unable to Connect to Samba Shares schkerke.com It will fix the restrictions that Microsoft implemented.

 

Unless I'm misunderstanding that article, it's about Windows 10's ability to connect to an unsecured share. Well, this thread is about Android's inability to connect to a secure Windows 10 share. I tried it anyway, and it did not work.

(Small rant: You seem to storm into threads with your friends, without properly reading what they are about and just drive-by post something, and then get upset and attempt to ridicule people when they point out that what you are talking about, and act arrogant about, is not actually what's going on in the thread. How about some quality over quantity?)

 

I wanted to say that i have the same problem as the OP, since the update from March 16th (i think) i'm unable to connect to my network shares from my windows 10 desktop computer using ES File Explorer and other software in android, nevertheless there's ONE app that works somehow and thats Solid Explorer, and about why it works is a mystery to me, also i can confirm that if u use a MS Live account as the main account under which u created the shares then the problem appears, if u switch to a private account everything works, which leads me to believe that it gotta do with some validation that it does against microsoft servers, i dont know if there are other places that are investigating this, or if there's even a way to contact microsoft to get this fixed, in some kind of support site, if anyone knows let me know please