make samba share visible in Windows “Network”
tl;dr Shared files are accessible, but server isn't visible in Windows listing.
I've got printers and some directories shared via Samba, but they do not appear in the listing when a Windows user opens their "Network". They can type "computername" and hit enter to see the shared printers and directories, but I'd like to make it easy to see the server listed along with other icons in their Network panel.
This used to work (ubuntu 13-something, I think), but recently (ubuntu 15.04) it doesn't. So something must have changed with the default configuration. It's probably a simple setting in smb.conf, I just don't know where to look. Any hints?
windows samba
add a comment |
tl;dr Shared files are accessible, but server isn't visible in Windows listing.
I've got printers and some directories shared via Samba, but they do not appear in the listing when a Windows user opens their "Network". They can type "computername" and hit enter to see the shared printers and directories, but I'd like to make it easy to see the server listed along with other icons in their Network panel.
This used to work (ubuntu 13-something, I think), but recently (ubuntu 15.04) it doesn't. So something must have changed with the default configuration. It's probably a simple setting in smb.conf, I just don't know where to look. Any hints?
windows samba
add a comment |
tl;dr Shared files are accessible, but server isn't visible in Windows listing.
I've got printers and some directories shared via Samba, but they do not appear in the listing when a Windows user opens their "Network". They can type "computername" and hit enter to see the shared printers and directories, but I'd like to make it easy to see the server listed along with other icons in their Network panel.
This used to work (ubuntu 13-something, I think), but recently (ubuntu 15.04) it doesn't. So something must have changed with the default configuration. It's probably a simple setting in smb.conf, I just don't know where to look. Any hints?
windows samba
tl;dr Shared files are accessible, but server isn't visible in Windows listing.
I've got printers and some directories shared via Samba, but they do not appear in the listing when a Windows user opens their "Network". They can type "computername" and hit enter to see the shared printers and directories, but I'd like to make it easy to see the server listed along with other icons in their Network panel.
This used to work (ubuntu 13-something, I think), but recently (ubuntu 15.04) it doesn't. So something must have changed with the default configuration. It's probably a simple setting in smb.conf, I just don't know where to look. Any hints?
windows samba
windows samba
asked Aug 15 '15 at 0:18
Iestyn ap Mwg
1262311
1262311
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
I have been using OpenSuse Leap 42.2 and as windows updates is breaks my samba network. This configuration in the [Global] section of samba config has worked until billy's recent updates and stopped working on my Windows 7 and 10 machines. My global section of samba config was:
[global]
workgroup = WORKGROUP
netbios name = LINUXSERVER
lanman auth = no
ntlm auth = yes
client lanman auth = no
I then added the 3 lines found on this site so global now reads:
[global]
workgroup = WORKGROUP
netbios name = LINUXSERVER
lanman auth = no
ntlm auth = yes
client lanman auth = no
wins support = yes
local master = yes
preferred master = yes
Now my samba shares show up in Windows 7/10. I know this is a Ubuntu forum but I am always willing to try to help fellow Linux users.
add a comment |
add lines in smb.conf
wins support = yes
local master = yes
preferred master = yes
For some reason, none of this works for me with Win 10. I always have to manually add the path to the share, or use \myhostname.local
– Fiddy Bux
yesterday
add a comment |
I've been hammering away at this problem for a few weeks, on and off, and it is only now that I have found the last piece of the puzzle for Windows 10 to see Samba shares in Network (places).
It's all described fully at this link:
How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows and Windows Server
Essentially, you need to enable SMBv1 / CIFS sharing support in Windows 10:
Just hit START in Windows and search for 'Turn Windows features on or off' and it'll take you there.
After I did this, all my problems vanished. Tada!
I don't know if it has reduced the security of my network (probably has!), but if it has it doesn't matter to me too much as it's all on LAN anyway.
Hope this helps some other people out.
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
});
}
});
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%2f661611%2fmake-samba-share-visible-in-windows-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have been using OpenSuse Leap 42.2 and as windows updates is breaks my samba network. This configuration in the [Global] section of samba config has worked until billy's recent updates and stopped working on my Windows 7 and 10 machines. My global section of samba config was:
[global]
workgroup = WORKGROUP
netbios name = LINUXSERVER
lanman auth = no
ntlm auth = yes
client lanman auth = no
I then added the 3 lines found on this site so global now reads:
[global]
workgroup = WORKGROUP
netbios name = LINUXSERVER
lanman auth = no
ntlm auth = yes
client lanman auth = no
wins support = yes
local master = yes
preferred master = yes
Now my samba shares show up in Windows 7/10. I know this is a Ubuntu forum but I am always willing to try to help fellow Linux users.
add a comment |
I have been using OpenSuse Leap 42.2 and as windows updates is breaks my samba network. This configuration in the [Global] section of samba config has worked until billy's recent updates and stopped working on my Windows 7 and 10 machines. My global section of samba config was:
[global]
workgroup = WORKGROUP
netbios name = LINUXSERVER
lanman auth = no
ntlm auth = yes
client lanman auth = no
I then added the 3 lines found on this site so global now reads:
[global]
workgroup = WORKGROUP
netbios name = LINUXSERVER
lanman auth = no
ntlm auth = yes
client lanman auth = no
wins support = yes
local master = yes
preferred master = yes
Now my samba shares show up in Windows 7/10. I know this is a Ubuntu forum but I am always willing to try to help fellow Linux users.
add a comment |
I have been using OpenSuse Leap 42.2 and as windows updates is breaks my samba network. This configuration in the [Global] section of samba config has worked until billy's recent updates and stopped working on my Windows 7 and 10 machines. My global section of samba config was:
[global]
workgroup = WORKGROUP
netbios name = LINUXSERVER
lanman auth = no
ntlm auth = yes
client lanman auth = no
I then added the 3 lines found on this site so global now reads:
[global]
workgroup = WORKGROUP
netbios name = LINUXSERVER
lanman auth = no
ntlm auth = yes
client lanman auth = no
wins support = yes
local master = yes
preferred master = yes
Now my samba shares show up in Windows 7/10. I know this is a Ubuntu forum but I am always willing to try to help fellow Linux users.
I have been using OpenSuse Leap 42.2 and as windows updates is breaks my samba network. This configuration in the [Global] section of samba config has worked until billy's recent updates and stopped working on my Windows 7 and 10 machines. My global section of samba config was:
[global]
workgroup = WORKGROUP
netbios name = LINUXSERVER
lanman auth = no
ntlm auth = yes
client lanman auth = no
I then added the 3 lines found on this site so global now reads:
[global]
workgroup = WORKGROUP
netbios name = LINUXSERVER
lanman auth = no
ntlm auth = yes
client lanman auth = no
wins support = yes
local master = yes
preferred master = yes
Now my samba shares show up in Windows 7/10. I know this is a Ubuntu forum but I am always willing to try to help fellow Linux users.
edited Nov 30 '17 at 6:51
karel
56.8k11126146
56.8k11126146
answered Nov 30 '17 at 2:15
John Poster
213
213
add a comment |
add a comment |
add lines in smb.conf
wins support = yes
local master = yes
preferred master = yes
For some reason, none of this works for me with Win 10. I always have to manually add the path to the share, or use \myhostname.local
– Fiddy Bux
yesterday
add a comment |
add lines in smb.conf
wins support = yes
local master = yes
preferred master = yes
For some reason, none of this works for me with Win 10. I always have to manually add the path to the share, or use \myhostname.local
– Fiddy Bux
yesterday
add a comment |
add lines in smb.conf
wins support = yes
local master = yes
preferred master = yes
add lines in smb.conf
wins support = yes
local master = yes
preferred master = yes
answered Aug 16 '15 at 3:30
pl_rock
7,09742834
7,09742834
For some reason, none of this works for me with Win 10. I always have to manually add the path to the share, or use \myhostname.local
– Fiddy Bux
yesterday
add a comment |
For some reason, none of this works for me with Win 10. I always have to manually add the path to the share, or use \myhostname.local
– Fiddy Bux
yesterday
For some reason, none of this works for me with Win 10. I always have to manually add the path to the share, or use \myhostname.local
– Fiddy Bux
yesterday
For some reason, none of this works for me with Win 10. I always have to manually add the path to the share, or use \myhostname.local
– Fiddy Bux
yesterday
add a comment |
I've been hammering away at this problem for a few weeks, on and off, and it is only now that I have found the last piece of the puzzle for Windows 10 to see Samba shares in Network (places).
It's all described fully at this link:
How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows and Windows Server
Essentially, you need to enable SMBv1 / CIFS sharing support in Windows 10:
Just hit START in Windows and search for 'Turn Windows features on or off' and it'll take you there.
After I did this, all my problems vanished. Tada!
I don't know if it has reduced the security of my network (probably has!), but if it has it doesn't matter to me too much as it's all on LAN anyway.
Hope this helps some other people out.
add a comment |
I've been hammering away at this problem for a few weeks, on and off, and it is only now that I have found the last piece of the puzzle for Windows 10 to see Samba shares in Network (places).
It's all described fully at this link:
How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows and Windows Server
Essentially, you need to enable SMBv1 / CIFS sharing support in Windows 10:
Just hit START in Windows and search for 'Turn Windows features on or off' and it'll take you there.
After I did this, all my problems vanished. Tada!
I don't know if it has reduced the security of my network (probably has!), but if it has it doesn't matter to me too much as it's all on LAN anyway.
Hope this helps some other people out.
add a comment |
I've been hammering away at this problem for a few weeks, on and off, and it is only now that I have found the last piece of the puzzle for Windows 10 to see Samba shares in Network (places).
It's all described fully at this link:
How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows and Windows Server
Essentially, you need to enable SMBv1 / CIFS sharing support in Windows 10:
Just hit START in Windows and search for 'Turn Windows features on or off' and it'll take you there.
After I did this, all my problems vanished. Tada!
I don't know if it has reduced the security of my network (probably has!), but if it has it doesn't matter to me too much as it's all on LAN anyway.
Hope this helps some other people out.
I've been hammering away at this problem for a few weeks, on and off, and it is only now that I have found the last piece of the puzzle for Windows 10 to see Samba shares in Network (places).
It's all described fully at this link:
How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows and Windows Server
Essentially, you need to enable SMBv1 / CIFS sharing support in Windows 10:
Just hit START in Windows and search for 'Turn Windows features on or off' and it'll take you there.
After I did this, all my problems vanished. Tada!
I don't know if it has reduced the security of my network (probably has!), but if it has it doesn't matter to me too much as it's all on LAN anyway.
Hope this helps some other people out.
answered 20 hours ago
Fiddy Bux
1114
1114
add a comment |
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f661611%2fmake-samba-share-visible-in-windows-network%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