Wireguard VPN clients accessing Windows File Server & local resources
I've been looking into Firewalla Gold replacing our current Sonicwall with SSL VPN clients. Currently the Sonicwall manages/allows incoming VPN clients to access the LAN inside the office, including the Windows file server shares and the AD/DNS/DHCP server.
If a client's laptop outside of the office connects now via Netextender and their login name on the domain is gharmon for example, we can switch user within Windows, and since the VPN connection is active, login to a new account not setup on the laptop, but active on AD, such as bcallus, and they will be authenticated and logged in. VPN'd clients can also access local resources such as office printers.
I see Firewalla can run in either router or bridge mode. Windows AD server prefers using its own DHCP/DNS server. Is there a way to configure the Firewalla Gold Plus in either router/bridge mode to keep DHCP/DNS on the current Windows server as setup now? And would VPN'd Wireguard clients then be able to access current LAN resources (file server, printers, domain, etc.)?
-
DHCP, you can turn off firewalla's and use your own. DNS is a bit tricky, since firewalla does a lot of filtering with it, if you use your own, you may need to turn off that feature, unless your DNS server is not on the same LAN segment, then it should be okay.
VPN'ed Wireguard clients should be able to access LAN resources. (remember these devices are now in their own network, so you can't have LAN services blocking none LAN clients)
Please sign in to leave a comment.
Comments
1 comment