How precisely did you map them? What host/servername?
truenas.local won't work. You can delete the mappings and recreate them using the IP address instead. Or make sure via your local DNS - in your router probably - that there is a consistent hostname that always resolves to the IP address of your NAS. And of course configure the VPN to use that same DNS server like when you plugged into your home LAN.
Hi Patrick! Thanks for the insightful information. You definitely enlightened me that there are numerous ways to map shared drives. Until now I had always just hit the "Browse" button next to folder name and selected the network device which I now know only maps based on network name (in this case it mapped as \\TRUENAS\). Apparently, that created issues. I now mapped directly to the IP address which seems to resolve the issue.
My TrueNAS server is on a dedicated IP which never changes, therefore anytime I now VPN into the network I should have direct access to the shared drives using the IP assignment. I've never had any issues not being able to ping (or see) the IP behind the firewall.
I did take your advice and checked the DNS settings and found something interesting...which I'd appreciate any further guidance/feedback.
In my pfsense DNS settings, under DNS Resolution Behavior I have it set to "Use remote DNS settings, ignore local DNS" and have 8.8.4.4 and 8.8.8.8 set as my DNS server(s).
However, under the OpenVPN settings in pfsense I have DNS default domain checked so that a default domain is provided to OpenVPN clients. Also, DNS Server is enabled so that my pfsense server provides DNS services to clients. SEE ATTACHED SCREENSHOTS
I suspect this may have been causing part of the issue I was having. Should I change the OpenVPN DNS settings? If so, how?