tech360
Cadet
- Joined
- Aug 28, 2014
- Messages
- 2
I recently upgraded to FreeNAS 11 (currently FreeNAS-11.0-U4) and have been experimenting with the VM capability. I created a new VM running Ubuntu Server 17, and installed plex on the server. I wanted to connect my /media dataset from my FreeNAS to the VM using SMB or NFS. I attempted to configure fstab to mount the shares on boot, but I kept getting errors that the shares were not accessible. After troubleshooting a bit, I realized I could not even ping my FreeNAS server from the VM. It appears that the FreeNAS is not visible to the VM, while other network computers and the internet are accessible.
Is there something I am missing to make the FreeNAS system available to the VM through IPv4? I do not know if this is blocked by default for security. Is there something else in FreeNAS that is blocking the packets?
I've had the server up and running for >4 years. SMB shares are visible to Windows 10 devices. I had plex running in a jail but it would not revive after upgrading to FreeNAS 11. I've had problems upgrading within the jail environment, so I was wanting to move to a VM.
Machine details: Supermicro X10SLL-F-O, Intel Xeon E3-1230V3, Crucial 8GBx2 DDR3L PC3-12800 ECC
Thanks in advance!
Is there something I am missing to make the FreeNAS system available to the VM through IPv4? I do not know if this is blocked by default for security. Is there something else in FreeNAS that is blocking the packets?
I've had the server up and running for >4 years. SMB shares are visible to Windows 10 devices. I had plex running in a jail but it would not revive after upgrading to FreeNAS 11. I've had problems upgrading within the jail environment, so I was wanting to move to a VM.
Machine details: Supermicro X10SLL-F-O, Intel Xeon E3-1230V3, Crucial 8GBx2 DDR3L PC3-12800 ECC
Thanks in advance!
Last edited by a moderator: