Windows 10 can't see TS-559 Pro II after upgrading firmware to 20221028

[nassimo]

Before upgrading firmware windows 10 could see NAS via SMBv1.
The firmware upgrade disabled SMBv1 on NAS but, even if I disabled SMBv1 in W10, i cannot see NAS in windows explorer.

Any suggestion?

[dolbyman]

Whats the SMB version status of your NAS ?

Login via SSH and do

Code: Select all

 smb2status

[Toxic17]

just out of curiosity, why are you using SMBv1?

btw: Microsoft has marked SMB1 as deprecated in June 2013 Windows Server 2016 and Windows 10 version 1709 do not have SMB1 installed by default.

[Moogle Stiltzkin]

on my ts-509 pro it can't be seen either. but this was before a recent update where malware remover or was it the latest firmware now removed smb1 from the QTS (whereas you had to do it manually before in ssh since it was not in the UI).

So i haven't checked recently. but a while back i could not see my 509 pro too, so i'm wondering if it was because smb1 was the active setting but windows 11 now defaults to block smb1. so i suspect maybe that was why? also seems the default for win10 is also not to enable smb1
https://learn.microsoft.com/en-us/windo ... in-windows

while at it you can also check your windows client, to make sure it's disabled if it isn't already
https://learn.microsoft.com/en-us/windo ... abs=server


Anyway you shouldn't be using smb1. use smb2 or better. I have the 659 pro II model as well, this one can be set to smb2+ in QTS.

Then check qfinder if it detects.

if not try reboot. but like others pointed out, check your smb status first on the qnap.


If still confused why you shouldn't be using smb1, read this
https://blog.barracuda.com/2022/05/11/a ... ernalblue/

[nassimo]

Whats the SMB version status of your NAS ?

Login via SSH and do

Code: Select all

 smb2status

Hi, thankyou for the hint.
The response to smb2status command was

smbd (samba daemon) Version 4.0.25
smbd (samba daemon) is running
max protocol SMB2.1 is enabled


--------------------------------------------
I also checked W10 to see in SMBv2 support was enabled

PS C:\Windows\system32> Get-SmbServerConfiguration | Select EnableSMB2Protocol

EnableSMB2Protocol
------------------
True


----------------------------------------------

so why the NAS is not discovered by W10 in windows explorer?

[nassimo]

just out of curiosity, why are you using SMBv1?

btw: Microsoft has marked SMB1 as deprecated in June 2013 Windows Server 2016 and Windows 10 version 1709 do not have SMB1 installed by default.

Hi, thankyou for your question.
TS-559 Pro II only supported SMBv1 till the recent firmware upgrade.
So I had to force W10 to use SMBv1 in order to see the NAS under windows explorer
I know the SMBv1 is deprecated but
- the NAS ins't exposed on Internet. It is only accessed in LAN.
- this was the only way to see the NAS under windows explorer

20221028 firmware upgrade of QTS 4.2.6 removed SMBv1 support from NAS and replaced with SMBv2 support
I welcomed this and upgraded the firmware, but now I cannot see the NAS in W10 windows explorer even if I removed SMBv1 support from W10

[Toxic17]

are you able to access the share in windows explorer by typing in the UNC path?

Code: Select all

\\ipadress\sharename

if that works, then maybe your NAS has not enabled WS-Discovery. (this has nothing to do with Samba versions)

quote:

Code: Select all

Enable WS-Discovery to help SMB clients discover the NAS	Select to enable Web Services Dynamic Discovery (WS-Discovery). WS-Discovery makes the NAS visible in File Explorer on Windows 10 computers.

Screenshot 2022-12-22 123523.png

[FSC830]

...
20221028 firmware upgrade of QTS 4.2.6 removed SMBv1 support from NAS and replaced with SMBv2 support
I welcomed this and upgraded the firmware, but now I cannot see the NAS in W10 windows explorer even if I removed SMBv1 support from W10

Its not removed, its just disabled.
If you run smb2disable at CLI SMBv1 will be available again!

Anyhow, Windows often has problems with discovering devices, this is to the mDNS, which seems to be not very reliable.
I am using several identical NAS (4 x TS-669), identical Firmware and identical settings. Sometimes all NAS can be seen in Windows, sometimes not.

But all can be accessed all the time.

So I dont care for that.

Regards

[nassimo]

are you able to access the share in windows explorer by typing in the UNC path?

Code: Select all

\\ipadress\sharename

if that works, then maybe your NAS has not enabled WS-Discovery. (this has nothing to do with Samba versions)

Yes, it works. So the issue may be related to WS-Discovery.
Unfortunately my eleven years old NAS runs QTS 4.2.6 whose GUI lacks of commands regarding WS-Discovery, as far I can see.
Do you know if there is a command via CLI that enable WS-Discovery?

[Toxic17]

I think WS-Discovery was introduced in QTS 4.3.4 so its not a feature in 4.2.6 from the WTS manual i looked at.

best then you just MAP your NAS shares to drive letters (permanently) I guess. That way you will see your NAS at least if you really need view of the nas in windows 10. or you just add the shares in the quick access menu. personally I would still suggest using SMBv3 rather than v1 as 1 is insecure and more vulnerable to malware/ransomware attacks.

[Toxic17]

@nassimo have you tried enabling Local master Browser too?

[Moogle Stiltzkin]

I think WS-Discovery was introduced in QTS 4.3.4 so its not a feature in 4.2.6 from the WTS manual i looked at.

best then you just MAP your NAS shares to drive letters (permanently) I guess. That way you will see your NAS at least if you really need view of the nas in windows 10. or you just add the shares in the quick access menu. personally I would still suggest using SMBv3 rather than v1 as 1 is insecure and more vulnerable to malware/ransomware attacks.

i also have this issue for a ts-509 pro. it's not detectable, but because i added the nas ip manually in qfinder, i can still access it even if it cannot detect. so for this old model, that's just how it is. the newer models don't have this issue