Only Windows 7 can access my NAS

rcnut

Dabbler
Joined
Apr 13, 2018
Messages
33
I'll probably get fussed at for not doing this right, but it's been working fine until now.
I built my first NAS several months ago and it's been great. When I got it up and running, I didn't bother to set up users and groups.
I'm the only user/group here.
I just looked on the network from my Windows 7 machine and started using the NAS like a 20TB drive.
I've had no problem using multiple Windows 7 computers simultaneously, both real and virtual.
Now I need to connect to the NAS with a Linux machine. Linux sees the NAS on the network but when I try to connect, I get
"Unable to mount location
Failed to retrieve share list from server: Connection timed out"
Doesn't seem to matter what flavor of Linux. I thought it might be that Linux just wouldn't work with SMB sharing.
I found something about installing smbclient but that didn't seem to matter.
When I looked at the Change Permissions window, I discovered it has been set on Unix all this time.
I changed it to Windows to see if that would matter, but it didn't.
I also noticed when set to Windows all the Read/Write/Execute check-boxes are grayed out!?
I tried a Windows 10 (which I haven't warmed up to yet) computer and looking at the network, it doesn't even see the NAS!
I've made sure that all computers are in the same workgroup.
What am I missing?
 

rcnut

Dabbler
Joined
Apr 13, 2018
Messages
33
Mine is 11.1-U7
I just discovered it's LinuxMint that wont connect.
I had tried a version of Ubuntu earlier and it didn't work either. Maybe I wasn't holding my tongue right.
I just booted a live CD of Ubuntu and it connects! I need to ask the Mint people what's going on.
And then there's still the issue with Windows 10. Anybody?
 

rcnut

Dabbler
Joined
Apr 13, 2018
Messages
33
Wow! That did it.
Thank you
Now Mint and Windows 10 work.
That one little check-box
Thank you very much
 

rcnut

Dabbler
Joined
Apr 13, 2018
Messages
33
Glad I finally asked on the forum. I was running out of hair to pull out.
 

rcnut

Dabbler
Joined
Apr 13, 2018
Messages
33
Now that I wouldn't need it, would there have been an issue with having it default to checked?
 

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,553
Now that I wouldn't need it, would there have been an issue with having it default to checked?
You can keep it checked on your server without issue. I'm working on some fixes to improve server discovery and access in future versions of FreeNAS. SMB1 will be eventually be deprecated. I saw chatter in samba-technical about 2020 being a cutoff for it, and since samba has 18 month release cycles for major versions, we'll probably follow fairly shortly after. Ultimately, these legacy protocols end up being a blocker for progress (for instance CA / clustering).
 

rcnut

Dabbler
Joined
Apr 13, 2018
Messages
33
What I meant was checked by default when installed. Windows 10 is probably going to be around a while. Not so legacy.
Y'all have done a great job.
 

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,553
What I meant was checked by default when installed. Windows 10 is probably going to be around a while. Not so legacy.
Y'all have done a great job.
Ah, Windows 10 doesn't actually require SMB1. If you type "smbstatus" you'll most likely see that your Windows 10 client has negotiated SMB3.11.
 
Top