Samba access from Android device stopped working

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.

dwisdom said:

@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.

bro67 said:

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

bro67 said:

arangaran see my post about the Samba shares not working with Windows 10. It has the fix in there. If you open up the ES app on your Android device, you should see a list of available devices at the bottom, that you tap on and then enter username and password. If not, enter the IP of the device and again username and password to access, since not all folders are not going to be accessible, unless you go into the Windows advanced share properties and change the Inheritance info.

Again the same? Thats useless, please stop spamming with really easy solutions that have nothing to do with our problem. The solution you are giving us is what we already did when we didn't have problems, now we CAN'T do that since windows updated.