4 ms·

(2) Samba, or at least Ubuntu's version of it, is very flaky. Some days it would see my networked drives, other days it wouldn't. The SMB client on your Ubuntu

(2) Samba, or at least Ubuntu's version of it, is very flaky. Some days it would see my networked drives, other days it wouldn't. The SMB client on your Ubuntu media player would have trouble seeing network drives? Make sure everything is in the same broadcast subnet and ethernet segment, and make sure that you aren't running NetBIOS ("Windows File Sharing") over anything other than TCP/IP, not NetBeui -- this shouldn't be a problem with more recent Windows versions, but every so often it pops up. Also, you might have luck if you disable nmbd in your samba clients and let a Windows machine be the master browser, especially if your media player linux machine isn't always on. But I guess this is all moot if you've moved onto some other solution. Maybe this will help someone else.

praeclarum 16y ago
It's very helpful thanks. Honestly, I am disliking the WIndows experience more than I disliked the Ubuntu experience, so I will probably give it another go. To be thoroughly honest, I don't know if it was Samba acting up on me or if it was the Ubuntu file browser (Nautilus?). Every couple days or so, I would have to click the refresh repeatedly for about 30s in order to get it to see the network shares. Was that Samba's fault or GNOMEs? I don't have the knowledge to say either way. Thank you for the information.
- thwarted 16y ago
  I don't know if it was Samba acting up on me or if it was the Ubuntu file browser (Nautilus?). Every couple days or so, I would have to click the refresh repeatedly for about 30s in order to get it to see the network shares. Was that Samba's fault or GNOMEs? I don't have the knowledge to say either way. Whenever it's visibility of machines with Windows file sharing, 90% of the time it is what I've described above -- it's neither Samba nor Gnome's fault. The best thing you can do for the browsablity of your network (once you've ensured that NetBuei isn't in use), if you have an always on non-Windows machine (anything that will run Samba), is run Samba on it with nmbd enabled, even if you don't share anything from that samba instance itself. By default, Samba will always win network elections to become the master browser. Since it always wins, the list of hosts that are sharing is more consistent. Obviously, if you want to access shares on a machine that isn't always on, it takes a while (about 30s or so) after that machine boots to show up in the browse list reliably. Another thing, if you have a bridged network, with both wireless and wired segments (which might be the case with a media player PC), run samba/nmbd on the wired segment. If a wireless machine that is the master browrser loses connectivity, a network election might need to take place and different machines might become the master browser, and they don't always have the full list of machines all the time.

praeclarum 16y ago

It's very helpful thanks. Honestly, I am disliking the WIndows experience more than I disliked the Ubuntu experience, so I will probably give it another go. To be thoroughly honest, I don't know if it was Samba acting up on me or if it was the Ubuntu file browser (Nautilus?). Every couple days or so, I would have to click the refresh repeatedly for about 30s in order to get it to see the network shares. Was that Samba's fault or GNOMEs? I don't have the knowledge to say either way. Thank you for the information.

thwarted 16y ago
I don't know if it was Samba acting up on me or if it was the Ubuntu file browser (Nautilus?). Every couple days or so, I would have to click the refresh repeatedly for about 30s in order to get it to see the network shares. Was that Samba's fault or GNOMEs? I don't have the knowledge to say either way. Whenever it's visibility of machines with Windows file sharing, 90% of the time it is what I've described above -- it's neither Samba nor Gnome's fault. The best thing you can do for the browsablity of your network (once you've ensured that NetBuei isn't in use), if you have an always on non-Windows machine (anything that will run Samba), is run Samba on it with nmbd enabled, even if you don't share anything from that samba instance itself. By default, Samba will always win network elections to become the master browser. Since it always wins, the list of hosts that are sharing is more consistent. Obviously, if you want to access shares on a machine that isn't always on, it takes a while (about 30s or so) after that machine boots to show up in the browse list reliably. Another thing, if you have a bridged network, with both wireless and wired segments (which might be the case with a media player PC), run samba/nmbd on the wired segment. If a wireless machine that is the master browrser loses connectivity, a network election might need to take place and different machines might become the master browser, and they don't always have the full list of machines all the time.