L2TP/iPsec Windows
Hey guys
I don't have any issues setting up in Nebula or getting the clients connected. But once connected it all goes wrong, on every machine I have had to add a route add command so the machines can see the remote network such as below...
route add 192.168.1.0 mask 255.255.255.0 172.16.0.0
I have added batch files in machines startup folders but this isn't a great long term solution, any ideas what I need to do or is this the norm using Windows VPN client?
0
All Replies
-
Can you be ensure if those L2TP profiles has enable the "Use default gateway on remote network" in advanced TCP/IP settings?If not then activate the support request also the org./site name for me to check.
Chris
0 -
Thanks Chris, I always leave this unchecked as from past experience it causes slow internet browsing but I will give it a try :-)
0
Categories
- All Categories
- 189 Beta Program
- 1.7K Nebula
- 91 Nebula Ideas
- 63 Nebula Status and Incidents
- 4.7K Security
- 236 Security Ideas
- 1.1K Switch
- 51 Switch Ideas
- 917 WirelessLAN
- 27 WLAN Ideas
- 5.4K Consumer Product
- 173 Service & License
- 296 News and Release
- 65 Security Advisories
- 14 Education Center
- 1K FAQ
- 452 Nebula FAQ
- 258 Security FAQ
- 100 Switch FAQ
- 115 WirelessLAN FAQ
- 22 Consumer Product FAQ
- 67 Service & License FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 69 About Community
- 52 Security Highlight