CIFS-Shares are not accessible from Linux Mint 18 Sarah

[FreeNAS-LinuxUser]

My network setup is as follows:
Speedport Router from Telekom: 192.168.1.1/24 DHCP enabled.
NAS(HP Microserver Gen8) with FreeNAS 11.2 U3 connects to it: 192.168.1.100/24
LINKSYS Router connects to Speedport: WAN-IP: 192.168.1.5/24
LAN-IP 192.168.2.100/24 DHCP enabled
PC1 with Linux Mint 18 Sarah connects to LINKSYS: 192.168.2.101/24
PC2 with Linux Mint 19.1 Tessa connects to LINKSYS 192.168.2.102/24

Both PCs don't show the shares on the NAS in Thunar under "network".
Both PCs can successfully ping the NAS.
Both PCs can successfully access and login the FreeNAS-GUI in the webbrowser.

PC2 can mount the shares with this command in the terminal:

Code:

sudo mount -t cifs //192.168.1.100/Test /mnt/Test -o username=mike

Then the mounted share is browsable in Thunar.

PC1 can't even do that.
Please help me to resolve this issue. I want PC1 to at least be able to access the shares, too. Preffered would be a solution to see the shares in Thunar after booting the machine and, upon double-clicking a share, to be asked for the credentials and being able to read and write on the shares thereafter.

 

[sretalla]

What's the full network config on the PCs and on FreeNAS? particularly the default gateways.

I don't see where the routing between the 192.168.1.x and 192.168.2.x networks is happening... is it in the Linksys router?

Because you're across subnets, it's only natural that browsing doesn't work... why do you need the subnets? (or why have FreeNAS on a separate subnet away from the PCs if you want browsing?)

Your DNS or WINS config will be important if you do maintain the subnetting as-is.

 

[FreeNAS-LinuxUser]

It happens in the LINKSYS. Its WAN-IP is from the 192.168.1.XXX and its LAN-IP is from the 192.168.2.XXX. The LINKSYS is flashed with dd-wrt and is my VPN-Gateway. So all machines connected to its 192.168.2.XXX LAN are immune to things like geoblocking.
The machines connected to the Speedport are still affected by geoblocking. But for some activities and users of my net that is fine. And I need the LAN-Ports of both routers.
Gateway is always 192.168.2.100 (LINKSYS'-IP)
Primary DNS is 192.168.1.1
Second and Third DNS are from my VPN-Provider.
These settings are identical for both PCs. But one can mount the shares, the other one not at all. But again both PCs can ping and login the NAS.
And the NAS settings are:
LAN-IP: 192.168.1.100/24
Default Routes: 192.168.1.1
Nameservers: 192.168.1.1

 

[KrisBee]

Clearly, mint 19.1 is more up to date. So, is there a "mount.cifs" bug in the older mint 18? As far as Thunar is concerned, IIRC the in-built network browsing provided by the gvfs backend relies on SMB1, but does it span subnets? You'll have to "Enable SMB1" on your FreeNAS smb service to test that. Otherwise keep the min smb proctocol at SMB2_02 and possibly make shortcut/bookmarks in Thunar, or resort to automounter.