If you open a command line window and type route print you will see a route with a destination of 0.0.0.0 and the gateway set to the VPN tunnel endpoint (most likely an IP address from the remote subnet, i.e. the VPN servers LAN). That's the default route.

Where 192.168.0.1 is my local router through which I'm connected to the internet, 192.168.0.11 is my client computer's address on this local network, 86.129.242.71 is my VPN server, 10.1.0.1 - 10.1.0.10 is my IP range for VPN clients and 10.1.0.1 is the default gateway on that server. Oct 29, 2017 · Destination 0.0.0.0 Netmask 0.0.0.0 Gateway 0.0.0.0 and Destination 0.0.0.0 Netmask 0.0.0.0 Gateway aaa.bbb.ccc.244 Checking through control panel only indicated one default gateway aaa.bbb.ccc.244. I did a "route -f" and the 0.0.0.0 gateway entry disappeared, as did the network problems I was trying to troubleshoot. Oct 07, 2010 · I have a windows server 2008 r2 machine that is connected to a domain. The server also has DHCP installed. I followed your instructions step-by-step. Clients can connect to the VPN, but. 1) the client’s gateway on the client is set to 0.0.0.0. This doesn’t SEEM right to me, but maybe it is. When connecting from the remote computer, I get an IP address from the dhcp pool but the default gateway is 0.0.0.0 and i cannot ping the remote server or asa. Also I cannot get webpages once connected to the VPN as the routing is through 0.0.0.0 I am using Shrewsoft VPN client due to a 64 bit machine.

Oct 07, 2010 · I have a windows server 2008 r2 machine that is connected to a domain. The server also has DHCP installed. I followed your instructions step-by-step. Clients can connect to the VPN, but. 1) the client’s gateway on the client is set to 0.0.0.0. This doesn’t SEEM right to me, but maybe it is.

Where 192.168.0.1 is my local router through which I'm connected to the internet, 192.168.0.11 is my client computer's address on this local network, 86.129.242.71 is my VPN server, 10.1.0.1 - 10.1.0.10 is my IP range for VPN clients and 10.1.0.1 is the default gateway on that server. Oct 29, 2017 · Destination 0.0.0.0 Netmask 0.0.0.0 Gateway 0.0.0.0 and Destination 0.0.0.0 Netmask 0.0.0.0 Gateway aaa.bbb.ccc.244 Checking through control panel only indicated one default gateway aaa.bbb.ccc.244. I did a "route -f" and the 0.0.0.0 gateway entry disappeared, as did the network problems I was trying to troubleshoot. Oct 07, 2010 · I have a windows server 2008 r2 machine that is connected to a domain. The server also has DHCP installed. I followed your instructions step-by-step. Clients can connect to the VPN, but. 1) the client’s gateway on the client is set to 0.0.0.0. This doesn’t SEEM right to me, but maybe it is. When connecting from the remote computer, I get an IP address from the dhcp pool but the default gateway is 0.0.0.0 and i cannot ping the remote server or asa. Also I cannot get webpages once connected to the VPN as the routing is through 0.0.0.0 I am using Shrewsoft VPN client due to a 64 bit machine.

Oct 07, 2010 · I have a windows server 2008 r2 machine that is connected to a domain. The server also has DHCP installed. I followed your instructions step-by-step. Clients can connect to the VPN, but. 1) the client’s gateway on the client is set to 0.0.0.0. This doesn’t SEEM right to me, but maybe it is.

Default Gateway 172.16.172.1 Enter the IP address of the default gateway or router. Enter 0.0.0.0 for no default router (Internet-facing). Metric 1 Enter the metric, from 1 to 16. Tunnel Default Gateway 10.10.0.2 Enter the IP address of the default gateway or router for tunnels. Enter 0.0.0.0 for no default router (corporate-facing). I have tried connecting the VPN on a separate machine (Windows Server 2008 Desktop connected via Ethernet to same DSL router), same issue occurs, so doesn't seem to be limited to Windows 8 clients. Ensured all Windows Updates have been applied Jan 11, 2009 · In my testlab, I had to reboot my Windows 2008 Server before everything started working correctly, but it might not be necessary to do this. From the client behind the Windows Server, which has its default gateway set to 192.168.10.254, try to ping the client behind the Juniper firewall, which has its default gateway set to 192.168.2.8 :