Can not add ACL ACL Owner CIFS
tuocmd
54 Posts
March 20, 2020, 4:19 pmQuote from tuocmd on March 20, 2020, 4:19 pmHi admin,
I Join to the AD in CIFS setting.
However, in the CIFS Share section, I cannot allow users to access ACL Owner.
You can share user manuals with AD and sharing models
Hi admin,
I Join to the AD in CIFS setting.
However, in the CIFS Share section, I cannot allow users to access ACL Owner.
You can share user manuals with AD and sharing models
admin
2,930 Posts
March 20, 2020, 4:34 pmQuote from admin on March 20, 2020, 4:34 pmFrom PetaSAN CIFS Shares page, you specify the ACL owner. Only the owner will have access to the share after creation. Then the owner, from Windows ui, grants other users /groups read/write on his share, just like a regular share he/she owns. From Windows right click on the share directory, properties, security...all in Windows.
In the near future we will also add snapshots support, browsing , time warp, restore will all be done through Windows.
From PetaSAN CIFS Shares page, you specify the ACL owner. Only the owner will have access to the share after creation. Then the owner, from Windows ui, grants other users /groups read/write on his share, just like a regular share he/she owns. From Windows right click on the share directory, properties, security...all in Windows.
In the near future we will also add snapshots support, browsing , time warp, restore will all be done through Windows.
ghbiz
76 Posts
March 20, 2020, 7:43 pmQuote from ghbiz on March 20, 2020, 7:43 pmjust to confirm, you are saying that you can only assign an ACL to a AD user. Why not be able to assign to a AD Group, that way, every user in that group can be included.
We have AD groups in our organization that are specific to Technical, Sales, Customer service, Billing, etc ...
just to confirm, you are saying that you can only assign an ACL to a AD user. Why not be able to assign to a AD Group, that way, every user in that group can be included.
We have AD groups in our organization that are specific to Technical, Sales, Customer service, Billing, etc ...
admin
2,930 Posts
March 20, 2020, 9:16 pmQuote from admin on March 20, 2020, 9:16 pmYou assign 1 owner, the owner can then allow/deny other groups/users to read/write. This is the same on Windows and Linux for shares and files, the owner of the file can allow other groups/user if he wishes.
In your case you can simply make the ACL ( Access Control List) owner the Domain Administrator for all shares, he is the owner, he can then go to a Windows box and use the regular share permission tab in Windows to grant the Sales group read/write on 1 share and the Billing group access to the other share...etc. Windows ACL is much more flexible than simply giving 1 group per share.
You assign 1 owner, the owner can then allow/deny other groups/users to read/write. This is the same on Windows and Linux for shares and files, the owner of the file can allow other groups/user if he wishes.
In your case you can simply make the ACL ( Access Control List) owner the Domain Administrator for all shares, he is the owner, he can then go to a Windows box and use the regular share permission tab in Windows to grant the Sales group read/write on 1 share and the Billing group access to the other share...etc. Windows ACL is much more flexible than simply giving 1 group per share.
tuocmd
54 Posts
March 20, 2020, 11:53 pmQuote from tuocmd on March 20, 2020, 11:53 pmFrom the page CIFS Share, I can not find Owner ACL.
Can you see image at the link below
https://imgur.com/a/Idpmmfv
From the page CIFS Share, I can not find Owner ACL.
Can you see image at the link below
tuocmd
54 Posts
March 21, 2020, 8:15 amQuote from tuocmd on March 21, 2020, 8:15 amHi admin
My system is divided into 3 parts as follows
1. Management network range: 192.168.1.0/24
2 . backend network range: 192.168.10.0/24
3. CIFS network range: 192.168.20.0/24.
So when I connect to AD via the CIFS array array it will be quite difficult,
Do you have any optimal way to connect to AD?
Hi admin
My system is divided into 3 parts as follows
1. Management network range: 192.168.1.0/24
2 . backend network range: 192.168.10.0/24
3. CIFS network range: 192.168.20.0/24.
So when I connect to AD via the CIFS array array it will be quite difficult,
Do you have any optimal way to connect to AD?
admin
2,930 Posts
March 21, 2020, 9:29 amQuote from admin on March 21, 2020, 9:29 amFor your first issue: if you do not see any domain users when adding a protected share, most probably the join did not work or it is currently not working. I recommend you unjoin and re-join.
For second issue: yes you do need an accessible IP address to be member of the domain, AD is not just security but plays a role in DNS for domain machines. It should be an IP in 1 of the 3 networks you specified, i am less sure if you can specify an external routable IP, if so then the AD DNS should be ping-able from the CIFS nodes and vice versa but i am not sure.
For your first issue: if you do not see any domain users when adding a protected share, most probably the join did not work or it is currently not working. I recommend you unjoin and re-join.
For second issue: yes you do need an accessible IP address to be member of the domain, AD is not just security but plays a role in DNS for domain machines. It should be an IP in 1 of the 3 networks you specified, i am less sure if you can specify an external routable IP, if so then the AD DNS should be ping-able from the CIFS nodes and vice versa but i am not sure.
Can not add ACL ACL Owner CIFS
tuocmd
54 Posts
Quote from tuocmd on March 20, 2020, 4:19 pmHi admin,
I Join to the AD in CIFS setting.
However, in the CIFS Share section, I cannot allow users to access ACL Owner.You can share user manuals with AD and sharing models
Hi admin,
I Join to the AD in CIFS setting.
However, in the CIFS Share section, I cannot allow users to access ACL Owner.
You can share user manuals with AD and sharing models
admin
2,930 Posts
Quote from admin on March 20, 2020, 4:34 pmFrom PetaSAN CIFS Shares page, you specify the ACL owner. Only the owner will have access to the share after creation. Then the owner, from Windows ui, grants other users /groups read/write on his share, just like a regular share he/she owns. From Windows right click on the share directory, properties, security...all in Windows.
In the near future we will also add snapshots support, browsing , time warp, restore will all be done through Windows.
From PetaSAN CIFS Shares page, you specify the ACL owner. Only the owner will have access to the share after creation. Then the owner, from Windows ui, grants other users /groups read/write on his share, just like a regular share he/she owns. From Windows right click on the share directory, properties, security...all in Windows.
In the near future we will also add snapshots support, browsing , time warp, restore will all be done through Windows.
ghbiz
76 Posts
Quote from ghbiz on March 20, 2020, 7:43 pmjust to confirm, you are saying that you can only assign an ACL to a AD user. Why not be able to assign to a AD Group, that way, every user in that group can be included.
We have AD groups in our organization that are specific to Technical, Sales, Customer service, Billing, etc ...
just to confirm, you are saying that you can only assign an ACL to a AD user. Why not be able to assign to a AD Group, that way, every user in that group can be included.
We have AD groups in our organization that are specific to Technical, Sales, Customer service, Billing, etc ...
admin
2,930 Posts
Quote from admin on March 20, 2020, 9:16 pmYou assign 1 owner, the owner can then allow/deny other groups/users to read/write. This is the same on Windows and Linux for shares and files, the owner of the file can allow other groups/user if he wishes.
In your case you can simply make the ACL ( Access Control List) owner the Domain Administrator for all shares, he is the owner, he can then go to a Windows box and use the regular share permission tab in Windows to grant the Sales group read/write on 1 share and the Billing group access to the other share...etc. Windows ACL is much more flexible than simply giving 1 group per share.
You assign 1 owner, the owner can then allow/deny other groups/users to read/write. This is the same on Windows and Linux for shares and files, the owner of the file can allow other groups/user if he wishes.
In your case you can simply make the ACL ( Access Control List) owner the Domain Administrator for all shares, he is the owner, he can then go to a Windows box and use the regular share permission tab in Windows to grant the Sales group read/write on 1 share and the Billing group access to the other share...etc. Windows ACL is much more flexible than simply giving 1 group per share.
tuocmd
54 Posts
Quote from tuocmd on March 20, 2020, 11:53 pmFrom the page CIFS Share, I can not find Owner ACL.
Can you see image at the link below
https://imgur.com/a/Idpmmfv
From the page CIFS Share, I can not find Owner ACL.
Can you see image at the link below
tuocmd
54 Posts
Quote from tuocmd on March 21, 2020, 8:15 amHi admin
My system is divided into 3 parts as follows
1. Management network range: 192.168.1.0/24
2 . backend network range: 192.168.10.0/24
3. CIFS network range: 192.168.20.0/24.So when I connect to AD via the CIFS array array it will be quite difficult,
Do you have any optimal way to connect to AD?
Hi admin
My system is divided into 3 parts as follows
1. Management network range: 192.168.1.0/24
2 . backend network range: 192.168.10.0/24
3. CIFS network range: 192.168.20.0/24.
So when I connect to AD via the CIFS array array it will be quite difficult,
Do you have any optimal way to connect to AD?
admin
2,930 Posts
Quote from admin on March 21, 2020, 9:29 amFor your first issue: if you do not see any domain users when adding a protected share, most probably the join did not work or it is currently not working. I recommend you unjoin and re-join.
For second issue: yes you do need an accessible IP address to be member of the domain, AD is not just security but plays a role in DNS for domain machines. It should be an IP in 1 of the 3 networks you specified, i am less sure if you can specify an external routable IP, if so then the AD DNS should be ping-able from the CIFS nodes and vice versa but i am not sure.
For your first issue: if you do not see any domain users when adding a protected share, most probably the join did not work or it is currently not working. I recommend you unjoin and re-join.
For second issue: yes you do need an accessible IP address to be member of the domain, AD is not just security but plays a role in DNS for domain machines. It should be an IP in 1 of the 3 networks you specified, i am less sure if you can specify an external routable IP, if so then the AD DNS should be ping-able from the CIFS nodes and vice versa but i am not sure.