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
-
Thanks for the answerZyxel_Jeff said:
. This solution does unfortunately not solve my problem with remote PC clients that doesn't know they need to bypass the local gateway (at a local Coffee shop as example) before making DNS requests to 192.168.1.1.
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 -
OK, I admit my question was a little bit stressed out and rude but I don't know what more information I can provide at the moment so I was hoping for some follow up questions to get in the right direction. Usually I think it's easy and fun to use the Zyxel manuals for self-learning but when i comes to this problem i have no clue whats happening.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 -
-
Thanks for the answerZyxel_Jeff said:
. This solution does unfortunately not solve my problem with remote PC clients that doesn't know they need to bypass the local gateway (at a local Coffee shop as example) before making DNS requests to 192.168.1.1.
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
- 439 Beta Program
- 2.8K Nebula
- 202 Nebula Ideas
- 126 Nebula Status and Incidents
- 6.3K Security
- 508 USG FLEX H Series
- 327 Security Ideas
- 1.7K Switch
- 84 Switch Ideas
- 1.3K Wireless
- 49 Wireless Ideas
- 6.8K Consumer Product
- 288 Service & License
- 458 News and Release
- 89 Security Advisories
- 31 Education Center
- 10 [Campaign] Zyxel Network Detective
- 4.3K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 96 Security Highlight
Freshman Member

Guru Member
Zyxel Employee
