QNAP NAS - Unable to access shared files & folders from Windows 10

[qnapdown]

Model : TVS-682
QTS Version : 5.2.4.3079
Windows OS = Windows 10

QNAP NAS is connected to a wireless router.
The PC from which I am trying to access the NAS is connected to the same wireless router.

I have created a folder from QTS and I am trying to access the shared files from Windows 10 file explorer.

Ping from command prompt is going well.
I can access the QTS via the ip address from a web browser.
FTP the files and download them using WinSCP without any issues.

But From Windows 10 PC, I cant see the files or the shared folers using a file exporer or using run command (\19x.x.xx.x) or by the NAS name itself. I only see an empty folder. Not sure why. Have tried restarting and checking the folder permissions and they all have correct access set up.

Also on Network Access, All network services/management services / applications are enabled for service binding (Enable service binding option checked).

Enable file services for Microsoft Networking (SMB) checked / selected on. On Advanced Options, highest and lowest SMB versions are set correctly.

Also when I try to connect via storage Plug & Connect, I can;t find any shared folders here either. But when I create a new folder, the folder gets created on the NAS, but on my PC/desktop it displays a error message that the network drive can’t be connected.

[dolbyman]

No need to censor internal IP’s … millions have the same

Have you tried to disable any firewalls on the qnap ?

[qnapdown]

LoL… Sorry about the masking. Have been doing that for years and years, habits dont die…

But with regards to Firewall, it was initially disabled and then I was playing around. Will check again to ensure that is all in place.

BRB

[qnapdown]

I am unable to enable firewall actually. Unable to switch on the button.

[dolbyman]

I meant disable or uninstall the firewall

[qnapdown]

I meant - Firewall is disabled and I am unable to “Enable” it. When I click it, it pops up with a box asking for confirmation to enabling firewall. When I click ok, it does nothing.

Trying to uninstall firewall.

[dolbyman]

On newer firmware’s the SMB service is actually it’s own program, is that running ok ? (Open it and see what it says)

[qnapdown]

Here we go - Restarting the NAS after firewall uninstall… But below are the screenshots for the service.

NOt sure what this means - 2. The latest update information will be available in the App Center. After successfully updating the SMB Service in the App Center, you also need to complete the update process through the SMB Service web interface.

[qnapdown]

After uninstalling the firewall and restarting the QNAP device, I am still having the same issue.

[dolbyman]

Then a ticket would be the best idea, I have seen issues with this a couple of times(just never myself), but nobody ever reported back, so please report back on what QNAP says

[qnapdown]

Thanks for your time going through with these. Raised a ticket with QNAP couple of days back and awaiting a response.

Will definitely report back with details.

[Toxic]

Have you tried enabling “Local Master Browser” in the SMB advanced options?

When the NAS is selected as Local Master Browser there is a chance it would be visible in Network Neighborhood.

How to enable LMB (Local Master Browser) in QTS?

[dolbyman]

But if OP tried to mount \NASNAMEORIP\Sharename, the masterbrowser option should not matter … at least that is what I read between the lines, all this Qfinder stuff was just done because the regular method did not work ? (no?..maybe I am wrong)

[qnapdown]

I have enabled LMB now. No difference.

[qnapdown]

For a fact, I am unable to enable windows option “Turn on file and printer sharing” under Advanced sharing settings

OS = Windows 10
But I have more updates to give you all.

[qnapdown]

I have another desktop - Which is on Windows 11. Wanted to give a try on that one. So spent 3 hours midnight until 2 AM on it to get this working on Windows 11 -

Got this error message first -

"You can’t access this shared folder because your Organization’s
security policies block unauthenticated guest access. These
policies help protect your PC from unsafe or malicious devices on
the network. "

Added Key AllowInsecureGuestAuth to registry with value as 1. Below are the details -

RegEdit Path = HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
Key (DWORD 32-bit) = AllowInsecureGuestAuth

Then this error "You can’t access this shared folder because your Organization’s security policies block unauthenticated guest access. " disappeared.

Now when I tried reconnecting(with qnap admin login), I had an different issue / error message -

To resolve the this issue/error(multiple connections to a server or shared resource by the same user), I executed the below 2 commands from command prompt (launch cmd as administrator) one after the other in the same order.

net stop workstation /y
net start workstation

Then I did the same previous action - Connect by giving the folder name along with the server/qnap device name/ip address -
\xxx.xx.x.xx\SharedFolderName.

It requested the login/password. I keyed in the NAS admin login info, then the connection was successful. I was able to access that particular shared folder.

Now as a magic, just typing the server in the run command (\xxx.xxx.x.xx) brings up all the shared folders from the QNAP as well.

Magic

Windows have become monopoly and they are much worse than a rubbish thing.

Yet to sort the issues on Windows 10. Will try and find some time later today or later this week.

Or will simply upgrade to Windows 11

FLIP the WINDOWS… Just behaves like Donald Duck…

[Franklin]

One other thing to try: Control panel; shared folders. Select the folder in question and edit permissions. Make sure the windows user has permission to read and write the folder. I realize this might be trivial-but when I first got a NAS over 10 years ago, I did not realize this. It took me s day to figure out.

[qnapdown]

Iam not using windows login. I am using admin login.

By the way I still cant enable file sharing option. Also i type anything from run and it opens this window. Not sure what is happening here.

[qnapdown]

Ridiculous… Worked now.

I did so many stuff over the past few hours… I am not 100 % sure what did the trick. But I believe enabling SMB 1.0 on “windows features on or off” did the trick.

Prior enabling SMB1.0, I remember doing many things. Some of them I remember are as follows -

Did a Network Reset.
and
RegEdit Path = HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
Key (DWORD 32-bit) = AllowInsecureGuestAuth
and

Did SFC /SCANNOW from command prompt (as admin) multiple times. It found errors once(the scan fixed the errors during/after the scan). Rest of the time, the scan results came good.

Also executed the below from command prompt (as admin) one by one (Don’t ask me why I did these, because I was googling heavily and found so many things and this is a set of things I was told to query / execute for a error code I saw. Again I cant remember the error code now.

sc.exe qc lanmanworkstation
sc.exe qc bowser
sc.exe qc mrxsmb10
sc.exe qc mrxsmb20
sc.exe qc nsi

Except mrxsmb10, rest all came positive.
So then I enabled SMB 1.0 from Windows features. Did a restart. Executed the above set of things from command prompt again and now everything came positive.

Mapped a network drive with a shared folder and used the admin login of NAS.
Result - Worked successfully.
Then I did a RUN and just used the ip address - \xxx.xxx.x.xx\ and all shared folders opened up.
Result - Worked without Issues.

QNAP Support yet to respond.

Microsoft has become so complex man .
SMB 1.0 was supposed to be vulnerable and enabling that on windows 10 works and resolves the issue even though the minimum SMB version was set as 2.0 on QNAP.

Other update : QuFirewall was disabled and I was unable to swith on that on QTS. So I uninstalled it and then reinstalled it.
QuFirewall was enabled when I made this work on on both the PC’s (Windows10 and Windows11).

Windows11 PC only had one option enabled - SMB1.0/CIFS Client -

So I have updated the same now Windows 10 system as well. But will check the results later to see if this still works.

Thanks all for your support and responses on this. Take care. Bye…