Windows 10: NAS Samba SMB2 not accessible on Windows 10

Hello, for some time now I have not been able to access the files on my NAS from my Windows 10 PC.

This is a D-Link DNS-325 Sharecenter type NAS on which I use the opensource Alt-F firmware, SMB2 compatible.
Windows version: Windows 10 Pro x64, Version 1909 18363.1256

When I enter the address directly in the File Explorer eg \\192.168.0.15\ I have the error 0x80070043,

if I enter the volume address eg \\192.168.0.15\ MyVolume I have the error 0x80004005.


At one point it doesn't work anymore because the D-Link firmware was only compatible with SMB1 which has security vulnerabilities and which is no longer enabled under Win10.

So I updated the NAS firmware to support SMB2 using AltF firmware. It worked for several months but it doesn't work again despite reactivating SMB1 in my system. Something has changed on my system but I don't know what.


Services.msc: the "NetBios Assistance on TCP / IP" service is successfully started and configured as a "Local Service" connexion

Windows features:
SMB Direct enabled
SMB 1.0 / CIFS file sharing support: all enabled
Firewall Defender: I don't know if it's good but in any case I can see my Freebox Server well so I think it's correct.

Powershell:

Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol => State: Enabled

Get-SmbServerConfiguration Select EnableSMB2Protocol => True


Ping response: I can ping the NAS from the PC without any problem from the Win10 PC

In addition, I can access the files of the NAS without any problem from my macbook.
I have also tried the following magic commands without success:

sfc / scannow

DISM / Online / Cleanup-Image / RestoreHealth

Thanks in advance for all the help. I really don't know what to do now maybe except changint my NAS.

:)

 

Windows 10 and DNS 320 NAS samba access issues

Hello everyone,

Since january 2017 approx. , i can't use my Dlink DNS 320 Nas in my desktop computer explorer (using either \\nas.ip or \\nasname). Before this date the NAS was perfectly working on the same computer.

The NAS is fully working because on a windows 7 laptop, on IOS phone, on Android phone i can connect with Samba protocol with no issues.

On the win 10, i can ping both the ip and the nas name, i can also access it by ftp on web admin interface.

I'm pretty sure a windows update broke it but i really don't know how to make it work again.

 

Samba v 4.8.x and connectivity (SMB1 / NAS etc)

Hi folks
I know people use NAS systems on this board which often use Linux type distros. Same goes for VM's.

Samba 4.8.x now throws error if you specify min protocol = SMB1 in your SMB.CONF file which will hose you up if you need connectivity to NAS via Windows / Smart TV's etc. especially on older gear which only works with SMB1.

Don't panic

Change SMB1 to NT1 in the samba.conf file on the NAS server.

for example : in the [global] section found generally in \etc\samba directory.

[global]
max protocol = NT1
; max protocol = SMB3
# can set it to SMB2 if you want experimental SMB2 support.
#
workgroup = WORKGROUP
server string = Samba Server Version %v

; max protocol = SMB2
netbios name = hestur

log file = /var/log/samba/log.%m
max log size = 50
security = user
passdb backend = tdbsam

.....etc

then it all works again fine -- example -- on the NAS box - sees the Windows machine OK.





Windows access also no problem either.

If running samba v 4.7.x then no probs - no change.

Cheers
jimbo

 

XP and NAS (Samba) access

Thanks again for the quick response. I checked in Win10 & it seems SMB1 is turned on.



What can I try now?