Windows 10: Samba access from Android device stopped working

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.

 

what you say it's quite obvious and also not the solution to the problem, please read what we wrote before answering back again about this please

 

I've got the same problem, both from ES in Android and Windows. I'm already using a local account, so now what?

Edit: I've fixed the problem

Solved problem with shared drive

 

Again that is the solution to fixing 10, so that you can see the Windows shares in File Explorer.

 

And here we go again...

 

Here is wher you go goodbye Alphos. You and the other need to move on, since the problem has been stated why only the OP has problems with the ap and no one else has.

 

actually as i said i have the same problems and if u read around there are others with the same problem even on microsoft forums there are people with this problem so if you cant understand that please keep silent, you already explained what u think is ur solution, thanks

 

I know what the issue is. I have stated what the user problem is and the fix. The Microsoft forums do not mean anything, because they have nothing to do with this forum. If you want to use them, that is fine. The complaints on there and solutions are not fixing a User problem.

No one else has had any problems using the ES File Explorer app, or even using the fix in the link I posted, if you cannot connect between Windows Machines or other devices and Windows 10.

This issue goes as far back as Windows 10. You are new here, I have over 35 years dealing with Networks and computers. You do not have the room to tell people to stay silent, so you may want to check yourself and learn how to listen when someone states that the problem has been fixed.

 

No one else has?

So why are here a lot of people with the same problem and NO ONE found the solution yet, just waiting for a new windows update to fix it?

And they seem to know a lot more than you about networking...

Cannot connect to CIFS / SMB / Samba Network Shares Shared Folders in Windows 10 after update 1511/10586

or here?

Cant access my share samba/lan folders after update KB3140768,Windows 10 Version 1511

 

Hi there

I've stated a solution that seems to work most of the time -

Again for local (home) type LANs - not Domains etc.

W10 doesn't need NETBIOS so simply in your GLOBAL section of the samba CONF file add the following line

max protocol = SMB3

Remove any reference to NETBIOS such as NETBIOSNAME
Don't use WINS parameter
and optionally the following two lines (also to GLOBAL section) - usually only needed if you get message Timeout on server appearing when trying to connect. :

wins support = no
name resolve order = bcast host lmhosts wins

Cheers

jimbo

 

I'm so sorry sir, but i think that a conversation among professional people have no space for ad-hominems, the truth of whatever we seek lays in the perceivable world and in what we can discover from reality not in the quality or knowledge of a person, his behavior, morality or lack of it, also, unless you are God, and leaving the whole religious debate aside, I doubt you can be 100% certain about something, you could have a thousand years of experience in the field, yet you wont be the owner of the truth, unless your truth is dogma, also as it has been said by the OP, your "solution" doesn't fix his problem, nor mine, hence by definition is NOT a "solution", you can't decree that whatever you say solves a problem, cos you arent God, nor an Emperor, that could impose his will onto us.

In the end, the only person who is more entitled to say that a problem is solved or not, is the person who reported the problem, cos he is the one who have access to the equipment that present the problem, unless you live with him or have access to his assets, you cant theoretically say that whatever you consider a "solution" is a real one.

Hope things are clear, it's not my intention to start a flame war, cos that's not the point of the forum.

 

Hi there

The best we can do (or most of us) is to find a solution that works for us and would hopefully apply to the OP's situation.
A real problem though - especially with newer members to the Forums is that they often don't provide any feedback - so it's hard to tell if the proposed solution works or not.

Most people here try and help other users - but users with problems can also help themselves more by providing feedback such as - solution doesn't work, does work or already tried that and no good.

Cheers
jimbo

 

I have just encountered the same problem. My Es File Explorer app finds the host and in the past i have used it to connect to my Windows 10 shared folders via smb. I haven't used it for a month or so so i just recently found out that there is a problem. Here are some things worth mentioning:

1. The app automatically finds the host, which uses static IP.
2. I use my Windows 10 account credentials (mail + password), and it worked in the past.
3. When i try to use other app (I tried AndSMB) it works fine. This may be pointing that the problem is with Es File Explorer and Windows or samba.
4. When i disable password protection, it works fine (for the files that i have enabled Guest access). When there is password protection, even Guest access doesn't work.
5. When i try to edit the server in Es File Explorer, when i click ok, it shows toast message: Error, cannot find server
6. I have disabled NetBIOS
7. I have applied the fix that enables connection to unsecured networks.

 

None of the posted solutions have worked so far.

However, I have news:

The AndSMB app can still connect to my Windows 10 machine! Unfortunately the app sucks.

But ES File Explorer can't, and neither can the File Manager from Asus. So, Microsoft probably did change something, which screwed the samba implementations that ES File Explorer and File Manager uses, but the AndSMB solution seems more robust (and they mention cifs too). Let's hope ES File Explorer updates soon, because they're not responding to e-mail. *Sad