September 7, 20169 yr Solved by enabling NETBIOS in IPv4 Last week Windows 10 Pro update is the only thing I can think that has caused this issue. I searched and tried various things and none have fixed this issue. I can access UnRaid server via browser by using IP address but not identification name (Tower) and my mapped drives in Windows explorer will no longer connect. It's a known issue that Windows 10 has trouble showing servers on network through explorer and I've lived with this by pinning the Tower to quick access and mapped shares via IP to allow Explorer access to my server. The main issue with this problem for me is I can't navigate to my server via Windows Explorer to access all shares/drives. Things I've tried and information: Windows 10 pro 1607 build 14393.105 Unraid v6.1.9 Identification is set to "Tower" (I changed this, and restarted with no luck and then changed back) SMB Local master is enabled. Restarted Windows machine and Server Can access Tower via Mac OSX system on same network and by Identification name in browsers (Chrome and Safari) Forced SMBv1 on Win10 Firewall disabled on Win10 "Fix Common Problems" plugin installed (no issues found with shares or connection) Workgroup is set correctly on Tower and Win10 system Disabled and renenabled IPv6 Credential Manager has no references to the server Registry edit: HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuestAuth with DWORD value set to 1 It's has got to be a change that that Windows update brought that broke the connections. I shut down and installed updates before I left for a trip and returned home to this issue. The server was running while away for remote access. I can't think of anything else to try to resolve this.
Archived
This topic is now archived and is closed to further replies.