Hey Guys,
I understand the issues surrounding more than one access protocol per volume etc. I have a simple home environment, most things are read-only. Most of my machines accessing the NAS are linux, but I have a single windows VM to run some VMWare ESX Backup software to a mapped network drive (freenas).
Whenever I actually MAP a network drive with SMB, my NFS shares become un-usable. Literally can't access any data. However, if I un-map the drive, and remove the "system volume information" folder, NFS is magically working again.
The crazy part is that my laptop and the mrs's laptop which are both windows, can write files to it just fine (not mapped, through explorer only) and it's no problem. I also tried with a standalone linux box as a SMB and NFS server to see if I can reproduce this, and I can't.
Is there a FreeNAS setting somewhere to have NFS not honor any windows permissions etc? Anyone know of a fix within Windows? Is this even a permissions thing? I would assume so.
Thanks!
I understand the issues surrounding more than one access protocol per volume etc. I have a simple home environment, most things are read-only. Most of my machines accessing the NAS are linux, but I have a single windows VM to run some VMWare ESX Backup software to a mapped network drive (freenas).
Whenever I actually MAP a network drive with SMB, my NFS shares become un-usable. Literally can't access any data. However, if I un-map the drive, and remove the "system volume information" folder, NFS is magically working again.
The crazy part is that my laptop and the mrs's laptop which are both windows, can write files to it just fine (not mapped, through explorer only) and it's no problem. I also tried with a standalone linux box as a SMB and NFS server to see if I can reproduce this, and I can't.
Is there a FreeNAS setting somewhere to have NFS not honor any windows permissions etc? Anyone know of a fix within Windows? Is this even a permissions thing? I would assume so.
Thanks!