Can access just the public folder

Hello all and thanks in advance for your support
I just reinstalled windows 10 with latest updates and I am using a QNAP NAS with QTS 4.5.3 with IP 192.168.0.4 (this is a fantasy IP of course)
typing \\192.168.0.4 in windows explorer results in showing JUST the Pblic folder and I am not asked for the NAS credentials
The NAS configuration is tha same as before (i.e. whene everything was working and I can still access the nas folders from other PCs)
When I access the NAS folders windows strangely does not ask for any user and password and I cannot remember how to set this manually ...

the server name is NAS-ZP. I was never able to access it by \\NAS-ZP... I am using explicit IP, still I would like to use the NET BIOS name. Any hints?

Please help

- - - Updated - - -

This means that the \\server\share is found on a Unix system (QNAP with QTS OS and the clients are Windows10. To be precise, client A can access all the \\server\ subfolder while client B can just access \\server\Public. This demonstrates tht this is related to client B network / firewall or whatever configurations (not solved yet)
- I have enable network discovery: should not this be enough??

What protocol does the nas use chances its been disabled

What smb version is windows using

I tried the command but it does not return anything, This should me that no SMB protocol is active right?

In the meantime I tried 'Turn Windows Feature on and off 'on the w10 PC-A (the one which can communicate with the NAS) and PC-A and make the same. PC-A. For Both, SMB/CIFS1.0 file sharing support is unchecked now. As a result I can just see JUST the Public folder on PC-B (to me this means that SMB is working and there are access problems somewhere)

I cannot understand why the command you suggest returns void on PC-B ...
On PC-A I get

ServerName ShareName UserName Credential Dialect NumOpens
---------- --------- -------- ---------- ------- --------
192.168.1.34 multimedia PC-******\***** PC-******\***** 3.1.1 7

so the next step is to enable SMB 3.1.1 on PC-B

https://docs.microsoft.com/en-us/win...le-smbv1-v2-v3

Thanks much

- - - Updated - - -

I also did this experiment on PC-A, where I mapped to a network drive z: the \\<nas-ip>\multimedia successfully
I tried to map another folder on disk x: and this did not work (i.e. it is attempting to connect since minutes ...)

- - - Updated - - -

I also tried to map the network drive using QNAP Finder Pro Two alternative methods to map the shared folder as the network drive in Windows | QNAP but still does not work. The list of mappable folder is empty. Differently from PC-A where I cann see the dirs in the NAS suited to be mapped

- - - Updated - - -


The smbd.log report from the PC-B

If the command returns nothing, it doesn't mean that no SMB protocol is active. It just means that the SMB server on PC-B (the device you ran the command on) has not negotiated a connection to a SMB client with any available SMB protocol.

On PC-B, run the following in an elevated PowerShell console to get PC-B's SMB configuration:

Code:

get-smbserverconfiguration

You're looking for the returns from EnableSMB1Protocol and EnableSMB2Protocol to see what's enabled. (I think this is easier than using Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol.)

Next (still from PC-B) enter:

Code:

net view \\NAS-ZP

This should show you the published shares on your NAS.

If nothing is returned, use the IP address of the NAS instead:

Code:

net view \\192.168.0.4

Compare this with the returns from PC-A (which your previous test shows is using SMB3.1, which is enabled by default) when you run the same commands.


I have no experience of a QNAS. I assume it offers a web interface to view configuration details? Does it show a connection to PC-A by either name or IP address?

Hope this helps...