Samba access from Android device stopped working

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.

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

bro67 said:

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

And here we go again...

bro67 said:

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

bro67 said:

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.

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

bro67 said:

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.

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.