Samba share can only be accessed with smbclient but not Explorer from Windows 10?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












0















I've set up a Samba server on Linux (Ubuntu 17.04) to share files with my Windows computer.



The server is up and running, but what's strange is that I can only access the shared folder using the smbclient command from my Windows Subsystem for Linux environment:



smbclient //xxx.xxx.xx.xx/share 


However, when I use the Windows command line tools for Samba (which is the same as adding a drive map from Explorer):



net use \xxx.xxx.xx.xxshare Z: 


After putting the same username/password as with the smbclient, I get an error message:



System error 5 has occurred. 
Access is denied.


Nearly everything from my smb.conf is by default, and the only configurations I added were:



hosts allow = xxx.xx.xx.xx/24 127.0.0.1 


and



[share] 
path = /my/share/folder
valid users = my_user
read only = no
writable = yes
browsable = yes
guest ok = no


(I also have used smbpasswd to set up the username and enabled samba in ufw )










share|improve this question
























  • Please can you provide all the non-comment lines from your smb.conf. (Different distributions seem to provide a different default file.)

    – roaima
    Feb 14 at 20:53











  • in smb.conf under the [global] section try adding max protocol = SMB2

    – ron
    Feb 14 at 22:21











  • win10 disables SMB1 protocol by default, and your linux samba might be defaulting to SMB1.

    – ron
    Feb 14 at 22:22











  • What do the (relevant) log files under /var/log/samba say?

    – roaima
    Feb 14 at 23:49











  • - I think you mean 'min protocol = SMB2'. I already tried it didn't work. - Log doesn't say anything rather than 'Denied access from IP xxx.xxx.xx.xx'. Strange thing is that even for the smbclient access which did come thru it reports the same thing.

    – peidaqi
    Feb 15 at 21:44
















0















I've set up a Samba server on Linux (Ubuntu 17.04) to share files with my Windows computer.



The server is up and running, but what's strange is that I can only access the shared folder using the smbclient command from my Windows Subsystem for Linux environment:



smbclient //xxx.xxx.xx.xx/share 


However, when I use the Windows command line tools for Samba (which is the same as adding a drive map from Explorer):



net use \xxx.xxx.xx.xxshare Z: 


After putting the same username/password as with the smbclient, I get an error message:



System error 5 has occurred. 
Access is denied.


Nearly everything from my smb.conf is by default, and the only configurations I added were:



hosts allow = xxx.xx.xx.xx/24 127.0.0.1 


and



[share] 
path = /my/share/folder
valid users = my_user
read only = no
writable = yes
browsable = yes
guest ok = no


(I also have used smbpasswd to set up the username and enabled samba in ufw )










share|improve this question
























  • Please can you provide all the non-comment lines from your smb.conf. (Different distributions seem to provide a different default file.)

    – roaima
    Feb 14 at 20:53











  • in smb.conf under the [global] section try adding max protocol = SMB2

    – ron
    Feb 14 at 22:21











  • win10 disables SMB1 protocol by default, and your linux samba might be defaulting to SMB1.

    – ron
    Feb 14 at 22:22











  • What do the (relevant) log files under /var/log/samba say?

    – roaima
    Feb 14 at 23:49











  • - I think you mean 'min protocol = SMB2'. I already tried it didn't work. - Log doesn't say anything rather than 'Denied access from IP xxx.xxx.xx.xx'. Strange thing is that even for the smbclient access which did come thru it reports the same thing.

    – peidaqi
    Feb 15 at 21:44














0












0








0








I've set up a Samba server on Linux (Ubuntu 17.04) to share files with my Windows computer.



The server is up and running, but what's strange is that I can only access the shared folder using the smbclient command from my Windows Subsystem for Linux environment:



smbclient //xxx.xxx.xx.xx/share 


However, when I use the Windows command line tools for Samba (which is the same as adding a drive map from Explorer):



net use \xxx.xxx.xx.xxshare Z: 


After putting the same username/password as with the smbclient, I get an error message:



System error 5 has occurred. 
Access is denied.


Nearly everything from my smb.conf is by default, and the only configurations I added were:



hosts allow = xxx.xx.xx.xx/24 127.0.0.1 


and



[share] 
path = /my/share/folder
valid users = my_user
read only = no
writable = yes
browsable = yes
guest ok = no


(I also have used smbpasswd to set up the username and enabled samba in ufw )










share|improve this question
















