Qnap Create Shared Folder

[Courtland Boland]

LockFile (Oplocks): Opportunistic locking is a Windows mechanism for the client to place an opportunistic lock (oplock) on a file residing on a server in order to cache the data locally for improved performance. Oplocks is enabled by default for everyday usage. For networks that require multiple users concurrently accessing the same file such as a database, oplocks should be disabled.

Restrict the access of Recycle Bin to Administrators only for now:This option is available only when Network Recycle Bin is enabled. Selecting this option prevents non-administrator users from recovering and deleting files in the Recycle Bin.

Enable write-only access on FTP connection: Selecting this option gives the administrator exclusive read and write access to the shared folder. Non-administrator users connected through FTP only get write access.

Enable access-based shared enumeration (ABSE):When enabled, users can only see the shared folders that they have permission to mount and access. Guest account users must enter a username and password to view shared folders.

Note: You can select the option "Also delete the data (mounted files will not be deleted)" to delete the folder and the files in it. If you select not to delete the folder data, the data will be retained in the NAS. You can create a shared folder of the same name again to access the data.

QTS supports subfolder permissions for secure management of the folders and subfolders. You can specify read, read/write, and deny access of individual user to each folder and subfolder. To configure subfolder permissions, follow the steps below:

To specify read only permission on the root folder and read/write permission on the subfolders, you must set read/write permission on the root folder and use the option "Only admin can create files and folders" (to be explained later).

If an unidentified account ID (such as 500) is shown for a subfolder on the permission assignment page after you click the "Access Permissions" button next to a shared folder in Control Panel >Privilege Settings > Shared Folders > Shared Folder, it is likely that the permission of that subfolder has been granted to a user account that no longer exists. In this case, please select this unidentified account ID and click "Remove" to delete this account ID.

The NAS folders can be accessed via Samba connection (Windows) by default. You can specify the IP addresses and hosts which are allowed to access the NAS via Microsoft Networking. Follow the steps below to set up:

You can aggregate the shared folders on Microsoft network as a portal folder on the NAS and let the NAS users access the folders through your NAS. Up to 10 folders can be linked to a portal folder. To use this function, follow the steps below:

Use "Advanced Folder Permissions" to configure subfolder permissions directly from the NAS UI. There is no depth limitation for the subfolder permissions. However, it is highly recommended to change the permissions only on the first or second level of the subfolders. When "Advanced Folder Permissions" is enabled, click the "Folder Permissions" button under the "Shared Folders" tab to configure the subfolder permission settings. See Shared Folders" > "Folder Permission of this section for details.

Use "Windows ACL" to configure the subfolder and file level permissions from Windows File Explorer. All Windows Permissions are supported. For detailed Windows ACL behavior, please refer to standard NTFS permissions: _permissTo assign subfolder and file permissions to a user or a user group, full control share-level permissions must be granted to the user or user group.

When Windows ACL is enabled while "Advanced Folder Permissions" are disabled, subfolder and file permissions will have effect only when accessing the NAS from Windows File Explorer. Users connecting to the NAS via FTP, AFP, or File Station will only have share-level permissions.

When Windows ACL and Advanced Folder Permissions are both enabled, users cannot configure Advanced Folder Permissions from the NAS UI. The permissions (Read only, Read/Write, and Deny) of Advanced Folder Permissions for AFP, File Station, and FTP will automatically follow Windows ACL configuration.

Hi have been successfully running Synthing on my QNAP for a number of years, but recently I had issue where the drives all got full and backups stopped, I reclaimed alot of disk space back by archiving off the data.Then I noticed I could not launch Syncthing, web page just gave generic message not available. I tried starting and stopping the ST app but no joy so then I deleted the app and installed it again. Upon starting everything is back to first time setup.Now issue is I try to add the folder I wish to sync my clients with but not able to as its says permissions denied.I am logged into QNAP as admin, but I cant work out how to see what account the syncting app is using.

Hi, still having issues, but decided to reset QNAP back to factory settings. After I setup the shares I can now at least start the scanning of the folder but it still complains of permission denied to all the folders in the folder I want to share.

