For some reason, I am having trouble accessing my server. I cannot find it in the Network in Windows 10. I have tried this trick here: 

 

HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuestAuth

 

With no avail. I had set up that was working, but I upgraded disks and just removed everything from it. Is there any way to reset everything? The disks are supposedly formatted and ready. 

tower-syslog-20170402-2118.zip

tower-diagnostics-20170403-2129.zip

 

I would like to note, that the server was up and running before, but I upgraded disks. It was originally just set up to try unraid and see if I liked it. So now that I have decided I like it, I went through and cleared out the shares and created new ones. Now I can't seem to map to them. 

Edited March 18, 20188 yr by FloppyWaffles

So when I try to map the server manually using \\tower\users, I get "Access Denied". I followed a stickied thread, Here which lead me to adding "ntlm auth = yes" to the SMB extra configuration and that didn't seem to do anything.

Edited April 4, 20179 yr by FloppyWaffles

Instead of posting only syslog, you should always go to Tools - Diagnostics and post the complete zip. It contains syslog(s) and many other useful files for diagnosing problems.

Have you been through this thread?

 

It covers a lot of issues that folks have had with the latest releases.  I would also like to point that there were a lot of issues with Windows 10 access when it was first introduced but they seem to have diminished considerably in the last couple of months. 

23 hours ago, Frank1940 said:

Have you been through this thread?

 

It covers a lot of issues that folks have had with the latest releases.  I would also like to point that there were a lot of issues with Windows 10 access when it was first introduced but they seem to have diminished considerably in the last couple of months. 

 

 

I went to that thread, which immediately leads me to this here. It only really said to do the SMB edit. Which I did and it didn't solve anything. I am going to go through it a little more thoroughly now though to see if there is anything I missed. Thanks!

 

23 hours ago, trurl said:

Instead of posting only syslog, you should always go to Tools - Diagnostics and post the complete zip. It contains syslog(s) and many other useful files for diagnosing problems.

 

 

I have edited my original post with the full diagnostic download. 

On 4/2/2017 at 10:42 PM, FloppyWaffles said:

So when I try to map the server manually using \\tower\users, I get "Access Denied". I followed a stickied thread, Here which lead me to adding "ntlm auth = yes" to the SMB extra configuration and that didn't seem to do anything.

 

OK.  I don't where you got this idea but you access your shares by \\server_name\share_name (example:     \\elsie1\Media     and capitalization is important!  )  in Windows Explorer navigation box.  When I looked at your share names in the diagnostics file, I didn't see any user share that could be 'users'  !   You can also get to the network by entering Network (again capitalization is important) in the navigation bar of Windows Explorer.    You should be able to see your server there.  If not, read through this post and its links and set up your server to become the Local  Master:

If you see your server name (should be Tower), double-click on it and you should see your shares.  They should be there as the shares that I looked were all public shares.

 

If you don't see your server name, check to see if your server is the Local Master.  You do this by 'Settings'  >>>   'SMB'   >>> 'Workgroup Settings'.  If it is and you can't see your server, reboot your PC.

 

If it is not the Local Master, see see which computer is.  Then powerdown both of these computers.  Turn the server on first and wait until it becomes the Local master.  Then start the other computer back-up. 

Edited April 4, 20179 yr by Frank1940