Allow VPN client to access remote PCs by name, not FQDN
-
I have looked at so many threads and articles and I just cannot figure out how to make this work!
I can access remote PCs via IP and FQDN (<pcname>.<domainname>), but not just by <pcname> the way I can on the local network.
Is there some checkbox somewhere I am missing?
Thanks!
-
Not looked into it but have you tried host / alias setting
-
@mattaton Short answer, always use FQDN.
-
maybe you what to push to connected clients an WINS IP server (old stuff but still functional) that it's keeping an inventory with NetBIOS name (pcname as you say).
So in this way remote clients can ask local LAN DNS server name but also WINS to retrieve NetBIOS name mapping to an IP....
Where ever the findings, please post who you resolved in the end. -
@bob-dig So this is typical behavior with OpenVPN via pfSense?
I have backup operations that run on my PC to another local PC (when it's local). I was hoping to be able to take that PC on the road with me, connect to the VPN, and then let the backup run to the same local PC name through the tunnel. If I have to use FQDN, that's not going to work. Unless, of course, I change all my paths over to FQDN, which I'm not sure work in my local network environment.@Meserias I've hunted for quite a while. If I can't find a solution by posting on the Netgate forum, I may be out of luck!
-
@bob-dig So, FQDN unsurprisingly works locally, but I'm still reluctant to switch everything over to it.
-
It appears I just had to add the DNS Default Domain under Advanced Client Settings in the VPN settings.
That just tacks my default LAN domain to the end of DNS lookups on the VPN client, et voila, NetBIOS or base PC names (without the domain appended) are converted to FQDN behind-the-scenes the same as happens locally and all is well.