I see that when you start syncthing it creates a user called syncthing and its not a member of the group that has permissions to this folder (admin and administrators group have permissions) but even if I add the syncthing user to the administrators group it still has access denied. This folder is share out on the network and my other accounts have read and write access ok. So not sure what to do next.

Hi, in the end I gave up trying to share the file on the QNAP NAS. As it was basically syncing to my laptops. I deleted the contents on the NAS, then started the sync from the laptop upto the NAS and that worked. Perhaps I should have done it this way all along.So for me it now works.

i enabled advanced permissions. I Shared Testing1234 then i click on folder 2 > Add user 1 as read only > went to the desktop > map network drive > \qnapipaddress\testing1234\folder1\folder2 > connect as different credentials > entered the user 1 credentials > the credentials keeps popping up

When adding libraries it allows me to browse the local linux file system for content - but clicking "Network" displays nothing. I tried manually entering UNC paths and it refused to accept them. Is it possible to add content using UNC paths?

I just finished configuring my settings. Just added my movies library. Currently scanning. Since my movies are in a direct play format and codecs (mp4, h264, aac and ac3 tracks) I want to see if it won't direct play the movies.

My main goal was to integrate with Kodi. I am running openelec 5.08 (raspberry Pi2) Kodi 14.2 and obviously the NAS has all the media and mysql to sync all the players. I read that people were integrating the Kodi and Emby databases which is what I hoping for so I could view all my library from either Kodi or Emby (local network or remotely).

That will probably be chapter image extracts - they're quite intensive. Once the first library scan has completed you shouldn't really see that issue again unless you add a heap of content all at once.

Yeah. I know. My only worry right now is the amount of applications I have running on the server that run multiple tasks at the same time. I have sonarr, couchpotato, nzbget, plex, and now emby. I fear Emby may slow down my download speed in nzbget since it is so resources intensive. Additionally, what would happen when both plex and emby adding the same content to their library after a download is complete. I have both set to real time monitoring. Wait...I also have nzbget convert my download to mp4s. Can you imagine the server converting, plex extracting chapters and emby extracting chapters all at the same time.

I want to use Emby as the library server, but have Kodi access the ISOs directly. The file path appears as /share/CACHEDEV1_DATA/Multimedia/Movies but the 'network' button doesn't find the NAS. I can't seem to figure out how to use the 'Path Substitution' dialog, so I don't know how to make the entries, and there doesn't seem to be much documentation on how to go about this.

Sorry for digging up this old thread but I am having this problem of having a shared folder on the QNAP pointing to a server share on s different machine. Does this path substitution work with QNAP Firm Ware 20161214-4.2.2?

I can specify the library path to a local shared folder but in the next entry below "Path" it only will allow me to select a path that is local on the machine any other path entry will not allow me to create this shared folder.

I removed two shared folders from my QNAP (version 4.2) but the space occupied remains the same. I used privilige settings -> shared folders and removed the shared folders. Is there a way to reclaim this space? I emptied the network recycle bin but that didn't work.

On QNAP I shared the whole disk let's say : Disk-1. I have no idea whether the QNAP creates a shared folder named Disk-1 or if it's the real Disk. Thats my issue. OMV will create a folder named "Disk-1" as far as I understand. Maybe I'm wrong. So that's why I'm asking.

In addition, once the drive is installed in OMV, you can use ssh and a tool like Midnight Commander to move files around. That means that you can create an empty OMV share, as normal, and later move existing files on the drive into that share.

I have activated the rsync service and created a private shared folder named "RSync". On my Windows machine I mapped a network drive to that share (Y:). I created a folder on that share for each machine I wanted to backup.

In the rsync configuration on qnap you have to specify a username and password. I tried to use that username/password to logon to qnap/RSync, but it refused. It also wouldn't let me connect directly to qnap/RSync/laptop/data. Then I reconfigured the username/password on rsync to be the same as the username/password that I can connect to qnap/RSync with and ran rsync again (after first destroying the private shared folder and creating it again). I could connect to qnap/Rsync using that username/password. I could go into folder "laptop", but it still refused me acces to folder "data".

3a8082e126