I've set up a Samba server on Linux (Ubuntu 17.04) to share files with my Windows computer.



The server is up and running, but what's strange is that I can only access the shared folder using the smbclient command from my Windows Subsystem for Linux environment:



smbclient //xxx.xxx.xx.xx/share 


However, when I use the Windows command line tools for Samba (which is the same as adding a drive map from Explorer):



net use \xxx.xxx.xx.xxshare Z: 


After putting the same username/password as with the smbclient, I get an error message:



System error 5 has occurred. 
Access is denied.


Nearly everything from my smb.conf is by default, and the only configurations I added were:



hosts allow = xxx.xx.xx.xx/24 127.0.0.1 


and



[share] 
path = /my/share/folder
valid users = my_user
read only = no
writable = yes
browsable = yes
guest ok = no


(I also have used smbpasswd to set up the username and enabled samba in ufw )







samba samba4






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 14 at 23:44









roaima

45.5k757123




45.5k757123










asked Feb 14 at 19:35









peidaqipeidaqi

1184




1184












  • Please can you provide all the non-comment lines from your smb.conf. (Different distributions seem to provide a different default file.)

    – roaima
    Feb 14 at 20:53











  • in smb.conf under the [global] section try adding max protocol = SMB2

    – ron
    Feb 14 at 22:21











  • win10 disables SMB1 protocol by default, and your linux samba might be defaulting to SMB1.

    – ron
    Feb 14 at 22:22











  • What do the (relevant) log files under /var/log/samba say?

    – roaima
    Feb 14 at 23:49











  • - I think you mean 'min protocol = SMB2'. I already tried it didn't work. - Log doesn't say anything rather than 'Denied access from IP xxx.xxx.xx.xx'. Strange thing is that even for the smbclient access which did come thru it reports the same thing.

    – peidaqi
    Feb 15 at 21:44


















  • Please can you provide all the non-comment lines from your smb.conf. (Different distributions seem to provide a different default file.)

    – roaima
    Feb 14 at 20:53











  • in smb.conf under the [global] section try adding max protocol = SMB2

    – ron
    Feb 14 at 22:21











  • win10 disables SMB1 protocol by default, and your linux samba might be defaulting to SMB1.

    – ron
    Feb 14 at 22:22











  • What do the (relevant) log files under /var/log/samba say?

    – roaima
    Feb 14 at 23:49











  • - I think you mean 'min protocol = SMB2'. I already tried it didn't work. - Log doesn't say anything rather than 'Denied access from IP xxx.xxx.xx.xx'. Strange thing is that even for the smbclient access which did come thru it reports the same thing.

    – peidaqi
    Feb 15 at 21:44

















Please can you provide all the non-comment lines from your smb.conf. (Different distributions seem to provide a different default file.)

– roaima
Feb 14 at 20:53





Please can you provide all the non-comment lines from your smb.conf. (Different distributions seem to provide a different default file.)

– roaima
Feb 14 at 20:53













in smb.conf under the [global] section try adding max protocol = SMB2

– ron
Feb 14 at 22:21





in smb.conf under the [global] section try adding max protocol = SMB2

– ron
Feb 14 at 22:21













win10 disables SMB1 protocol by default, and your linux samba might be defaulting to SMB1.

– ron
Feb 14 at 22:22





win10 disables SMB1 protocol by default, and your linux samba might be defaulting to SMB1.

– ron
Feb 14 at 22:22













What do the (relevant) log files under /var/log/samba say?

– roaima
Feb 14 at 23:49





What do the (relevant) log files under /var/log/samba say?

– roaima
Feb 14 at 23:49













- I think you mean 'min protocol = SMB2'. I already tried it didn't work. - Log doesn't say anything rather than 'Denied access from IP xxx.xxx.xx.xx'. Strange thing is that even for the smbclient access which did come thru it reports the same thing.

– peidaqi
Feb 15 at 21:44






- I think you mean 'min protocol = SMB2'. I already tried it didn't work. - Log doesn't say anything rather than 'Denied access from IP xxx.xxx.xx.xx'. Strange thing is that even for the smbclient access which did come thru it reports the same thing.

– peidaqi
Feb 15 at 21:44











0






active

oldest

votes











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



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f500698%2fsamba-share-can-only-be-accessed-with-smbclient-but-not-explorer-from-windows-10%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 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.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f500698%2fsamba-share-can-only-be-accessed-with-smbclient-but-not-explorer-from-windows-10%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

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay