reefcrazed Posted November 8, 2018 Share Posted November 8, 2018 I have updated from the first version of Unraid, I really never needed to so I just let it ride all these years. So I updated last week, a billion great changes it seems. I have a domain but I do not want the the Unraid attached. I have the share set for workgroup and public. If I try to go to \\servername\shared I get an error. If I go to the \\192.168.0.30\shared I can get right to it. I am 100% positive my DNS is right. What would cause this? Link to comment
itimpi Posted November 8, 2018 Share Posted November 8, 2018 What client are you using? If it is Windows then this is quite a common issue as with default settings recent Microsoft updates have broken the way name resolution happens for finding Samba servers and the associated shares. Link to comment
reefcrazed Posted November 9, 2018 Author Share Posted November 9, 2018 I think they all are either a mix of 2016 server or Windows 10. Link to comment
reefcrazed Posted November 9, 2018 Author Share Posted November 9, 2018 Also, I tried just doing a net view \\servername and shows nothing. I mean the share is definitely there, if I use the IP address I can get to it. A simple ping or NS Lookup shows the DNS resolution is perfect. Link to comment
itimpi Posted November 9, 2018 Share Posted November 9, 2018 The name lookup that matters is not DNS, but netBios. That is what tends to be disabled in latest Windows builds. Link to comment
reefcrazed Posted November 9, 2018 Author Share Posted November 9, 2018 I can just change the mappings I guess. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.