Windows 10: 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

:)

 

SMB writes to remote computer freezes or dropps to 5kbs after creator update

After installing Windows [Version 10.0.15063] my access to NAS (RaspberryPI with USB disks connected) is nearly impossible.

Coping even few megabytes to the NAS takes a long time (minutes) and often does not finish - no errors on the Samba end , just connection from Windows goes dead. Speed seems to be around 5KB/s.

Same network and same NAS with my laptop :
Windows [Version 10.0.14393] and all is working fine - 20+ MB/s - which is what I can expect from this setup and is enough for documents and source code backups.

Reading from the NAS Samba share is fast.

Reading from the laptops' share is fast.

Writing to laptops' share is 5KB/s slow as well. Laptop is sharing folder using the normal Windows SMB. All Microsoft.

Writing to NAS share , SAMBA , is slow.

Looks like any writes I do from the Creator Update computer are slow. Very Slow.

Has anybody got similar problem or solutions to a very slow , unreliable connection to SMB/Samba after the creators update?

 

Pin to Quick Access on a Mapped Network Drive

It seems to be a problem with the samba protocol, the problem is only on a NAS running linux. A large majority of NAS are using samba protocol for file sharing, that's a big problem...

 

I think you need to accept the new certificate that is all. Like if you update a VM then RDC will fail as certitficate has changed after update of Windows version.

For SAMBA I never had a problem - I know you always do with every upgrade - but since about Windows 8 I use this and never change it Code: # # /etc/fstab: static file system information # # <file system> <dir> <type> <options> <dump> <pass> UUID=b023985e-c449-4301-ae92-582e6d3c39b3 / btrfs defaults,compress 0 0 //192.168.1.100/Downloads /mnt/MacBook cifs credentials=/root/secret.txt,iocharset=utf8,uid=1000,gid=1000,file_mode=0777,dir_mode=0777,nounix,nofail,x-systemd.device-timeout=1 0 0[/quote] with the "/root/secret.txt" being in plain text: Code: username=Hali domain=TP5 password=xxx{whatever}xxx[/quote]

 

I got the same problem with my Buffalo NAS in W10 1607 and SMB 1.0 disabled. Enabling did the job here.
Can it be that in W10 pro 1709 build 16299.64 SMB 1.0 CIFS File sharing Support is disabled.
https://www.theregister.co.uk/2017/0...xploited_smb1/
Can it be that your Samba needs SMB 1.0.
Try an Firmware update of your NAS or try to enable SMB 1.0 again in W10 1709.

 

There was also a security worry about using SMB 2 in 1709 and it was disabled by default. Perhaps that was it.

Guest access smb2 disabled by default in windows 10

I would say though that connecting using CIFS it has NEVER been a problem for me connecting from Linux to Windows. Jimbo seems to get a problem every upgrade so perhaps his security requirements are more extreme than mine.

I'm pretty lax - I even store my password in plain text (although root only access).

 

I have had strange issues accessing Samba shares on C drive from android that worked fin before 16299. I can access share on non OS drives without any issues. Interestingly, I can access public folders on c drive ok but no others. See this post

Cannot access C drive from android devices since upgraded to 16299 - Windows 10 Forums

Pretty sure there is a bug somewhere. Can you access non OS drives?

 

Now you mention it I've not tried. I only share Downloads from Windows which I have on C. I'll try sharing another partition or drive and see.

 

http://borncity.com/win/2017/11/26/s...hes-for-samba/

 

Try this
Run gpedit.msc
Computer Configuration>Administrative Templates>Network>Lanman Workstation
Enable insecure guest logon = enabled
The 1709 update has introduced a policy on Pro and higher version to disable the guest account by default