https://community.checkpoint.com/t5/SASE-and-Remote-Access/after-disabe-split-tunnel-routes-missing/m-p/59308#M12128 When a VPN client is connected there should be routes that are part of the remote access VPN domain (if set seperately), so that is where you can easily add or remove the networks that should be reachable from the VPN client.<BR />You verify that on a Windows client with: route print<BR />Do keep in mind that it can take multiple logins before those settings are actually collected by the client, best is to test and sometimes if it all still fails reboot he PC. Wed, 31 Jul 2019 06:13:07 GMT Maarten_Sjouw 2019-07-31T06:13:07Z https://community.checkpoint.com/t5/SASE-and-Remote-Access/after-disabe-split-tunnel-routes-missing/m-p/59279#M12127 <P>hi,</P><P>when i disabled split tunnel , my routes in vpn domain changes with gw route table. so vpn clients can not reach subnet in vpn domain. i configred subnet again yet nothing working.&nbsp;</P><P>i dont want to gw route map on client after vpn connection. thanks for help.&nbsp;</P> Tue, 30 Jul 2019 20:53:05 GMT https://community.checkpoint.com/t5/SASE-and-Remote-Access/after-disabe-split-tunnel-routes-missing/m-p/59279#M12127 kayzersoze 2019-07-30T20:53:05Z https://community.checkpoint.com/t5/SASE-and-Remote-Access/after-disabe-split-tunnel-routes-missing/m-p/59308#M12128 When a VPN client is connected there should be routes that are part of the remote access VPN domain (if set seperately), so that is where you can easily add or remove the networks that should be reachable from the VPN client.<BR />You verify that on a Windows client with: route print<BR />Do keep in mind that it can take multiple logins before those settings are actually collected by the client, best is to test and sometimes if it all still fails reboot he PC. Wed, 31 Jul 2019 06:13:07 GMT https://community.checkpoint.com/t5/SASE-and-Remote-Access/after-disabe-split-tunnel-routes-missing/m-p/59308#M12128 Maarten_Sjouw 2019-07-31T06:13:07Z