Wireguard autoconnect, Windows ,external/internal Network Problem
Hello guys,
i need your support.
I built a small/medium network for my company with TPlink Omada components (Controller OC300, Router ER8411, multiple Switches SG3428XMP, Multiple AP EAP773).
All components are up to date.
Two people uses Laptops with Windows 10 to work. We use folder redirections for Desktop/Downloads etc. and two network drives on a Windows Server.
The users are not administrators on the machines.
I configured a scheduled Task on the Laptops to start the Wireguard connection at each user logon.
Works good from outside the company network if the user connects to a wifi before logon.
If the user is in the company and is automatically connected to the company WiFi, the Wireguard connection is also established.
But in this situation the entire connection no longer works - no folder redirection, no connection to the domain, no internet access.
What can i do to get it to work in this situation? Do i have to change the wireguard configuration to get this to work, or is it the normal behavior?
I read somethere that in this case you need to configure NAT-Reflection to NAT your Wireguard external IP from your config to the internal IP on the router? But im not sure if this is correct or how i can do this.
Otherwise, if you cannot change this behavior, i need another routine/script to automatically start Wireguard before the user is logs in - but only when the machine is outside the company network.
Thank you in advance
Michael