OpenVPN and WINs refuse to play together
-
As already noted on the other thread, you should use DNS and FQDNs. No idea why you started another thread about the same thing. >:(
https://forum.pfsense.org/index.php?topic=89868
(Not to mention, no such thing will work with OpenVPN unless specifically enable - which is still a bad idea and completely pointless for this purpose.)
-
As already noted on the other thread, you should use DNS and FQDNs. No idea why you started another thread about the same thing.
https://forum.pfsense.org/index.php?topic=89868
My DNS and DQDN is working fine, I can access the nas device like so: \host.domain. But I want the \host to work
-
In the case that you will follow doctornotor, I would still want to assign static IPs
-
-
Running a wins server is a hassle and its not 100% reliable either.
I have 1 configured and haven't used it in years.
-
For the benefit of those who want this to work without a WINS server, do the following:
Set the pfsense domain to: lan
Check the option of sending a default domain name to VPN clients in the OpenVPN server config and choose 'lan' as the default domain name.
Works.
-
I probably would have made the domain something other than "lan", but sure. Thats seems logical. Its working well?
-
I probably would have made the domain something other than "lan", but sure. Thats seems logical. Its working well?
Actually 'lan' along with 'local' are in the list of reserved domains and that's what made the whole thing work. Don't ask me why lol
-
It works for me using DNS Resolver if I use \MachineName.DomainName without using wins and without having to use any specific reserved names.
I think its probably better this way but if the other way makes you happy, go for it if its not breaking anything I guess.
Edit: I learned something about this…
Set the pfsense domain to: AnyWordYouLike
Check the option of sending a default domain name to VPN clients in the OpenVPN server config and choose the same word you chose for pfsense domain as the default domain name.
It doesn't have to be "lan"
-
if this is an Active Directory just change group policy to the FQDN and problem does not matter 5 min work to you and on there next login they have the new settings