How do I configure Samba so that Windows 10 doesn’t complain about insecure guest logons?












1















I’ve just set up a new Ubuntu 18.10 server with a single SMB share which I’d like to access from Windows. But whenever I try to open the paths \servername or \servernamesharename in Windows, I get this error message:




You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.




This is documented by Microsoft at Guest access in SMB2 disabled by default in Windows 10, Windows Server 2016 version 1709, and Windows Server 2019. If I use the Enable insecure guest logons group policy option, as suggested in the documentation, everything works fine. I can browse \servername without entering any credentials, and if I try to access \servernamesharename, I’m asked for a username and password. My Samba credentials work as expected.



But I don’t want to enable anything insecure! I’ve tried to disable all the default shares that are guest-accessible, and I’m happy to give up the ability to be able to browse \servername (although it would be nice to have). I don’t need to support any legacy clients; I just want to access the share from one Windows 10 machine with a username and password.



Noting that the error message refers to SMB2, I tried adding the line server min protocol = SMB3 to /etc/samba/smb.conf in the [global] section, but this didn’t change anything.



How can I configure Samba so that Windows 10 will prompt the user for credentials, rather than attempting to use an insecure guest logon?










share|improve this question























  • I had trouble setting up SAMBA at first - but then I found https://help.ubuntu.com/community/How%20to%20Create%20a%20Network%20Share%20Via%20Samba%20Via%20CLI%20%28Command-line%20interface/Linux%20Terminal%29%20-%20Uncomplicated,%20Simple%20and%20Brief%20Way!

    – Charles Green
    Feb 10 at 2:25











  • I also had to add to /etc/samba/smb.conf a line in the Global section: encrypt passwords = true

    – Charles Green
    Feb 10 at 2:38
















1















I’ve just set up a new Ubuntu 18.10 server with a single SMB share which I’d like to access from Windows. But whenever I try to open the paths \servername or \servernamesharename in Windows, I get this error message:




You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.




This is documented by Microsoft at Guest access in SMB2 disabled by default in Windows 10, Windows Server 2016 version 1709, and Windows Server 2019. If I use the Enable insecure guest logons group policy option, as suggested in the documentation, everything works fine. I can browse \servername without entering any credentials, and if I try to access \servernamesharename, I’m asked for a username and password. My Samba credentials work as expected.



But I don’t want to enable anything insecure! I’ve tried to disable all the default shares that are guest-accessible, and I’m happy to give up the ability to be able to browse \servername (although it would be nice to have). I don’t need to support any legacy clients; I just want to access the share from one Windows 10 machine with a username and password.



Noting that the error message refers to SMB2, I tried adding the line server min protocol = SMB3 to /etc/samba/smb.conf in the [global] section, but this didn’t change anything.



How can I configure Samba so that Windows 10 will prompt the user for credentials, rather than attempting to use an insecure guest logon?










share|improve this question























  • I had trouble setting up SAMBA at first - but then I found https://help.ubuntu.com/community/How%20to%20Create%20a%20Network%20Share%20Via%20Samba%20Via%20CLI%20%28Command-line%20interface/Linux%20Terminal%29%20-%20Uncomplicated,%20Simple%20and%20Brief%20Way!

    – Charles Green
    Feb 10 at 2:25











  • I also had to add to /etc/samba/smb.conf a line in the Global section: encrypt passwords = true

    – Charles Green
    Feb 10 at 2:38














1












1








1








I’ve just set up a new Ubuntu 18.10 server with a single SMB share which I’d like to access from Windows. But whenever I try to open the paths \servername or \servernamesharename in Windows, I get this error message:




You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.




This is documented by Microsoft at Guest access in SMB2 disabled by default in Windows 10, Windows Server 2016 version 1709, and Windows Server 2019. If I use the Enable insecure guest logons group policy option, as suggested in the documentation, everything works fine. I can browse \servername without entering any credentials, and if I try to access \servernamesharename, I’m asked for a username and password. My Samba credentials work as expected.



