Remote VPN and local network DNS conflict with L2Tp wizard?
Options
Hi.
I have configured an L2TP VPN connection for remote clients (full tunnel) using only the wizard on my USG20W-VPN for now to learn the necessary config settings on my own.
Why is the remote client PC still asking the local gateway for DNS requests after VPN connection is established on remote client? This causes major problems with accessing NAS resources on our company network. How can I fix this problem easy?
Alot of routers use 192.168.1.1 as standard so this must be a known issue and why would you want a client to use local network dns in full tunnel mode at all? Is it something that has to be addressed in Windows?
I have configured an L2TP VPN connection for remote clients (full tunnel) using only the wizard on my USG20W-VPN for now to learn the necessary config settings on my own.
Why is the remote client PC still asking the local gateway for DNS requests after VPN connection is established on remote client? This causes major problems with accessing NAS resources on our company network. How can I fix this problem easy?
Alot of routers use 192.168.1.1 as standard so this must be a known issue and why would you want a client to use local network dns in full tunnel mode at all? Is it something that has to be addressed in Windows?
0
Accepted Solution
-
Zyxel_Jeff said:
I think I solved the problem in another way by using unique subnet addressing on our HQ LAN instead of default (out of the box) addressing.
0
All Replies
-
How can I fix this problem easy?
The easy and fast solution is... contact a skilled network technician and provide him any information he/she asks. And pay he/she nicely.The cheap solution is.. start to provide a bit more information. It's not "easy", but sometimes works.0 -
mMontana said:
How can I fix this problem easy?
The easy and fast solution is... contact a skilled network technician and provide him any information he/she asks. And pay he/she nicely.The cheap solution is.. start to provide a bit more information. It's not "easy", but sometimes works.
0 -
0
-
Zyxel_Jeff said:
I think I solved the problem in another way by using unique subnet addressing on our HQ LAN instead of default (out of the box) addressing.
0
Categories
- All Categories
- 397 Beta Program
- 2.1K Nebula
- 117 Nebula Ideas
- 81 Nebula Status and Incidents
- 5.1K Security
- 91 USG FLEX H Series
- 247 Security Ideas
- 1.3K Switch
- 69 Switch Ideas
- 919 WirelessLAN
- 35 WLAN Ideas
- 5.9K Consumer Product
- 210 Service & License
- 337 News and Release
- 71 Security Advisories
- 21 Education Center
- 5 [Campaign] Zyxel Network Detective
- 2K FAQ
- 926 Nebula FAQ
- 422 Security FAQ
- 238 Switch FAQ
- 210 WirelessLAN FAQ
- 47 Consumer Product FAQ
- 139 Service & License FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 72 About Community
- 62 Security Highlight