#Qnap unable to find with qfinder full#
#Qnap unable to find with qfinder software#
#Qnap unable to find with qfinder windows#

It is trying to emulate a Windows NTFS/AD style permission system. The QNAP qui only has options for R, RW, Deny, or Special there is no X (execute). The QNAP has a form of Windows ACL enabled and the drive is formatted in NTFS. I understand what your saying as I am very familiar with Linux permission structure. I appreciate the help but this is not a Linux environment. You'll want rwx or r-x on directories.Īlso, any user can delete any file if they have write and execute on the file's directory, regardless of the permission modes or ownership of the file. If you set a directory permission to r-x, the user will be able to read the directory contents, and cd to the directory, but will not be able to remove, or create entries, in the directory. Write and execute on a directory means that the user can create, delete, rename and link entries in the directory. But 'w'rite is not operative unless the user also has execute permission on the directory. Write permission on a directory allows users to create files (including subdirectories), in the directory. Absent 'x' on a directory, a user won't be able to cd into the directory. The execute permission bit in Linux controls directory access. I setup a TEST first to make sure this was going to work at it failed miserably.

We don't want them to create sub folders in the main shared folder, so they all have read access to it to map the drive and rw to the folders they need access to. We setup security groups for each folder and added users according to what folders they should have access to. Any help would be appreciated.Įach sub folder needs to have separate permissions. I tried it on another QNAP with out windows ACL turn on and got the same results. We have advanced folder permissions turn on and windows ACL turn on. The permissions are showing the same on the QNAP gui and in windows explorer.

#Qnap unable to find with qfinder full#

I have check the effective permissions and they have full control. The drive maps no problem, the user can open the folders they have rw access to and cannot open the other folders, they also cannot write to the folder the have rw access to.

Each sub folder needs to have separate permissions. Currently all user have access to all folders. But that's all blunt theory - as QNAP Finder can't find it.We have a shared folder in our QNAP for 'Finance Users' We have security group that all 'Finance Users' are in and we use that to map the drive in a GPO. Common home and SMB routers do not block any broadcast or UPnP traffic on the L2 level - except where the switch is configured into different security zones, sometimes for LAN vs. However, changing the IP address for example is possible using QNAP Finder. because of the ISP supplied a new router using a different LAN subnet (Murphy's law #214312) - QNAP Finder might be able to discover, but can can't connect to the NAS Web UI. because of the NAS LAN interface was set fixed, and the router LAN config changed, ie. Things are slightly different when the computer and the NAS are in different TCP/IP sub-networks (i.e. That's a little bit more difficult to explain - but in reality it's easy: On these simple home routers all GbE ports for a flat Ethernet, a single broadcast domain - here the NAS _should_ be _discoverable_ if the handler is working there. When I just bought the QNAP TS-112 I could find my NAS in the QNAP Finder.

#Qnap unable to find with qfinder software#

Mouseke wrote:I tried the version of QNAP Finder you posted still no succes, how do I determine if QNAP Finder software is in the same subnet.