December 29, 20241 yr Attached SMB settings and SMB security settings for reference. New to unRAID. I setup SMB to access shares on my windows 11 laptop. I seem to just get an error when I try to access: Network --> NAS --> windows cannot access \\Hostname error code 0x80070035 I have: - created (and deleted) a simple username and password. Added that to the shares with read/write and set to private. - cleared and readded to windows credentials. - tried restarting the server and my laptop. - reset all networking and restarted my laptop - disabled windows firewall It's on the same network. The nas is plugged right into my modem/router combo and if i type the ip into the file manager address it pops open my browser to http://ip/Main for the unRAID control panel. I'm out of ideas.
December 29, 20241 yr Author Solution At the point I made this thread, no. I couldn't see any folders or get any level of access through the windows file manager. Since then I (again a couple of more times) deleted the user and set everything to private. I reset network settings again and restarted my PC. Then I made the user again, but forgot to change to allow the user read/write access. I was then able to get into the file system and have access. I don't know if it was the order of operations, but for some reason it's working now. I hope it keeps working. I spent all day on this. Edited December 29, 20241 yr by tenletters
December 29, 20241 yr Community Expert 24 minutes ago, tenletters said: restarted my PC. This is a good thing to do anytime you make a change to the network configuration on either Windows or the Unraid side. Windows does not have a convenient way to stop and start its SMB service which is a convenient way to force a logout. (Windows will only allow one connection to a server and there is no way to easily force it to a logout of a SMB login. With Unraid, you do it by stopping-and-starting the array.)
December 29, 20241 yr Author I left the array going though. I didn't restart the server in this case.
December 29, 20241 yr Community Expert 1 hour ago, tenletters said: I left the array going though. I didn't restart the server in this case. I understand that either side can break the login but I have always done it from the Windows side as that one seems to be the bigger 'chamber of horrors' that defies understanding... 🤣
December 29, 20241 yr Community Expert Windows has made quite a few samba changes. its always a windows side thing. https://learn.microsoft.com/en-us/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell
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.