ZyXEL → USG50 L2TP/IPSEC VPN almost working (I think)

just checked- apparently when you do an 'ipconfig' on win7 it labels the l2tp connection as 'PPP adapter xxxx'-the 192.168.55.2 ip should be coming from the 'IP address pool' setting in your USG's L2TP config

-255.255.255.255 mask is normal

-gateway is normal. if you do a 'route print' you should see Windows sets the default route to be the VPN connection with gateway 'on-link'(by default Windows sends everything thru the tunnel)

What do you have set up for policy routes on your USG?

Should have 1 route:
Incoming:any
Destination:{your-l2tp-address-pool-object}
Next-hop:VPN Tunnel{your-l2tp-connection-object}

And another route(for internet access thru the tunnel):
Incoming:Tunnel{your-l2tp-connection-object}
Source:{your-l2tp-address-pool-object}
Next Hop:Trunk{default_wan_trunk}

Hello GB15102 and Brano,

You guys ROCK! Brano, thanks for your quick how-to (»L2TP VPN on USG - quick how-to). That's what got me 95% there.

GB,
I did everything you mentioned and it did the trick with two additions:
In Policy Route:- I needed to change SNAT to 'outgoing-interface'. Without this I couldn't browse the internet through the VPN.

- In the L2TP VPN settings, I used my server (192.168.55.200) as the 1st DNS server. Allowed me to use names instead of ips.

Other things I noticed:
- In order to ping my server through the VPN I had to have my internet traffic going through the VPN connector. (I had unchecked "Use default gateway on remote network" in VPN Connector Properties -> Networking tab -> TCP/IPv4 properties -> Advanced. It was driving me nuts to have internet access blocked while troubleshooting. )
- To ping the server name or connect to it in Windows Explorer, you need the FQDN, ie myserver.mydomain.local and \\myserver.mydomain.local respectively. The server name alone doesn't resolve.

Thanks for the quick responses!
-John