Mounting Windows server shares in fstab
I want to be able to save to an XLSM file on Windows Server 2008. I can open the file using LibreOffice but cannot save using smb.
Research has let me to believe that I need to somehow mount the server using cifs instead of smb. I have this line in my fstab file.
//192.168.0.16/new_server /media/hpserver cifs -o vers=2.0 iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000, 0 0
I cannot for the life of me figure out what I am missing. I am either getting a parse error with the -o ver=2.0 or if I remove that part, I get a Host is down error.
Can someone please help me to understand what I am doing wrong? I am running Ubuntu 18.04 64 bits
/media/hpserver is an empty existing folder.
server mount samba libreoffice fstab
edited 5 hours ago
Pablo Bianchi
2,72821533
asked 6 hours ago
SlickTrickSlickTrick
583
New contributor
SlickTrick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I want to be able to save to an XLSM file on Windows Server 2008. I can open the file using LibreOffice but cannot save using smb.
Research has let me to believe that I need to somehow mount the server using cifs instead of smb. I have this line in my fstab file.
//192.168.0.16/new_server /media/hpserver cifs -o vers=2.0 iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000, 0 0
I cannot for the life of me figure out what I am missing. I am either getting a parse error with the -o ver=2.0 or if I remove that part, I get a Host is down error.
Can someone please help me to understand what I am doing wrong? I am running Ubuntu 18.04 64 bits
/media/hpserver is an empty existing folder.
server mount samba libreoffice fstab
edited 5 hours ago
Pablo Bianchi
2,72821533
asked 6 hours ago
SlickTrickSlickTrick
583
New contributor
SlickTrick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
AFAIK the options need to be in a single comma-delimited string, like-o vers=2.0,iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000(not sure that a trailing comma is allowed)
– steeldriver
6 hours ago
add a comment |
I want to be able to save to an XLSM file on Windows Server 2008. I can open the file using LibreOffice but cannot save using smb.
Research has let me to believe that I need to somehow mount the server using cifs instead of smb. I have this line in my fstab file.
//192.168.0.16/new_server /media/hpserver cifs -o vers=2.0 iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000, 0 0
I cannot for the life of me figure out what I am missing. I am either getting a parse error with the -o ver=2.0 or if I remove that part, I get a Host is down error.
Can someone please help me to understand what I am doing wrong? I am running Ubuntu 18.04 64 bits
/media/hpserver is an empty existing folder.
server mount samba libreoffice fstab
edited 5 hours ago
Pablo Bianchi
2,72821533
asked 6 hours ago
SlickTrickSlickTrick
583
New contributor
SlickTrick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I want to be able to save to an XLSM file on Windows Server 2008. I can open the file using LibreOffice but cannot save using smb.
Research has let me to believe that I need to somehow mount the server using cifs instead of smb. I have this line in my fstab file.
//192.168.0.16/new_server /media/hpserver cifs -o vers=2.0 iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000, 0 0
I cannot for the life of me figure out what I am missing. I am either getting a parse error with the -o ver=2.0 or if I remove that part, I get a Host is down error.
Can someone please help me to understand what I am doing wrong? I am running Ubuntu 18.04 64 bits
/media/hpserver is an empty existing folder.
server mount samba libreoffice fstab
server mount samba libreoffice fstab
edited 5 hours ago
Pablo Bianchi
2,72821533
asked 6 hours ago
SlickTrickSlickTrick
583
New contributor
SlickTrick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 5 hours ago
Pablo Bianchi
2,72821533
asked 6 hours ago
SlickTrickSlickTrick
583
New contributor
SlickTrick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 5 hours ago
Pablo Bianchi
2,72821533
edited 5 hours ago
Pablo Bianchi
2,72821533
edited 5 hours ago
Pablo Bianchi
2,72821533
2,72821533
asked 6 hours ago
SlickTrickSlickTrick
583
New contributor
SlickTrick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 6 hours ago
SlickTrickSlickTrick
583
asked 6 hours ago
SlickTrickSlickTrick
583
583
New contributor
SlickTrick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
SlickTrick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
SlickTrick is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
AFAIK the options need to be in a single comma-delimited string, like-o vers=2.0,iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000(not sure that a trailing comma is allowed)
– steeldriver
6 hours ago
add a comment |
1
AFAIK the options need to be in a single comma-delimited string, like-o vers=2.0,iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000(not sure that a trailing comma is allowed)
– steeldriver
6 hours ago
1
1
AFAIK the options need to be in a single comma-delimited string, like
-o vers=2.0,iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000 (not sure that a trailing comma is allowed)– steeldriver
6 hours ago
AFAIK the options need to be in a single comma-delimited string, like
-o vers=2.0,iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000 (not sure that a trailing comma is allowed)– steeldriver
6 hours ago
add a comment |
2 Answers
2
active
oldest
votes
Sorry for posting an answer I can't comment yet. It sounds like a permissions error, I'd look up setting correct permissions for cifs. I had similar issues not being able to write to my shares when I set up my NAS using a raspberry pi. Try something along the lines of //your/server/ /your/mount/point cifs defaults,uid=username,gid=username,user=user,password=password,rw 0 0 obviously you can replace the username/password bit with you credentials. Also try sudo mount -t cifs //your/server /mount/point/ -o username=username to test mounting without having to reboot.
answered 6 hours ago
rohtuarohtua
261
I have tried both of your suggestions. The first one I get a parse error --ignored which makes me think I have some wrong syntax somehow, and when connecting from the terminal, I get host is down.
– SlickTrick
5 hours ago
1
I've had a look on Google. There's a few suggestions here. serverfault.com/questions/414074/mount-cifs-host-is-down
– rohtua
5 hours ago
Making progress here, it did not have the direct answer, however it did link another source that now has me connecting. I can now mount and access, but no write access. Gonna see if there is a missing command in that line. I am sure the finish line is in sight now. I'll report back.
– SlickTrick
5 hours ago
1
I got it! //192.168.0.16/new_server /media/hpserver cifs defaults,iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000,vers=1.0,noperm This is the command I used, and I am now able to connect, and read/write my file! Thank you all who helped.
– SlickTrick
5 hours ago
add a comment |
Please install the cifs-utils with:
sudo apt-get install cifs-utils
sudo mount -a
answered 6 hours ago
AlpyAlpy
813
New contributor
Alpy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have done this already, I just did it again, and am getting; cifs-utils is already the newest version (2:6.8-1). Still getting an error when I try and run the mount command. mount error(112): Host is down
– SlickTrick
6 hours ago
is telnet 192.168.0.16 139 working??
– Alpy
6 hours ago
Good idea on telnet, however when I try and telnet, it looks like it is frozen for a minute or so, then it passes me a message back "Connection closed by foreign host" It did tell me that the Escape character is '^' which looks like it is working? What I don't get, is that smb://192.168.... works just fine for accessing, and writing everything except what I want to write to.
– SlickTrick
5 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});
}
});
SlickTrick is a new contributor. Be nice, and check out our Code of Conduct.
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%2faskubuntu.com%2fquestions%2f1121209%2fmounting-windows-server-shares-in-fstab%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sorry for posting an answer I can't comment yet. It sounds like a permissions error, I'd look up setting correct permissions for cifs. I had similar issues not being able to write to my shares when I set up my NAS using a raspberry pi. Try something along the lines of //your/server/ /your/mount/point cifs defaults,uid=username,gid=username,user=user,password=password,rw 0 0 obviously you can replace the username/password bit with you credentials. Also try sudo mount -t cifs //your/server /mount/point/ -o username=username to test mounting without having to reboot.
answered 6 hours ago
rohtuarohtua
261
I have tried both of your suggestions. The first one I get a parse error --ignored which makes me think I have some wrong syntax somehow, and when connecting from the terminal, I get host is down.
– SlickTrick
5 hours ago
1
I've had a look on Google. There's a few suggestions here. serverfault.com/questions/414074/mount-cifs-host-is-down
– rohtua
5 hours ago
Making progress here, it did not have the direct answer, however it did link another source that now has me connecting. I can now mount and access, but no write access. Gonna see if there is a missing command in that line. I am sure the finish line is in sight now. I'll report back.
– SlickTrick
5 hours ago
1
I got it! //192.168.0.16/new_server /media/hpserver cifs defaults,iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000,vers=1.0,noperm This is the command I used, and I am now able to connect, and read/write my file! Thank you all who helped.
– SlickTrick
5 hours ago
add a comment |
Sorry for posting an answer I can't comment yet. It sounds like a permissions error, I'd look up setting correct permissions for cifs. I had similar issues not being able to write to my shares when I set up my NAS using a raspberry pi. Try something along the lines of //your/server/ /your/mount/point cifs defaults,uid=username,gid=username,user=user,password=password,rw 0 0 obviously you can replace the username/password bit with you credentials. Also try sudo mount -t cifs //your/server /mount/point/ -o username=username to test mounting without having to reboot.
answered 6 hours ago
rohtuarohtua
261
I have tried both of your suggestions. The first one I get a parse error --ignored which makes me think I have some wrong syntax somehow, and when connecting from the terminal, I get host is down.
– SlickTrick
5 hours ago
1
I've had a look on Google. There's a few suggestions here. serverfault.com/questions/414074/mount-cifs-host-is-down
– rohtua
5 hours ago
Making progress here, it did not have the direct answer, however it did link another source that now has me connecting. I can now mount and access, but no write access. Gonna see if there is a missing command in that line. I am sure the finish line is in sight now. I'll report back.
– SlickTrick
5 hours ago
1
I got it! //192.168.0.16/new_server /media/hpserver cifs defaults,iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000,vers=1.0,noperm This is the command I used, and I am now able to connect, and read/write my file! Thank you all who helped.
– SlickTrick
5 hours ago
add a comment |
Sorry for posting an answer I can't comment yet. It sounds like a permissions error, I'd look up setting correct permissions for cifs. I had similar issues not being able to write to my shares when I set up my NAS using a raspberry pi. Try something along the lines of //your/server/ /your/mount/point cifs defaults,uid=username,gid=username,user=user,password=password,rw 0 0 obviously you can replace the username/password bit with you credentials. Also try sudo mount -t cifs //your/server /mount/point/ -o username=username to test mounting without having to reboot.
answered 6 hours ago
rohtuarohtua
261
Sorry for posting an answer I can't comment yet. It sounds like a permissions error, I'd look up setting correct permissions for cifs. I had similar issues not being able to write to my shares when I set up my NAS using a raspberry pi. Try something along the lines of //your/server/ /your/mount/point cifs defaults,uid=username,gid=username,user=user,password=password,rw 0 0 obviously you can replace the username/password bit with you credentials. Also try sudo mount -t cifs //your/server /mount/point/ -o username=username to test mounting without having to reboot.
answered 6 hours ago
rohtuarohtua
261
answered 6 hours ago
rohtuarohtua
261
answered 6 hours ago
rohtuarohtua
261
answered 6 hours ago
rohtuarohtua
261
261
I have tried both of your suggestions. The first one I get a parse error --ignored which makes me think I have some wrong syntax somehow, and when connecting from the terminal, I get host is down.
– SlickTrick
5 hours ago
1
I've had a look on Google. There's a few suggestions here. serverfault.com/questions/414074/mount-cifs-host-is-down
– rohtua
5 hours ago
Making progress here, it did not have the direct answer, however it did link another source that now has me connecting. I can now mount and access, but no write access. Gonna see if there is a missing command in that line. I am sure the finish line is in sight now. I'll report back.
– SlickTrick
5 hours ago
1
I got it! //192.168.0.16/new_server /media/hpserver cifs defaults,iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000,vers=1.0,noperm This is the command I used, and I am now able to connect, and read/write my file! Thank you all who helped.
– SlickTrick
5 hours ago
add a comment |
I have tried both of your suggestions. The first one I get a parse error --ignored which makes me think I have some wrong syntax somehow, and when connecting from the terminal, I get host is down.
– SlickTrick
5 hours ago
1
I've had a look on Google. There's a few suggestions here. serverfault.com/questions/414074/mount-cifs-host-is-down
– rohtua
5 hours ago
Making progress here, it did not have the direct answer, however it did link another source that now has me connecting. I can now mount and access, but no write access. Gonna see if there is a missing command in that line. I am sure the finish line is in sight now. I'll report back.
– SlickTrick
5 hours ago
1
I got it! //192.168.0.16/new_server /media/hpserver cifs defaults,iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000,vers=1.0,noperm This is the command I used, and I am now able to connect, and read/write my file! Thank you all who helped.
– SlickTrick
5 hours ago
I have tried both of your suggestions. The first one I get a parse error --ignored which makes me think I have some wrong syntax somehow, and when connecting from the terminal, I get host is down.
– SlickTrick
5 hours ago
I have tried both of your suggestions. The first one I get a parse error --ignored which makes me think I have some wrong syntax somehow, and when connecting from the terminal, I get host is down.
– SlickTrick
5 hours ago
1
1
I've had a look on Google. There's a few suggestions here. serverfault.com/questions/414074/mount-cifs-host-is-down
– rohtua
5 hours ago
I've had a look on Google. There's a few suggestions here. serverfault.com/questions/414074/mount-cifs-host-is-down
– rohtua
5 hours ago
Making progress here, it did not have the direct answer, however it did link another source that now has me connecting. I can now mount and access, but no write access. Gonna see if there is a missing command in that line. I am sure the finish line is in sight now. I'll report back.
– SlickTrick
5 hours ago
Making progress here, it did not have the direct answer, however it did link another source that now has me connecting. I can now mount and access, but no write access. Gonna see if there is a missing command in that line. I am sure the finish line is in sight now. I'll report back.
– SlickTrick
5 hours ago
1
1
I got it! //192.168.0.16/new_server /media/hpserver cifs defaults,iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000,vers=1.0,noperm This is the command I used, and I am now able to connect, and read/write my file! Thank you all who helped.
– SlickTrick
5 hours ago
I got it! //192.168.0.16/new_server /media/hpserver cifs defaults,iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000,vers=1.0,noperm This is the command I used, and I am now able to connect, and read/write my file! Thank you all who helped.
– SlickTrick
5 hours ago
add a comment |
Please install the cifs-utils with:
sudo apt-get install cifs-utils
sudo mount -a
answered 6 hours ago
AlpyAlpy
813
New contributor
Alpy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have done this already, I just did it again, and am getting; cifs-utils is already the newest version (2:6.8-1). Still getting an error when I try and run the mount command. mount error(112): Host is down
– SlickTrick
6 hours ago
is telnet 192.168.0.16 139 working??
– Alpy
6 hours ago
Good idea on telnet, however when I try and telnet, it looks like it is frozen for a minute or so, then it passes me a message back "Connection closed by foreign host" It did tell me that the Escape character is '^' which looks like it is working? What I don't get, is that smb://192.168.... works just fine for accessing, and writing everything except what I want to write to.
– SlickTrick
5 hours ago
add a comment |
Please install the cifs-utils with:
sudo apt-get install cifs-utils
sudo mount -a
answered 6 hours ago
AlpyAlpy
813
New contributor
Alpy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have done this already, I just did it again, and am getting; cifs-utils is already the newest version (2:6.8-1). Still getting an error when I try and run the mount command. mount error(112): Host is down
– SlickTrick
6 hours ago
is telnet 192.168.0.16 139 working??
– Alpy
6 hours ago
Good idea on telnet, however when I try and telnet, it looks like it is frozen for a minute or so, then it passes me a message back "Connection closed by foreign host" It did tell me that the Escape character is '^' which looks like it is working? What I don't get, is that smb://192.168.... works just fine for accessing, and writing everything except what I want to write to.
– SlickTrick
5 hours ago
add a comment |
Please install the cifs-utils with:
sudo apt-get install cifs-utils
sudo mount -a
answered 6 hours ago
AlpyAlpy
813
New contributor
Alpy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Please install the cifs-utils with:
sudo apt-get install cifs-utils
sudo mount -a
answered 6 hours ago
AlpyAlpy
813
New contributor
Alpy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 6 hours ago
AlpyAlpy
813
New contributor
Alpy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 6 hours ago
AlpyAlpy
813
answered 6 hours ago
AlpyAlpy
813
813
New contributor
Alpy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Alpy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Alpy is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have done this already, I just did it again, and am getting; cifs-utils is already the newest version (2:6.8-1). Still getting an error when I try and run the mount command. mount error(112): Host is down
– SlickTrick
6 hours ago
is telnet 192.168.0.16 139 working??
– Alpy
6 hours ago
Good idea on telnet, however when I try and telnet, it looks like it is frozen for a minute or so, then it passes me a message back "Connection closed by foreign host" It did tell me that the Escape character is '^' which looks like it is working? What I don't get, is that smb://192.168.... works just fine for accessing, and writing everything except what I want to write to.
– SlickTrick
5 hours ago
add a comment |
I have done this already, I just did it again, and am getting; cifs-utils is already the newest version (2:6.8-1). Still getting an error when I try and run the mount command. mount error(112): Host is down
– SlickTrick
6 hours ago
is telnet 192.168.0.16 139 working??
– Alpy
6 hours ago
Good idea on telnet, however when I try and telnet, it looks like it is frozen for a minute or so, then it passes me a message back "Connection closed by foreign host" It did tell me that the Escape character is '^' which looks like it is working? What I don't get, is that smb://192.168.... works just fine for accessing, and writing everything except what I want to write to.
– SlickTrick
5 hours ago
I have done this already, I just did it again, and am getting; cifs-utils is already the newest version (2:6.8-1). Still getting an error when I try and run the mount command. mount error(112): Host is down
– SlickTrick
6 hours ago
I have done this already, I just did it again, and am getting; cifs-utils is already the newest version (2:6.8-1). Still getting an error when I try and run the mount command. mount error(112): Host is down
– SlickTrick
6 hours ago
is telnet 192.168.0.16 139 working??
– Alpy
6 hours ago
is telnet 192.168.0.16 139 working??
– Alpy
6 hours ago
Good idea on telnet, however when I try and telnet, it looks like it is frozen for a minute or so, then it passes me a message back "Connection closed by foreign host" It did tell me that the Escape character is '^' which looks like it is working? What I don't get, is that smb://192.168.... works just fine for accessing, and writing everything except what I want to write to.
– SlickTrick
5 hours ago
Good idea on telnet, however when I try and telnet, it looks like it is frozen for a minute or so, then it passes me a message back "Connection closed by foreign host" It did tell me that the Escape character is '^' which looks like it is working? What I don't get, is that smb://192.168.... works just fine for accessing, and writing everything except what I want to write to.
– SlickTrick
5 hours ago
add a comment |
SlickTrick is a new contributor. Be nice, and check out our Code of Conduct.
SlickTrick is a new contributor. Be nice, and check out our Code of Conduct.
SlickTrick is a new contributor. Be nice, and check out our Code of Conduct.
SlickTrick is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1121209%2fmounting-windows-server-shares-in-fstab%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
1
AFAIK the options need to be in a single comma-delimited string, like
-o vers=2.0,iocharset=utf8,credentials=/home/me/.smbcredentials,gid=1000(not sure that a trailing comma is allowed)– steeldriver
6 hours ago