Unable to Access Windows shares from anything else.

[rambo919]

Once again taking the plunge into Linux partly due to taking a break from gaming for a while..... I noticed something odd while trying to get filesharing to work, I thought it was Linux to blame but after thinking to test Android it turns out it's windows.

1-Both Android and Linux clients can access Android and Linux shares but neither can access Windows shares. They complain the connection was reset. In Linux I can mount the share's directly but the specific problem seems to be getting the share-list.

2-Windows clients can access shares from all three OS's.

3-Android could not too long ago happily access Windows shares.

wtf? what did M$ change in recent updates? Is there a setting I don't know about creating this walled networking garden?

As an aside ignoring it's annoyances once you figure out Linux filesharing it's much easier than Windows that ties everything to the filesystem instead of folder structure.... it was a pain in the ass figuring out anon sharing though.

 

[Hamish McPanji]

Firewall
Permissions

In that order

 

[rambo919]

Firewall
Permissions

In that order

There are two windows PC's connected atm, both share the same problem. Password sharing is turned off.

Only one has an extra firewall. Different AV's.

This does not explain why anon/guest access works fine with other windows devices but not with either Android or Linux devices..... but just last month it worked perfectly fine for Android clients. Even the one PC which has always refused all connections from Android clients worked at the time.

 

[rambo919]

OK odd thing, fired up my laptop which had some old shares. Same problem, then I removed all shares and added a new one.... now it works for only that laptop. Will try the same with other PC's tomorrow.

 

[rustypup]

Prior versions of SMB are being intentionally blocked.... because they're security garbage and have been for a long time.

...although SMB v3 is not without similar issues

 

[rambo919]

Prior versions of SMB are being intentionally blocked.... because they're security garbage and have been for a long time.

...although SMB v3 is not without similar issues

That's why I use min protocol instead of the previously recommended max protocol in smb.conf. Even tried going directly to SMB3 when initially setting up but that did not work but it's worth a shot trying again at some point.

Before I did this I predictably (because of debian's half-assed implementation that filters down to all derivatives) could not browse the workgroup from my Linux PC.

I did discover tonight though in my irritated testing that there might be a file manager problem in my default android software, cx explorer seems to have no problems whatsoever in comparison.

 

[access]

there was an update pretty recently that messed with anonymous connections to shares with windows 10.

there was a gpedit or a regedit fix for it, i think the regedit did the trick

 

[Totempole]

There are two windows PC's connected atm, both share the same problem. Password sharing is turned off.

This would have been my suggestion. If you've ruled that out I've got nothing.

Only suggestion I can make is that if your devices are assigned IP addresses by a router, to reboot that router everytime you change a setting. Trust me, this could save you hours of troubleshooting.

 

[rambo919]

there was an update pretty recently that messed with anonymous connections to shares with windows 10.

there was a gpedit or a regedit fix for it, i think the regedit did the trick

Will look out for that this weekend when I get to it again thanks

 

[rambo919]

This would have been my suggestion. If you've ruled that out I've got nothing.

Only suggestion I can make is that if your devices are assigned IP addresses by a router, to reboot that router everytime you change a setting. Trust me, this could save you hours of troubleshooting.

Fortunately for me I put the important one's on static IP's anyway to save myself headaches with the less tech literate household members..... probably why share mounting actually works if you know the share names.

 

[access]

Will look out for that this weekend when I get to it again thanks

i think this was it:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters] "AllowInsecureGuestAuth"=dword:1

the gpedit setting made no difference, this above did the trick.