Hi, we had a very old FreeNAS with SMB enabled that worked well for people across different VLANs (different IP subnets). Our switch handles the tagging and communication.
Due to SMB1 depreciation, we tried to install TrueNAS 13 Core. Everything is set up accordingly, and people in the same VLAN can access via Windows Explorer.
However, people in different VLAN (different IP subnets) can't access it, ie. when going to \\10.0.1.11 they got error "Windows cannot access \\10.0.1.11" with detailed error code 0x80004005
(NOTE: truenas is the server name)
What we've tried to confirm it's not network issue:
- We can ping the TrueNAS from different IP subnets
- We enabled FTP on the TrueNAS, and confirmed that people in different IP subnets can access
So from these tests, seems like the access problem lies in SMB service.
Is this the restriction of the SMB implementation?
Any way to make it work?
Thanks
Due to SMB1 depreciation, we tried to install TrueNAS 13 Core. Everything is set up accordingly, and people in the same VLAN can access via Windows Explorer.
However, people in different VLAN (different IP subnets) can't access it, ie. when going to \\10.0.1.11 they got error "Windows cannot access \\10.0.1.11" with detailed error code 0x80004005
(NOTE: truenas is the server name)
What we've tried to confirm it's not network issue:
- We can ping the TrueNAS from different IP subnets
- We enabled FTP on the TrueNAS, and confirmed that people in different IP subnets can access
So from these tests, seems like the access problem lies in SMB service.
Is this the restriction of the SMB implementation?
Any way to make it work?
Thanks
