Remote VPN and local network DNS conflict with L2Tp wizard?
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 -
See how you've made an impact in Zyxel Community this year!
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
- 415 Beta Program
- 2.4K Nebula
- 147 Nebula Ideas
- 96 Nebula Status and Incidents
- 5.7K Security
- 262 USG FLEX H Series
- 271 Security Ideas
- 1.4K Switch
- 74 Switch Ideas
- 1.1K Wireless
- 40 Wireless Ideas
- 6.4K Consumer Product
- 249 Service & License
- 387 News and Release
- 84 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.5K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 73 Security Highlight