I have a weird acess issue.
The setup is simple:
A veracrypt created volume file, created within a normal NTFS volume (Windows 10 Home).
The encrypted volume itself is also NTFS (else I couldn't share it).
There are also a couple of more Win 10 Home computers on the network.
The volume is shared with full acess to them.
Now the issue:
If I create a folder using one of the other computers on the network (or use the folders already available and moved in the veracrypt encrypted volume), then the folder is fully accessible by all.
If I create a folder using THE SAME computer that actually hosts the encrypted volume (!), then the other computers on the network do not have the right to read it.
When I go to see the content of the folder on the computer that hosts the encrypted volume (that should already have full access) then the system tells me that I can't see the properties of the folder (it even reports empty when it is not) except if I choose to see them permanently (takes over ownership?). When I do this, I read properly the folder contents AND the other computers can see them.
So it's a matter of the host computer itself not setting security properly on the veracrypt volume?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a weird acess issue.
The setup is simple:
A veracrypt created volume file, created within a normal NTFS volume (Windows 10 Home).
The encrypted volume itself is also NTFS (else I couldn't share it).
There are also a couple of more Win 10 Home computers on the network.
The volume is shared with full acess to them.
Now the issue:
If I create a folder using one of the other computers on the network (or use the folders already available and moved in the veracrypt encrypted volume), then the folder is fully accessible by all.
If I create a folder using THE SAME computer that actually hosts the encrypted volume (!), then the other computers on the network do not have the right to read it.
When I go to see the content of the folder on the computer that hosts the encrypted volume (that should already have full access) then the system tells me that I can't see the properties of the folder (it even reports empty when it is not) except if I choose to see them permanently (takes over ownership?). When I do this, I read properly the folder contents AND the other computers can see them.
So it's a matter of the host computer itself not setting security properly on the veracrypt volume?