Samba write access problem: parameter does not show in testparm even though it is in smb.conf

Clash Royale CLAN TAG#URR8PPP
I am trying to get a samba share setup so that users have both read and write permissions. I thought that I would be able to do this by editing /etc/samba/smb.conf to add my share like so:
[CLOUD]
path = /cloud
writable = yes
security = user
valid users = neon, win
write list = neon, win
and then running:
$ sudo systemctl restart smb.service
$ sudo systemctl restart nmb.service
I can access my share from the two accounts, but neither can write. When I run testparam, some of the parameters are missing(security and writable, but there is no explicit error.
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[printers]"
Processing section "[CLOUD]"
Global parameter security found in service section!
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
dns proxy = No
log file = /usr/local/samba/var/log.%m
max log size = 50
server role = standalone server
server string = Samba Server
workgroup = MYGROUP
idmap config * : backend = tdb
[homes]
browseable = No
comment = Home Directories
read only = No
[printers]
browseable = No
comment = All Printers
path = /usr/spool/samba
printable = Yes
[CLOUD]
path = /cloud
read only = No
valid users = neon win
write list = neon win
I take this to mean that the writable = yes parameter is not being recognized, but since there are no errors I have no idea why. Any suggestions as to what might be going on here?
I am using Arch.
permissions configuration samba cifs
add a comment |
I am trying to get a samba share setup so that users have both read and write permissions. I thought that I would be able to do this by editing /etc/samba/smb.conf to add my share like so:
[CLOUD]
path = /cloud
writable = yes
security = user
valid users = neon, win
write list = neon, win
and then running:
$ sudo systemctl restart smb.service
$ sudo systemctl restart nmb.service
I can access my share from the two accounts, but neither can write. When I run testparam, some of the parameters are missing(security and writable, but there is no explicit error.
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[printers]"
Processing section "[CLOUD]"
Global parameter security found in service section!
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
dns proxy = No
log file = /usr/local/samba/var/log.%m
max log size = 50
server role = standalone server
server string = Samba Server
workgroup = MYGROUP
idmap config * : backend = tdb
[homes]
browseable = No
comment = Home Directories
read only = No
[printers]
browseable = No
comment = All Printers
path = /usr/spool/samba
printable = Yes
[CLOUD]
path = /cloud
read only = No
valid users = neon win
write list = neon win
I take this to mean that the writable = yes parameter is not being recognized, but since there are no errors I have no idea why. Any suggestions as to what might be going on here?
I am using Arch.
permissions configuration samba cifs
add a comment |
I am trying to get a samba share setup so that users have both read and write permissions. I thought that I would be able to do this by editing /etc/samba/smb.conf to add my share like so:
[CLOUD]
path = /cloud
writable = yes
security = user
valid users = neon, win
write list = neon, win
and then running:
$ sudo systemctl restart smb.service
$ sudo systemctl restart nmb.service
I can access my share from the two accounts, but neither can write. When I run testparam, some of the parameters are missing(security and writable, but there is no explicit error.
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[printers]"
Processing section "[CLOUD]"
Global parameter security found in service section!
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
dns proxy = No
log file = /usr/local/samba/var/log.%m
max log size = 50
server role = standalone server
server string = Samba Server
workgroup = MYGROUP
idmap config * : backend = tdb
[homes]
browseable = No
comment = Home Directories
read only = No
[printers]
browseable = No
comment = All Printers
path = /usr/spool/samba
printable = Yes
[CLOUD]
path = /cloud
read only = No
valid users = neon win
write list = neon win
I take this to mean that the writable = yes parameter is not being recognized, but since there are no errors I have no idea why. Any suggestions as to what might be going on here?
I am using Arch.
permissions configuration samba cifs
I am trying to get a samba share setup so that users have both read and write permissions. I thought that I would be able to do this by editing /etc/samba/smb.conf to add my share like so:
[CLOUD]
path = /cloud
writable = yes
security = user
valid users = neon, win
write list = neon, win
and then running:
$ sudo systemctl restart smb.service
$ sudo systemctl restart nmb.service
I can access my share from the two accounts, but neither can write. When I run testparam, some of the parameters are missing(security and writable, but there is no explicit error.
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[printers]"
Processing section "[CLOUD]"
Global parameter security found in service section!
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
dns proxy = No
log file = /usr/local/samba/var/log.%m
max log size = 50
server role = standalone server
server string = Samba Server
workgroup = MYGROUP
idmap config * : backend = tdb
[homes]
browseable = No
comment = Home Directories
read only = No
[printers]
browseable = No
comment = All Printers
path = /usr/spool/samba
printable = Yes
[CLOUD]
path = /cloud
read only = No
valid users = neon win
write list = neon win
I take this to mean that the writable = yes parameter is not being recognized, but since there are no errors I have no idea why. Any suggestions as to what might be going on here?
I am using Arch.
permissions configuration samba cifs
permissions configuration samba cifs
asked Feb 26 at 10:30
ThoughtcraftThoughtcraft
18811
18811
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Try this:
[CLOUD]
writeable = yes
path = /cloud
valid users = neon,win
Restart smbd
Check also read/write permissions directly in your Linux system when you have logged in as user neon or win.
I often had to sign out/in again in Windows
You were right, it was a permission issue. I had ranchmod 777on my shared folder and it seems ok now. I'm still a bit confused about the output of testparm but I guess that doesn't matter since it wasn't even the problem. Unfortunately that did not work. Also, the output of testparm is still different than the smb.conf file in that it saysread only = Noandwriteable = yesis missing.
– Thoughtcraft
Feb 26 at 12:00
Well, I still cant write from the neon (linux) user. But I guess that is a separate problem because Windows can write to the share now.
– Thoughtcraft
Feb 26 at 12:12
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f503102%2fsamba-write-access-problem-parameter-does-not-show-in-testparm-even-though-it-i%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Try this:
[CLOUD]
writeable = yes
path = /cloud
valid users = neon,win
Restart smbd
Check also read/write permissions directly in your Linux system when you have logged in as user neon or win.
I often had to sign out/in again in Windows
You were right, it was a permission issue. I had ranchmod 777on my shared folder and it seems ok now. I'm still a bit confused about the output of testparm but I guess that doesn't matter since it wasn't even the problem. Unfortunately that did not work. Also, the output of testparm is still different than the smb.conf file in that it saysread only = Noandwriteable = yesis missing.
– Thoughtcraft
Feb 26 at 12:00
Well, I still cant write from the neon (linux) user. But I guess that is a separate problem because Windows can write to the share now.
– Thoughtcraft
Feb 26 at 12:12
add a comment |
Try this:
[CLOUD]
writeable = yes
path = /cloud
valid users = neon,win
Restart smbd
Check also read/write permissions directly in your Linux system when you have logged in as user neon or win.
I often had to sign out/in again in Windows
You were right, it was a permission issue. I had ranchmod 777on my shared folder and it seems ok now. I'm still a bit confused about the output of testparm but I guess that doesn't matter since it wasn't even the problem. Unfortunately that did not work. Also, the output of testparm is still different than the smb.conf file in that it saysread only = Noandwriteable = yesis missing.
– Thoughtcraft
Feb 26 at 12:00
Well, I still cant write from the neon (linux) user. But I guess that is a separate problem because Windows can write to the share now.
– Thoughtcraft
Feb 26 at 12:12
add a comment |
Try this:
[CLOUD]
writeable = yes
path = /cloud
valid users = neon,win
Restart smbd
Check also read/write permissions directly in your Linux system when you have logged in as user neon or win.
I often had to sign out/in again in Windows
Try this:
[CLOUD]
writeable = yes
path = /cloud
valid users = neon,win
Restart smbd
Check also read/write permissions directly in your Linux system when you have logged in as user neon or win.
I often had to sign out/in again in Windows
answered Feb 26 at 11:00
rottrigesrottriges
364
364
You were right, it was a permission issue. I had ranchmod 777on my shared folder and it seems ok now. I'm still a bit confused about the output of testparm but I guess that doesn't matter since it wasn't even the problem. Unfortunately that did not work. Also, the output of testparm is still different than the smb.conf file in that it saysread only = Noandwriteable = yesis missing.
– Thoughtcraft
Feb 26 at 12:00
Well, I still cant write from the neon (linux) user. But I guess that is a separate problem because Windows can write to the share now.
– Thoughtcraft
Feb 26 at 12:12
add a comment |
You were right, it was a permission issue. I had ranchmod 777on my shared folder and it seems ok now. I'm still a bit confused about the output of testparm but I guess that doesn't matter since it wasn't even the problem. Unfortunately that did not work. Also, the output of testparm is still different than the smb.conf file in that it saysread only = Noandwriteable = yesis missing.
– Thoughtcraft
Feb 26 at 12:00
Well, I still cant write from the neon (linux) user. But I guess that is a separate problem because Windows can write to the share now.
– Thoughtcraft
Feb 26 at 12:12
You were right, it was a permission issue. I had ran
chmod 777 on my shared folder and it seems ok now. I'm still a bit confused about the output of testparm but I guess that doesn't matter since it wasn't even the problem. Unfortunately that did not work. Also, the output of testparm is still different than the smb.conf file in that it says read only = No and writeable = yes is missing.– Thoughtcraft
Feb 26 at 12:00
You were right, it was a permission issue. I had ran
chmod 777 on my shared folder and it seems ok now. I'm still a bit confused about the output of testparm but I guess that doesn't matter since it wasn't even the problem. Unfortunately that did not work. Also, the output of testparm is still different than the smb.conf file in that it says read only = No and writeable = yes is missing.– Thoughtcraft
Feb 26 at 12:00
Well, I still cant write from the neon (linux) user. But I guess that is a separate problem because Windows can write to the share now.
– Thoughtcraft
Feb 26 at 12:12
Well, I still cant write from the neon (linux) user. But I guess that is a separate problem because Windows can write to the share now.
– Thoughtcraft
Feb 26 at 12:12
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f503102%2fsamba-write-access-problem-parameter-does-not-show-in-testparm-even-though-it-i%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown