The samba share is hosted through TrueNAS. I have one computer(win10 pro) connecting to the share just fine. I just setup a new computer, fresh install of Win10 pro. On TrueNAS I created a new user for the share. First attempt to connect from the new machine it worked. After a reboot I can no longer access the share. I have another smb share setup on a QNAP which the computer is able to access. The other computer connects using smb2 and I would assume the new system would as well, but I've enabled smb1 on Truenas just to see if it'd help.
While typing this up, it connected after I tried using truenas's IP instead of the name. This happened to me before in the past on the other PC where I could only connect using the IP until it just randomly stopped working and only accepted connections using the name again. My main PC currently can access the share through IP or host name. The new PC, for now, IP only. I'm thinking maybe a NetBIOS issue but then why is my other PC working fine?
- Enabled smb 1 (will be disabled once this is sorted out)
- Restarted the smb service on Truenas
- Cleared any saved winows credentials
- Tried every policy setting for "Network Security: LAN Manager authentication level" (currently set to NTLMv2 only ignore others)
- Rebooted PC
- Tried creating another account
While typing this up, it connected after I tried using truenas's IP instead of the name. This happened to me before in the past on the other PC where I could only connect using the IP until it just randomly stopped working and only accepted connections using the name again. My main PC currently can access the share through IP or host name. The new PC, for now, IP only. I'm thinking maybe a NetBIOS issue but then why is my other PC working fine?
Facebook
Twitter
Instagram