Nautilus sees duplicate shares in 18.04
up vote
0
down vote
favorite
Nautilus is displaying 2 icons/items for some, but not all systems on the network. Here is how I got where I am.
The original problem was Nautilus would display only the two NAS devices on the network in the "Network Servers" windows and nothing in the "Windows Networks" window. This resulted in one RaspberryPI (running openhab) and a few Windows systems not being displayed in Nautilus. The Windows systems could display all devices on the network in the Windows network window. The 18.04 system could ping all systems on the network by name as well as IP address.
This particular 18.04 workstation system was a clean install, not an upgrade. I have another system running identical hardware (other than drives) that was an upgrade from 16.04 which does not have this issue.
This is what I've done to try and resolve this problem:
- Installed Samba not the samba client initially just Samba. I'm not sure what the difference is between the two.
- Compared the smb.conf of the working system with the non-working system - they are the same.
- Then I found and followed the suggestions in "Nautilus fails to see shares in 18.04". That corrected the problem of not seeing everything on the network.
"Nautilus fails to see shares in 18.04" - Introduced the following issues:
- Duplicate entries in the Network servers window.
- Every network device shows up in the root of then "Network Servers" window when only Linux type shares should be displayed (I think).
- Only Windows based systems are displayed in the Windows networks window, which I think is correct but they are also displayed in the root of the "Network Servers" windows.
Any suggestions would be great. Thanks.
networking nautilus samba
asked Nov 30 at 18:39
TroyT
1
add a comment |
up vote
0
down vote
favorite
Nautilus is displaying 2 icons/items for some, but not all systems on the network. Here is how I got where I am.
The original problem was Nautilus would display only the two NAS devices on the network in the "Network Servers" windows and nothing in the "Windows Networks" window. This resulted in one RaspberryPI (running openhab) and a few Windows systems not being displayed in Nautilus. The Windows systems could display all devices on the network in the Windows network window. The 18.04 system could ping all systems on the network by name as well as IP address.
This particular 18.04 workstation system was a clean install, not an upgrade. I have another system running identical hardware (other than drives) that was an upgrade from 16.04 which does not have this issue.
This is what I've done to try and resolve this problem:
- Installed Samba not the samba client initially just Samba. I'm not sure what the difference is between the two.
- Compared the smb.conf of the working system with the non-working system - they are the same.
- Then I found and followed the suggestions in "Nautilus fails to see shares in 18.04". That corrected the problem of not seeing everything on the network.
"Nautilus fails to see shares in 18.04" - Introduced the following issues:
- Duplicate entries in the Network servers window.
- Every network device shows up in the root of then "Network Servers" window when only Linux type shares should be displayed (I think).
- Only Windows based systems are displayed in the Windows networks window, which I think is correct but they are also displayed in the root of the "Network Servers" windows.
Any suggestions would be great. Thanks.
networking nautilus samba
asked Nov 30 at 18:39
TroyT
1
3
Possible duplicate of Nautilus fails to see shares in 18.04
– karel
Dec 1 at 4:33
1
It is not a duplicate of the answer presented in the linked to question. It is the result of using it as I explained in my answer below.
– Morbius1
Dec 1 at 12:35
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Nautilus is displaying 2 icons/items for some, but not all systems on the network. Here is how I got where I am.
The original problem was Nautilus would display only the two NAS devices on the network in the "Network Servers" windows and nothing in the "Windows Networks" window. This resulted in one RaspberryPI (running openhab) and a few Windows systems not being displayed in Nautilus. The Windows systems could display all devices on the network in the Windows network window. The 18.04 system could ping all systems on the network by name as well as IP address.
This particular 18.04 workstation system was a clean install, not an upgrade. I have another system running identical hardware (other than drives) that was an upgrade from 16.04 which does not have this issue.
This is what I've done to try and resolve this problem:
- Installed Samba not the samba client initially just Samba. I'm not sure what the difference is between the two.
- Compared the smb.conf of the working system with the non-working system - they are the same.
- Then I found and followed the suggestions in "Nautilus fails to see shares in 18.04". That corrected the problem of not seeing everything on the network.
"Nautilus fails to see shares in 18.04" - Introduced the following issues:
- Duplicate entries in the Network servers window.
- Every network device shows up in the root of then "Network Servers" window when only Linux type shares should be displayed (I think).
- Only Windows based systems are displayed in the Windows networks window, which I think is correct but they are also displayed in the root of the "Network Servers" windows.
Any suggestions would be great. Thanks.
networking nautilus samba
asked Nov 30 at 18:39
TroyT
1
Nautilus is displaying 2 icons/items for some, but not all systems on the network. Here is how I got where I am.
The original problem was Nautilus would display only the two NAS devices on the network in the "Network Servers" windows and nothing in the "Windows Networks" window. This resulted in one RaspberryPI (running openhab) and a few Windows systems not being displayed in Nautilus. The Windows systems could display all devices on the network in the Windows network window. The 18.04 system could ping all systems on the network by name as well as IP address.
This particular 18.04 workstation system was a clean install, not an upgrade. I have another system running identical hardware (other than drives) that was an upgrade from 16.04 which does not have this issue.
This is what I've done to try and resolve this problem:
- Installed Samba not the samba client initially just Samba. I'm not sure what the difference is between the two.
- Compared the smb.conf of the working system with the non-working system - they are the same.
- Then I found and followed the suggestions in "Nautilus fails to see shares in 18.04". That corrected the problem of not seeing everything on the network.
"Nautilus fails to see shares in 18.04" - Introduced the following issues:
- Duplicate entries in the Network servers window.
- Every network device shows up in the root of then "Network Servers" window when only Linux type shares should be displayed (I think).
- Only Windows based systems are displayed in the Windows networks window, which I think is correct but they are also displayed in the root of the "Network Servers" windows.
Any suggestions would be great. Thanks.
networking nautilus samba
networking nautilus samba
asked Nov 30 at 18:39
TroyT
1
asked Nov 30 at 18:39
TroyT
1
asked Nov 30 at 18:39
TroyT
1
asked Nov 30 at 18:39
TroyT
1
asked Nov 30 at 18:39
TroyT
1
1
3
Possible duplicate of Nautilus fails to see shares in 18.04
– karel
Dec 1 at 4:33
1
It is not a duplicate of the answer presented in the linked to question. It is the result of using it as I explained in my answer below.
– Morbius1
Dec 1 at 12:35
add a comment |
3
Possible duplicate of Nautilus fails to see shares in 18.04
– karel
Dec 1 at 4:33
1
It is not a duplicate of the answer presented in the linked to question. It is the result of using it as I explained in my answer below.
– Morbius1
Dec 1 at 12:35
3
3
Possible duplicate of Nautilus fails to see shares in 18.04
– karel
Dec 1 at 4:33
Possible duplicate of Nautilus fails to see shares in 18.04
– karel
Dec 1 at 4:33
1
1
It is not a duplicate of the answer presented in the linked to question. It is the result of using it as I explained in my answer below.
– Morbius1
Dec 1 at 12:35
It is not a duplicate of the answer presented in the linked to question. It is the result of using it as I explained in my answer below.
– Morbius1
Dec 1 at 12:35
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Given the types of hosts you have in your network there isn't a real good answer to your dilemma.
There are two ways a Linux smb client can "discover" hosts on the network.
The old netbios way which in 18.04 is pretty much broken and can only be fixed if you add "client max protocol = NT1" to smb.conf.
The modern mDNS way which works for Linux, macOS, and any device designed to work with them.
A server ( like Ubuntu 18.04 ) can and does broadcast itself to the rest of the network using both methods except for Windows since it doesn't use mDNS for this purpose.
A Linux client can discover both which is why you see duplicates for those machines that brodcast using both methods. One of them will resolve to a-host-name ( netbios ) and one to a-host-name.local ( mDNS ). Any host that uses mDNS will show outside the "Windows Network" label because they aren't using netbios.
But, a further complication is that often used servers using netbios can show up outside the "Windows Network" because they have already been resolved and remembered.
EDIT: I offer here a possible way around this issue which might work for you: Don't browse for these hosts / devices. Bookmark them instead.
Browse to the server in Nautilus as you normally do but when the list of shares available shows up for that server bookmark it: Click on the "hamburger" icon in Nautilus and select the "Bookmark this Location" icon.
That will create a link on the side panel labeled "Windows shares on xxx". You can rename that if you want by right clicking the link.
Then when you want to access a network resource you select the bookmark instead of going through Network / Windows Network.
answered Nov 30 at 22:58
Morbius1
1,256127
I edited my original answer to provide a possible option that might work for you
– Morbius1
Dec 1 at 13:56
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',
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%2f1097488%2fnautilus-sees-duplicate-shares-in-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Given the types of hosts you have in your network there isn't a real good answer to your dilemma.
There are two ways a Linux smb client can "discover" hosts on the network.
The old netbios way which in 18.04 is pretty much broken and can only be fixed if you add "client max protocol = NT1" to smb.conf.
The modern mDNS way which works for Linux, macOS, and any device designed to work with them.
A server ( like Ubuntu 18.04 ) can and does broadcast itself to the rest of the network using both methods except for Windows since it doesn't use mDNS for this purpose.
A Linux client can discover both which is why you see duplicates for those machines that brodcast using both methods. One of them will resolve to a-host-name ( netbios ) and one to a-host-name.local ( mDNS ). Any host that uses mDNS will show outside the "Windows Network" label because they aren't using netbios.
But, a further complication is that often used servers using netbios can show up outside the "Windows Network" because they have already been resolved and remembered.
EDIT: I offer here a possible way around this issue which might work for you: Don't browse for these hosts / devices. Bookmark them instead.
Browse to the server in Nautilus as you normally do but when the list of shares available shows up for that server bookmark it: Click on the "hamburger" icon in Nautilus and select the "Bookmark this Location" icon.
That will create a link on the side panel labeled "Windows shares on xxx". You can rename that if you want by right clicking the link.
Then when you want to access a network resource you select the bookmark instead of going through Network / Windows Network.
answered Nov 30 at 22:58
Morbius1
1,256127
I edited my original answer to provide a possible option that might work for you
– Morbius1
Dec 1 at 13:56
add a comment |
up vote
0
down vote
Given the types of hosts you have in your network there isn't a real good answer to your dilemma.
There are two ways a Linux smb client can "discover" hosts on the network.
The old netbios way which in 18.04 is pretty much broken and can only be fixed if you add "client max protocol = NT1" to smb.conf.
The modern mDNS way which works for Linux, macOS, and any device designed to work with them.
A server ( like Ubuntu 18.04 ) can and does broadcast itself to the rest of the network using both methods except for Windows since it doesn't use mDNS for this purpose.
A Linux client can discover both which is why you see duplicates for those machines that brodcast using both methods. One of them will resolve to a-host-name ( netbios ) and one to a-host-name.local ( mDNS ). Any host that uses mDNS will show outside the "Windows Network" label because they aren't using netbios.
But, a further complication is that often used servers using netbios can show up outside the "Windows Network" because they have already been resolved and remembered.
EDIT: I offer here a possible way around this issue which might work for you: Don't browse for these hosts / devices. Bookmark them instead.
Browse to the server in Nautilus as you normally do but when the list of shares available shows up for that server bookmark it: Click on the "hamburger" icon in Nautilus and select the "Bookmark this Location" icon.
That will create a link on the side panel labeled "Windows shares on xxx". You can rename that if you want by right clicking the link.
Then when you want to access a network resource you select the bookmark instead of going through Network / Windows Network.
answered Nov 30 at 22:58
Morbius1
1,256127
I edited my original answer to provide a possible option that might work for you
– Morbius1
Dec 1 at 13:56
add a comment |
up vote
0
down vote
up vote
0
down vote
Given the types of hosts you have in your network there isn't a real good answer to your dilemma.
There are two ways a Linux smb client can "discover" hosts on the network.
The old netbios way which in 18.04 is pretty much broken and can only be fixed if you add "client max protocol = NT1" to smb.conf.
The modern mDNS way which works for Linux, macOS, and any device designed to work with them.
A server ( like Ubuntu 18.04 ) can and does broadcast itself to the rest of the network using both methods except for Windows since it doesn't use mDNS for this purpose.
A Linux client can discover both which is why you see duplicates for those machines that brodcast using both methods. One of them will resolve to a-host-name ( netbios ) and one to a-host-name.local ( mDNS ). Any host that uses mDNS will show outside the "Windows Network" label because they aren't using netbios.
But, a further complication is that often used servers using netbios can show up outside the "Windows Network" because they have already been resolved and remembered.
EDIT: I offer here a possible way around this issue which might work for you: Don't browse for these hosts / devices. Bookmark them instead.
Browse to the server in Nautilus as you normally do but when the list of shares available shows up for that server bookmark it: Click on the "hamburger" icon in Nautilus and select the "Bookmark this Location" icon.
That will create a link on the side panel labeled "Windows shares on xxx". You can rename that if you want by right clicking the link.
Then when you want to access a network resource you select the bookmark instead of going through Network / Windows Network.
answered Nov 30 at 22:58
Morbius1
1,256127
Given the types of hosts you have in your network there isn't a real good answer to your dilemma.
There are two ways a Linux smb client can "discover" hosts on the network.
The old netbios way which in 18.04 is pretty much broken and can only be fixed if you add "client max protocol = NT1" to smb.conf.
The modern mDNS way which works for Linux, macOS, and any device designed to work with them.
A server ( like Ubuntu 18.04 ) can and does broadcast itself to the rest of the network using both methods except for Windows since it doesn't use mDNS for this purpose.
A Linux client can discover both which is why you see duplicates for those machines that brodcast using both methods. One of them will resolve to a-host-name ( netbios ) and one to a-host-name.local ( mDNS ). Any host that uses mDNS will show outside the "Windows Network" label because they aren't using netbios.
But, a further complication is that often used servers using netbios can show up outside the "Windows Network" because they have already been resolved and remembered.
EDIT: I offer here a possible way around this issue which might work for you: Don't browse for these hosts / devices. Bookmark them instead.
Browse to the server in Nautilus as you normally do but when the list of shares available shows up for that server bookmark it: Click on the "hamburger" icon in Nautilus and select the "Bookmark this Location" icon.
That will create a link on the side panel labeled "Windows shares on xxx". You can rename that if you want by right clicking the link.
Then when you want to access a network resource you select the bookmark instead of going through Network / Windows Network.
answered Nov 30 at 22:58
Morbius1
1,256127
edited Dec 1 at 13:55
answered Nov 30 at 22:58
Morbius1
1,256127
answered Nov 30 at 22:58
Morbius1
1,256127
answered Nov 30 at 22:58
Morbius1
1,256127
1,256127
I edited my original answer to provide a possible option that might work for you
– Morbius1
Dec 1 at 13:56
add a comment |
I edited my original answer to provide a possible option that might work for you
– Morbius1
Dec 1 at 13:56
I edited my original answer to provide a possible option that might work for you
– Morbius1
Dec 1 at 13:56
I edited my original answer to provide a possible option that might work for you
– Morbius1
Dec 1 at 13:56
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%2f1097488%2fnautilus-sees-duplicate-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
3
Possible duplicate of Nautilus fails to see shares in 18.04
– karel
Dec 1 at 4:33
1
It is not a duplicate of the answer presented in the linked to question. It is the result of using it as I explained in my answer below.
– Morbius1
Dec 1 at 12:35