But I don’t want to enable anything insecure! I’ve tried to disable all the default shares that are guest-accessible, and I’m happy to give up the ability to be able to browse \servername (although it would be nice to have). I don’t need to support any legacy clients; I just want to access the share from one Windows 10 machine with a username and password.



Noting that the error message refers to SMB2, I tried adding the line server min protocol = SMB3 to /etc/samba/smb.conf in the [global] section, but this didn’t change anything.



How can I configure Samba so that Windows 10 will prompt the user for credentials, rather than attempting to use an insecure guest logon?










share|improve this question














I’ve just set up a new Ubuntu 18.10 server with a single SMB share which I’d like to access from Windows. But whenever I try to open the paths \servername or \servernamesharename in Windows, I get this error message:




You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.




This is documented by Microsoft at Guest access in SMB2 disabled by default in Windows 10, Windows Server 2016 version 1709, and Windows Server 2019. If I use the Enable insecure guest logons group policy option, as suggested in the documentation, everything works fine. I can browse \servername without entering any credentials, and if I try to access \servernamesharename, I’m asked for a username and password. My Samba credentials work as expected.



But I don’t want to enable anything insecure! I’ve tried to disable all the default shares that are guest-accessible, and I’m happy to give up the ability to be able to browse \servername (although it would be nice to have). I don’t need to support any legacy clients; I just want to access the share from one Windows 10 machine with a username and password.



Noting that the error message refers to SMB2, I tried adding the line server min protocol = SMB3 to /etc/samba/smb.conf in the [global] section, but this didn’t change anything.



How can I configure Samba so that Windows 10 will prompt the user for credentials, rather than attempting to use an insecure guest logon?







samba






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 10 at 0:09









sjysjy

1062




1062













  • I had trouble setting up SAMBA at first - but then I found https://help.ubuntu.com/community/How%20to%20Create%20a%20Network%20Share%20Via%20Samba%20Via%20CLI%20%28Command-line%20interface/Linux%20Terminal%29%20-%20Uncomplicated,%20Simple%20and%20Brief%20Way!

    – Charles Green
    Feb 10 at 2:25











  • I also had to add to /etc/samba/smb.conf a line in the Global section: encrypt passwords = true

    – Charles Green
    Feb 10 at 2:38



















  • I had trouble setting up SAMBA at first - but then I found https://help.ubuntu.com/community/How%20to%20Create%20a%20Network%20Share%20Via%20Samba%20Via%20CLI%20%28Command-line%20interface/Linux%20Terminal%29%20-%20Uncomplicated,%20Simple%20and%20Brief%20Way!

    – Charles Green
    Feb 10 at 2:25











  • I also had to add to /etc/samba/smb.conf a line in the Global section: encrypt passwords = true

    – Charles Green
    Feb 10 at 2:38

















I had trouble setting up SAMBA at first - but then I found https://help.ubuntu.com/community/How%20to%20Create%20a%20Network%20Share%20Via%20Samba%20Via%20CLI%20%28Command-line%20interface/Linux%20Terminal%29%20-%20Uncomplicated,%20Simple%20and%20Brief%20Way!

– Charles Green
Feb 10 at 2:25





I had trouble setting up SAMBA at first - but then I found https://help.ubuntu.com/community/How%20to%20Create%20a%20Network%20Share%20Via%20Samba%20Via%20CLI%20%28Command-line%20interface/Linux%20Terminal%29%20-%20Uncomplicated,%20Simple%20and%20Brief%20Way!

– Charles Green
Feb 10 at 2:25













I also had to add to /etc/samba/smb.conf a line in the Global section: encrypt passwords = true

– Charles Green
Feb 10 at 2:38





I also had to add to /etc/samba/smb.conf a line in the Global section: encrypt passwords = true

– Charles Green
Feb 10 at 2:38










0






active

oldest

votes











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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117030%2fhow-do-i-configure-samba-so-that-windows-10-doesn-t-complain-about-insecure-gues%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117030%2fhow-do-i-configure-samba-so-that-windows-10-doesn-t-complain-about-insecure-gues%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