Nautilus fails to see shares in 18.04
After upgrading non-essential PCs to 18.04, while keeping my primary PC on 17.10, I'm running into a minor problem with networking and Nautilus in 18.04.
When I select Other Locations in the Nautilus sidebar, I expect to see the other machines on my network plus my Windows network. They are all there on machines running 17.10, but don't appear in 18.04. Also in 18.04 although there is an icon for the Windows network, clicking on it doesn't bring up the existing Workgroups as it does in 17.10.
My /etc/samba/smb.conf files are identical on all machines. I can access the shares from the 18.04 machines by running:
nautilus smb://<ip address>
in a terminal, which is why I suspect it has something to do with Nautilus rather than Samba. The Nautilus version on the 17.10 machines is 3.26.0, on the 18.04 machines is 3.26.3.
networking nautilus samba 18.04 connection-sharing
edited Jul 7 '18 at 0:31
slm
1,73611824
asked May 3 '18 at 17:08
Richard QuintRichard Quint
175212
add a comment |
After upgrading non-essential PCs to 18.04, while keeping my primary PC on 17.10, I'm running into a minor problem with networking and Nautilus in 18.04.
When I select Other Locations in the Nautilus sidebar, I expect to see the other machines on my network plus my Windows network. They are all there on machines running 17.10, but don't appear in 18.04. Also in 18.04 although there is an icon for the Windows network, clicking on it doesn't bring up the existing Workgroups as it does in 17.10.
My /etc/samba/smb.conf files are identical on all machines. I can access the shares from the 18.04 machines by running:
nautilus smb://<ip address>
in a terminal, which is why I suspect it has something to do with Nautilus rather than Samba. The Nautilus version on the 17.10 machines is 3.26.0, on the 18.04 machines is 3.26.3.
networking nautilus samba 18.04 connection-sharing
edited Jul 7 '18 at 0:31
slm
1,73611824
asked May 3 '18 at 17:08
Richard QuintRichard Quint
175212
add a comment |
After upgrading non-essential PCs to 18.04, while keeping my primary PC on 17.10, I'm running into a minor problem with networking and Nautilus in 18.04.
When I select Other Locations in the Nautilus sidebar, I expect to see the other machines on my network plus my Windows network. They are all there on machines running 17.10, but don't appear in 18.04. Also in 18.04 although there is an icon for the Windows network, clicking on it doesn't bring up the existing Workgroups as it does in 17.10.
My /etc/samba/smb.conf files are identical on all machines. I can access the shares from the 18.04 machines by running:
nautilus smb://<ip address>
in a terminal, which is why I suspect it has something to do with Nautilus rather than Samba. The Nautilus version on the 17.10 machines is 3.26.0, on the 18.04 machines is 3.26.3.
networking nautilus samba 18.04 connection-sharing
edited Jul 7 '18 at 0:31
slm
1,73611824
asked May 3 '18 at 17:08
Richard QuintRichard Quint
175212
After upgrading non-essential PCs to 18.04, while keeping my primary PC on 17.10, I'm running into a minor problem with networking and Nautilus in 18.04.
When I select Other Locations in the Nautilus sidebar, I expect to see the other machines on my network plus my Windows network. They are all there on machines running 17.10, but don't appear in 18.04. Also in 18.04 although there is an icon for the Windows network, clicking on it doesn't bring up the existing Workgroups as it does in 17.10.
My /etc/samba/smb.conf files are identical on all machines. I can access the shares from the 18.04 machines by running:
nautilus smb://<ip address>
in a terminal, which is why I suspect it has something to do with Nautilus rather than Samba. The Nautilus version on the 17.10 machines is 3.26.0, on the 18.04 machines is 3.26.3.
networking nautilus samba 18.04 connection-sharing
networking nautilus samba 18.04 connection-sharing
edited Jul 7 '18 at 0:31
slm
1,73611824
asked May 3 '18 at 17:08
Richard QuintRichard Quint
175212
edited Jul 7 '18 at 0:31
slm
1,73611824
asked May 3 '18 at 17:08
Richard QuintRichard Quint
175212
edited Jul 7 '18 at 0:31
slm
1,73611824
edited Jul 7 '18 at 0:31
slm
1,73611824
edited Jul 7 '18 at 0:31
slm
1,73611824
1,73611824
asked May 3 '18 at 17:08
Richard QuintRichard Quint
175212
asked May 3 '18 at 17:08
Richard QuintRichard Quint
175212
asked May 3 '18 at 17:08
Richard QuintRichard Quint
175212
175212
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
There's two different issues in your description.
The "Windows Network" problem is due to samba changing a client protocol level: https://ubuntuforums.org/showthread.php?t=2384959
To restore it to how it used to work:
Install smbclient:
sudo apt install smbclient
Then edit /etc/samba/smb.conf and add a line under the workgroup = WORKGROUP line:
client max protocol = NT1
Save the file and reboot ... yes ... reboot.
Please read the forum post about why Samba changed this to see if it affects you.
The other issue about not finding 17.10 samba servers seems odd because starting with that release they should be "published" automatically regardless of protocol level. I would see if the following service is running on all your machines:
sudo service avahi-daemon status
If it's not running restart it:
sudo service avahi-demon start
Changing the client max to NT1 should also fix the Ubuntu 17.10 discovery but the avahi method really should be working by default.
answered May 3 '18 at 19:46
Morbius1Morbius1
1,376127
The first part of the answer solved my problem, the avahi-daemon was already running.
– Richard Quint
May 3 '18 at 20:54
client max protocol = SMB2 also worked for me. SMB3 not.
– s.k
Dec 13 '18 at 13:19
client max protocol = NT1- thank you, thank you! Been trawling for the answer to this for days. Although now I have two local shares showing for this machine, bothsmb://xubuntu.localandsmb://xubuntu. I can live with this though. Going to now see if the same works on my Debian box.
– Fiddy Bux
Jan 7 at 21:56
add a comment |
I had to disable ufw firewall to make windows network browsing work. Have not figured out what rules to make it work with firewall on.
Status: active
To Action From
-- ------ ----
137,138/udp ALLOW Anywhere
139,445/tcp ALLOW Anywhere
Apache Full ALLOW Anywhere
Samba ALLOW Anywhere
Samba (v6) ALLOW Anywhere (v6)
22/tcp ALLOW OUT Anywhere
edited 5 hours ago
tinlyx
78221023
answered 9 hours ago
hikerbkhikerbk
12
New contributor
hikerbk 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 |
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%2f1031643%2fnautilus-fails-to-see-shares-in-18-04%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
There's two different issues in your description.
The "Windows Network" problem is due to samba changing a client protocol level: https://ubuntuforums.org/showthread.php?t=2384959
To restore it to how it used to work:
Install smbclient:
sudo apt install smbclient
Then edit /etc/samba/smb.conf and add a line under the workgroup = WORKGROUP line:
client max protocol = NT1
Save the file and reboot ... yes ... reboot.
Please read the forum post about why Samba changed this to see if it affects you.
The other issue about not finding 17.10 samba servers seems odd because starting with that release they should be "published" automatically regardless of protocol level. I would see if the following service is running on all your machines:
sudo service avahi-daemon status
If it's not running restart it:
sudo service avahi-demon start
Changing the client max to NT1 should also fix the Ubuntu 17.10 discovery but the avahi method really should be working by default.
answered May 3 '18 at 19:46
Morbius1Morbius1
1,376127
The first part of the answer solved my problem, the avahi-daemon was already running.
– Richard Quint
May 3 '18 at 20:54
client max protocol = SMB2 also worked for me. SMB3 not.
– s.k
Dec 13 '18 at 13:19
client max protocol = NT1- thank you, thank you! Been trawling for the answer to this for days. Although now I have two local shares showing for this machine, bothsmb://xubuntu.localandsmb://xubuntu. I can live with this though. Going to now see if the same works on my Debian box.
– Fiddy Bux
Jan 7 at 21:56
add a comment |
There's two different issues in your description.
The "Windows Network" problem is due to samba changing a client protocol level: https://ubuntuforums.org/showthread.php?t=2384959
To restore it to how it used to work:
Install smbclient:
sudo apt install smbclient
Then edit /etc/samba/smb.conf and add a line under the workgroup = WORKGROUP line:
client max protocol = NT1
Save the file and reboot ... yes ... reboot.
Please read the forum post about why Samba changed this to see if it affects you.
The other issue about not finding 17.10 samba servers seems odd because starting with that release they should be "published" automatically regardless of protocol level. I would see if the following service is running on all your machines:
sudo service avahi-daemon status
If it's not running restart it:
sudo service avahi-demon start
Changing the client max to NT1 should also fix the Ubuntu 17.10 discovery but the avahi method really should be working by default.
answered May 3 '18 at 19:46
Morbius1Morbius1
1,376127
The first part of the answer solved my problem, the avahi-daemon was already running.
– Richard Quint
May 3 '18 at 20:54
client max protocol = SMB2 also worked for me. SMB3 not.
– s.k
Dec 13 '18 at 13:19
client max protocol = NT1- thank you, thank you! Been trawling for the answer to this for days. Although now I have two local shares showing for this machine, bothsmb://xubuntu.localandsmb://xubuntu. I can live with this though. Going to now see if the same works on my Debian box.
– Fiddy Bux
Jan 7 at 21:56
add a comment |
There's two different issues in your description.
The "Windows Network" problem is due to samba changing a client protocol level: https://ubuntuforums.org/showthread.php?t=2384959
To restore it to how it used to work:
Install smbclient:
sudo apt install smbclient
Then edit /etc/samba/smb.conf and add a line under the workgroup = WORKGROUP line:
client max protocol = NT1
Save the file and reboot ... yes ... reboot.
Please read the forum post about why Samba changed this to see if it affects you.
The other issue about not finding 17.10 samba servers seems odd because starting with that release they should be "published" automatically regardless of protocol level. I would see if the following service is running on all your machines:
sudo service avahi-daemon status
If it's not running restart it:
sudo service avahi-demon start
Changing the client max to NT1 should also fix the Ubuntu 17.10 discovery but the avahi method really should be working by default.
answered May 3 '18 at 19:46
Morbius1Morbius1
1,376127
There's two different issues in your description.
The "Windows Network" problem is due to samba changing a client protocol level: https://ubuntuforums.org/showthread.php?t=2384959
To restore it to how it used to work:
Install smbclient:
sudo apt install smbclient
Then edit /etc/samba/smb.conf and add a line under the workgroup = WORKGROUP line:
client max protocol = NT1
Save the file and reboot ... yes ... reboot.
Please read the forum post about why Samba changed this to see if it affects you.
The other issue about not finding 17.10 samba servers seems odd because starting with that release they should be "published" automatically regardless of protocol level. I would see if the following service is running on all your machines:
sudo service avahi-daemon status
If it's not running restart it:
sudo service avahi-demon start
Changing the client max to NT1 should also fix the Ubuntu 17.10 discovery but the avahi method really should be working by default.
answered May 3 '18 at 19:46
Morbius1Morbius1
1,376127
answered May 3 '18 at 19:46
Morbius1Morbius1
1,376127
answered May 3 '18 at 19:46
Morbius1Morbius1
1,376127
answered May 3 '18 at 19:46
Morbius1Morbius1
1,376127
1,376127
The first part of the answer solved my problem, the avahi-daemon was already running.
– Richard Quint
May 3 '18 at 20:54
client max protocol = SMB2 also worked for me. SMB3 not.
– s.k
Dec 13 '18 at 13:19
client max protocol = NT1- thank you, thank you! Been trawling for the answer to this for days. Although now I have two local shares showing for this machine, bothsmb://xubuntu.localandsmb://xubuntu. I can live with this though. Going to now see if the same works on my Debian box.
– Fiddy Bux
Jan 7 at 21:56
add a comment |
The first part of the answer solved my problem, the avahi-daemon was already running.
– Richard Quint
May 3 '18 at 20:54
client max protocol = SMB2 also worked for me. SMB3 not.
– s.k
Dec 13 '18 at 13:19
client max protocol = NT1- thank you, thank you! Been trawling for the answer to this for days. Although now I have two local shares showing for this machine, bothsmb://xubuntu.localandsmb://xubuntu. I can live with this though. Going to now see if the same works on my Debian box.
– Fiddy Bux
Jan 7 at 21:56
The first part of the answer solved my problem, the avahi-daemon was already running.
– Richard Quint
May 3 '18 at 20:54
The first part of the answer solved my problem, the avahi-daemon was already running.
– Richard Quint
May 3 '18 at 20:54
client max protocol = SMB2 also worked for me. SMB3 not.
– s.k
Dec 13 '18 at 13:19
client max protocol = SMB2 also worked for me. SMB3 not.
– s.k
Dec 13 '18 at 13:19
client max protocol = NT1 - thank you, thank you! Been trawling for the answer to this for days. Although now I have two local shares showing for this machine, both smb://xubuntu.local and smb://xubuntu. I can live with this though. Going to now see if the same works on my Debian box.– Fiddy Bux
Jan 7 at 21:56
client max protocol = NT1 - thank you, thank you! Been trawling for the answer to this for days. Although now I have two local shares showing for this machine, both smb://xubuntu.local and smb://xubuntu. I can live with this though. Going to now see if the same works on my Debian box.– Fiddy Bux
Jan 7 at 21:56
add a comment |
I had to disable ufw firewall to make windows network browsing work. Have not figured out what rules to make it work with firewall on.
Status: active
To Action From
-- ------ ----
137,138/udp ALLOW Anywhere
139,445/tcp ALLOW Anywhere
Apache Full ALLOW Anywhere
Samba ALLOW Anywhere
Samba (v6) ALLOW Anywhere (v6)
22/tcp ALLOW OUT Anywhere
edited 5 hours ago
tinlyx
78221023
answered 9 hours ago
hikerbkhikerbk
12
New contributor
hikerbk 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 had to disable ufw firewall to make windows network browsing work. Have not figured out what rules to make it work with firewall on.
Status: active
To Action From
-- ------ ----
137,138/udp ALLOW Anywhere
139,445/tcp ALLOW Anywhere
Apache Full ALLOW Anywhere
Samba ALLOW Anywhere
Samba (v6) ALLOW Anywhere (v6)
22/tcp ALLOW OUT Anywhere
edited 5 hours ago
tinlyx
78221023
answered 9 hours ago
hikerbkhikerbk
12
New contributor
hikerbk 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 had to disable ufw firewall to make windows network browsing work. Have not figured out what rules to make it work with firewall on.
Status: active
To Action From
-- ------ ----
137,138/udp ALLOW Anywhere
139,445/tcp ALLOW Anywhere
Apache Full ALLOW Anywhere
Samba ALLOW Anywhere
Samba (v6) ALLOW Anywhere (v6)
22/tcp ALLOW OUT Anywhere
edited 5 hours ago
tinlyx
78221023
answered 9 hours ago
hikerbkhikerbk
12
New contributor
hikerbk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I had to disable ufw firewall to make windows network browsing work. Have not figured out what rules to make it work with firewall on.
Status: active
To Action From
-- ------ ----
137,138/udp ALLOW Anywhere
139,445/tcp ALLOW Anywhere
Apache Full ALLOW Anywhere
Samba ALLOW Anywhere
Samba (v6) ALLOW Anywhere (v6)
22/tcp ALLOW OUT Anywhere
edited 5 hours ago
tinlyx
78221023
answered 9 hours ago
hikerbkhikerbk
12
New contributor
hikerbk 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
tinlyx
78221023
edited 5 hours ago
tinlyx
78221023
edited 5 hours ago
tinlyx
78221023
78221023
answered 9 hours ago
hikerbkhikerbk
12
New contributor
hikerbk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 9 hours ago
hikerbkhikerbk
12
answered 9 hours ago
hikerbkhikerbk
12
12
New contributor
hikerbk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
hikerbk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
hikerbk 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 |
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.
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%2f1031643%2fnautilus-fails-to-see-shares-in-18-04%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
