December 5, 201312 yr I use unRAID as a media server for several Dune media player devices. These devices use Samba. On 4.7, Windows 7 would not show my shares in "Network", but I could manually type \\TOWER and browse everything just fine. Sometimes windows 7 would automatically find \\TOWER, but it was about 50/50. However, my Dune devices have a network browser, which would always find \\TOWER. However, since switching to 5.0.3, neither my Windows 7 PC, nor Dune devices seem to automatically find \\TOWER. I can manually type \\TOWER (or in the case of the Dune, add a shortcut to \\TOWER), but nothing seems to automatically be able to find my unRAID server. I have SMB enabled as workgroup. My workgroup name matches on all devices. UnRAID was the local master, but I tried it as no, didn't make a difference, so I changed back to yes. Searching the web, I found a couple of examples where linux was using a default netmask of 255.255.0.0 and that would cause this behavior. But I have checked etho0 on my unRAID and mask is 255.255.255.0. I checked to make sure Discovery is on in my Win7 PC too. I've spent several hours trying to figure out what could have changed, but I'm at a loss. It's like unRAID is in stealth mode or something. Nothing can see it to browse, but if I type in a link to \\tower, it will open the location I've typed. On the hardware side, I have a Trendnet wired router (and tried a D-Link thinking the router might be the problem) that is not connected to the internet (no WAN). Dunes, unRAID, and PC connect to a D-Link switch. Switch connects to router. All devices are setup for Auto DHCP. Anyone have any ideas?
December 5, 201312 yr Have you run the new permissions script? Also you will have to delete your cached login info in windows, but I don't recall how to do that. Sent from a mobile device, sorry for any typos.
December 5, 201312 yr Author Yes, ran the new permissions script. I don't get any type of errors. I simply can't browse my network shares. But if I enter \\tower\movies , for example, it will open my movies share and I can open any folder or file in that share without a problem. My problem is mainly with my Dune players. I basically have to type using the 1-9 buttons on my remote, like old school phone texting (push 7 4 times to enter an S). My only thought so far, did unRAID 4.7 use smb1, and 5.0 switched to smb2? The only thing I can think of is that the Dune players are old enough to not have smb2 and maybe it isn't backwards compatible? I don't know.
December 5, 201312 yr Also you will have to delete your cached login info in windows, but I don't recall how to do that. I'm also interested in how to do that!
December 5, 201312 yr Author The more I think about it, the more I think it has to be in the router. When I browsed SMB on my Dunes, not only did I see my unRAID shares, but I would also see all other Dune devices on my network. One Dune cannot see another Dune now, which would have nothing to do with unRAID I guess (unless being the master somehow masks other devices). I wonder what ports samba requires.
December 5, 201312 yr Sorry to disappoint you but it is a windows issue. One of the many windows & networking mysteries. Edit: I'm also interested in how to do that! Read up on this. This is invaluable!
December 5, 201312 yr Author Well, I can't believe I wasted hours when the solution was so simple. My workgroup name in 4.7 was WORKGROUP. Somehow, when I migrated to 5.0, my workgroup was entered as Workgroup. I have 5 samba servers, unraid included, all part of WORKGROUP. It turns out that if i enter any of their workgroup as Workgroup, and the rest are WORKGROUP, then none of them can find each other. At least according to Microsoft, the workgroup name is not case sensative, so it shouldn't have mattered. You would think that if it was case sensative, it would have created two workgroups, WORKGROUP and Workgroup, and server/clients would still have been able to see whatever was in their group. But no, using WORKGROUP and Workgroup completely knocked out network discovery on everything, and none of the devices could see each other. But now that all servers and devices are in WORKGROUP, everything is back to normal. Stupid and Weird!
December 5, 201312 yr Glad you found it. I'm bookmarking this solution...someone will need it again in a couple of months.
December 5, 201312 yr Also you will have to delete your cached login info in windows, but I don't recall how to do that. I'm also interested in how to do that! Wouldn't that be in "Credential Manager" in Control Panel?
Archived
This topic is now archived and is closed to further replies.