talkto_menow Posted December 13, 2015 Share Posted December 13, 2015 I'm really frustrated with Windows10. I decided to do upgrade to Win10 on one my computers and to my surprise TOWER is no longer visible when selecting Network items in windows explorer. I searched for solution and found one that requires add new registry key HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuestAuth That did not solve the problem. I added new windows credentials for Tower and I can connect to \\TOWER. Shares are accessible however after closing Windows explorer and rebooting everything is gone again until I enter in address bar \\TOWER I tested Win10 Home 32 bit and Win10 Pro 64 bit with the same result. This is the latest Win10 download. I tested local user in Win10 and microsoft account. Running Unraid 6.1.6 Any suggestions? Thanks Quote Link to comment
Adam64 Posted December 14, 2015 Share Posted December 14, 2015 I had similar issues and resolved it, but don't completely understand why it works now and didn't before. I was using a static IP vs DHCP. I changed it to DHCP, configured my router (DHCP server) to always make my unRAID box x.x.x.10 and as part of the DHCP data I made my router the WINS server. That fixed it. Quote Link to comment
dikkiedirk Posted December 14, 2015 Share Posted December 14, 2015 All I had to do was shutdown all servers and switches on my network and then reboot my router and switching on everything starting with the switches and ending with the unraid server. Could be because my server is set local master. I have static IPs set on all my servers. Quote Link to comment
LateNight Posted December 14, 2015 Share Posted December 14, 2015 I had the same problem after Windows 10 updated last week. I came across this thread and this in particular: Windows 10 now uses SMB3, which Samba has not kept up with (according to the link I found). The latest stable build of Samba, though, does support it. After disabling SMBv2 and SMBv3 on the SMB client in Windows 10 my unRAID machine is no longer hidden. To disable SMBv2 and SMBv3 on the SMB client, run the following commands: sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi sc.exe config mrxsmb20 start= disabled To enable SMBv2 and SMBv3 on the SMB client, run the following commands: sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi sc.exe config mrxsmb20 start= auto *You must restart the computer after you make these changes. Quote Link to comment
Woodpusherghd Posted December 14, 2015 Share Posted December 14, 2015 I had the same problem but the latest Windows 10 build (10586.29) solves the problem. No need to disable smb 2 and 3. Quote Link to comment
LateNight Posted December 14, 2015 Share Posted December 14, 2015 The update to 10586.29 is when I started having problems, odd. Quote Link to comment
talkto_menow Posted December 15, 2015 Author Share Posted December 15, 2015 I check the DHCP settings on my router and Tower has "Static Lease Type" so I guess it means that IP is static. This Windows 10 Home 32bit shows version 1511 build 10856.0. I will check for updates and see if there is any improvement. Quote Link to comment
talkto_menow Posted December 17, 2015 Author Share Posted December 17, 2015 There were no additional updates that would fix this issue. Therefore I decided to give a try and disable SMBv2 and SMBv3. After rebooting TOWER shows up in Windows explorer all the time. Clearly this problem is related to Samba protocol. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.