Windows 10: Windows latest update causes SAMBA (NAS) change ????

Hi there

Haven't changed any settings in Windows 10 or in SAMBA files but after latest W10 update I get the NAS trying to act as a local master browser ????? -- I haven't got anything in SAMBA to specify this -- samba hasn't changed so it can only be windows / networking.





One doesn't want this type of behaviour on a LAN otherwise you'll get a continuous "election" between Windows and SAMBA -- I just need basic simple file sharing like it always used to work.

Any ideas

(I know it's windows because if I restore an older version of Windows (pre the updates) and re-boot the nas I get connections fine and the NAS server simply has a message "Ready to serve connections"

Cheers
jimbo

:)

 

NAS / SAMBA 4.8.x updates and connectivity


Hi folks
I posted in the VM section but as a lot run NAS servers / Linux OS's I'll repeat the info as some don't use the VM section.

You might find that after an update to SAMBA 4.8.X (4.7.x is ok and needs no change) that you lose connectivity, can't see your network from the NAS side or even get an error when re-starting SAMBA especially when using SMB1 for connectivity.

The max protocol = SMB1 in the samba/conf file has now been deprecated -- you have to change the SMB1 to NT1 and then it all works again.

I've got the example shown in my post : Samba v 4.8.x and connectivity (SMB1 / NAS etc) Solved - Windows 10 Forums

Cheers
jimbo

 

Samba at Risk from Wormable Bug Similar to WannaCry: Present on Many NAS boxes

The big concern here is "unsupported" devices, as there are most like hundreds of thousands, if not millions of devices out there that run samba, but have fallen off the supported devices category from their original manufacturer. It means that they no longer receive software updates, but it doesn't mean the devices are useless. No company is going to go and release patches for devices that dropped off their supported devices list 4-5 years ago. These devices could be things like routers, web cameras and what not, in addition to just NAS appliances, as samba is used on anything that has remote accessible storage, so it's a rather scary thing, as so many of these devices have lax security. What's worse, many of these devices can't have the software updated, as it's an integral part of the firmware and changing samba version can break a lot of things.

 

W10 pro update 1709 shares cannot be accesed FROM NAS Server (Samba)


Hi folks

it's definitely a windows update problem with version 1709.

FROM Nas server -- cannot access windows shares vua samba anymore -- says timeout on xxxxx - and this comes up immediately !!!

other windows machines have no problem.

Accessing the server FROM windows is OK but I need to access windows FROM the server as well (auto backups from server).

Any suggestions folks.

I actually didn't want this last update but some how windows set to auto update.

version is W10 pro 1709 build 16299.64

SAMBA on server running just fine -- TV's, phones etc can all access OK. SAMBA V4 (latest) being used on server.

Note Windows TO server works, Windows FROM server fails. I have 2 NAS servers and same problem -old Windows works but not the latest.

Tested also disabling BOTH sets of firewalls and Windows has all the allow remote access stuff enabled.

Is there some type of local security policy default enabled that wasn't there before. ??

Cheers
jimbo