Hello,
we're using SSL VPN Client for our employees and in the RemoteAccess -> Advanced Settings we have set our internal DNS / Active Directory (10.200.100.31 and .32).
The respective route and firewall rule is created accordingly
PUSH: Received control message: 'PUSH_REPLY,route-gateway 10.242.2.1,route-gateway 10.242.2.1,topology subnet,ping 10,ping-restart 120,route 10.200.100.0 255.255.255.0,dhcp-option DNS 10.200.100.31,dhcp-option DNS 10.200.100.32,dhcp-option DOMAIN myspecialcompany.local,ifconfig 10.242.2.14 255.255.255.0'
Firewall for DNS: employees (user group network) -> DNS -> 10.200.100.31 and 32
Now we have some external employees who should also use the ssl vpn client, but not our internetl network (10.200.100.0/24), only some terminalservers in other network.
We created a new VLAN/Network like 10.0.10.0/24
Firewall: external employees (user group network) -> mstsc -> terminalservers
We pushed only the route to the new network to these users:
PUSH: Received control message: 'PUSH_REPLY,route-gateway 10.242.2.1,route-gateway 10.242.2.1,topology subnet,ping 10,ping-restart 120,route 10.0.10.0 255.255.255.0,dhcp-option DNS 10.200.100.31,dhcp-option DNS 10.200.100.32,dhcp-option DOMAIN myspecialcompany.local,ifconfig 10.242.2.14 255.255.255.0'
The connection to the terminalservers is working fine, bot the DNS lookup not.
All external employees get the internal DNS server pushed.
I tried to edit the config file with
pull-filter ignore "dhcp-option DNS"
but with this, the client does not connect.
Whats the best way to solve our problem?
Push the IP of the UTM (and if yes, which one) to all users and add a request routing for our domain "myspecialcompany.local"?
Regards
Tobias
This thread was automatically locked due to age.