November 23, 20178 yr I can't access my shares from Windows File Explorer on ONE computer, I can access it from all others on the same network. unRAID version 6.3.5 - I can access the web GUI via IP address or by typing //TOWER. - Win10 Education Version, which is essentially Win10 Pro. Laptop is also on Win10 EDU though and it works fine. - Both wired and wireless PC's can access //TOWER in File Explorer - I've ensured they are all on the same workgroup - I've ensured unRAID is set to Master in the SMB settings and ensure the workgroup name matches - I've tried changing the name of the unRAID server itself - I've tried rebooting both the unRAID server and the PC several times - Tried disabling IPv6 - Tried two different NIC's on the PC - Ensured the PC and the server are both on 192.168.1.x I've seen this issue brought up a dozen or more times over the last 5 years and it always ends up with "oh I restarted and it worked" or "oh I refreshed several times and it worked" I haven't been fortunate enough to have it start randomly working. Anyone have any suggestions? Since other PC's can access it, I doubt it's an unRAID configuration problem, but more likely the PC. I'm getting ready to do a full reinstall of Windows, but I would really rather not due to the large amount of configuration and downloading I'll have to do. I'd appreciate some guidance. Thanks!
November 23, 20178 yr Community Expert Read through the article in the link below about how to determine what is the Local Master on that PC with the problem: https://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/ (I do wish to point out that this is link to an non-unRAID site and you should use due-diligence in downloading as you would from any website. However, I will say that I have downloaded this program in the past and used it without any problem.) If you do use it, you can report what you found, and if there are still issues, someone may have some other thoughts to assist you.
November 23, 20178 yr Community Expert what I've found is MS broke the computer browser when they disabled smb1 support in the creators update, it seems to effect win to win networking too. https://social.technet.microsoft.com/Forums/en-US/bd0af6aa-51ec-477a-8c81-888a4e60bd94/master-browser-service-broken-after-creator-update?forum=win10itpronetworking currently I have to restart the workstation service on every reboot (after attempting connection) to get everything working again, this might work for you. yet to find a good, permanent solution. Edited November 23, 20178 yr by tjb_altf4
November 23, 20178 yr I had to add my unraid server to the hosts file on my windows 10 vm to get it to work be able to access the server by name.
November 25, 20178 yr Community Expert On 23/11/2017 at 1:11 PM, SSD said: I had to add my unraid server to the hosts file on my windows 10 vm to get it to work be able to access the server by name. Interesting, since doing this everything works without any work arounds mentioned previously, regardless of the fact I'm accessing by IP ! Not sure what the hell windows is doing in the background, but this fixed all my issues. Note: it also significantly improved first access (per reboot) to unraid web ui as well Edited November 25, 20178 yr by tjb_altf4
July 5, 20187 yr Hi all, I had same issue and It got fixed easy with below changes: Go to Control Panel Go to Credential Manager on each Windows 7/10 machine on the network Under Windows Credentials, type in the name of each machine, username and password And It's DONE.
Archived
This topic is now archived and is closed to further replies.