[vpn-help] Windows 10 x86_64 Shrewsoft 2.2.2 - DNS for VPN domains does not go through VPN

Shamim Islam shamim.islam at gmail.com
Fri Oct 7 23:12:00 CDT 2016


Look in the policy tab of your connection - you need to identify the
networks that will route through your VPN. Otherwise, either all traffic
goes through the VPN or none of it does. I have 12 networks listed in the
policy tab. (Keep going to the right.)

On Fri, Oct 7, 2016 at 10:16 AM, Marcel Feistl <marcel.feistl at inhive.group>
wrote:

> I guess that the issue is routing.
>
> When I establish the vpn connection I can`t connect to my vm, so the issue
> is that the whole traffic will be routed through the vpn. (This server is
> running on azure)
>
>
>
> Do you have an idea how to fix it?
>
>
>
> Best Regards,
>
>
> *Marcel Feistl *Cloud System Administrator
>
> inhive Group | join innovation | www.inhive-group.com
> Phone +49-06251-80388-17 | Mobile +49-06251-80386-17 |  Fax
> +49-06251-80387-17
>
>
> inhive Group (Germany) GmbH & Co. KG, a member of the inhive Group
> Marienburger Straße 2 | 64653 Lorsch, Germany
> Represented by inhive Group GmbH | AG Darmstadt HRB 91743
> Managing directors: Peter Gegusch, Christian Strauch, Oliver Vettel
>
>
>
> *From:* Shamim Islam [mailto:shamim.islam at gmail.com]
> *Sent:* Friday, October 7, 2016 14:50
> *To:* Marcel Feistl <marcel.feistl at inhive.group>; vpn-help at lists.shrew.net
> *Subject:* RE: [vpn-help] Windows 10 x86_64 Shrewsoft 2.2.2 - DNS for VPN
> domains does not go through VPN
>
>
>
> My problem was only the DNS. Windows kept using local DNS instead of the
> VPN one. Is your problem routing?
>
> On October 7, 2016 4:00:08 AM EDT, Marcel Feistl <
> marcel.feistl at inhive.group> wrote:
>
> Its not the solution.
>
> I`ve changed the metric for the NIC and the machine is still not reachable
> after we start the vpn.
>
>
>
> So in my case there is just 1 network card and if I change the metric for
> it nothing changes.
>
> What is the difference between your and my machine?
>
>
>
> It is Win Server 2012r2
>
>
>
> Best Regards,
>
>
> *Marcel Feistl *Cloud System Administrator
>
> inhive Group | join innovation | www.inhive-group.com
> Phone +49-06251-80388-17 | Mobile +49-06251-80386-17 |  Fax
> +49-06251-80387-17
>
>
> inhive Group (Germany) GmbH & Co. KG, a member of the inhive Group
> Marienburger Straße 2 | 64653 Lorsch, Germany
> Represented by inhive Group GmbH | AG Darmstadt HRB 91743
> Managing directors: Peter Gegusch, Christian Strauch, Oliver Vettel
>
>
>
> *From:* vpn-help [mailto:vpn-help-bounces at lists.shrew.net
> <vpn-help-bounces at lists.shrew.net>] *On Behalf Of *Shamim Islam
> *Sent:* Thursday, October 6, 2016 23:33
> *To:* vpn-help at lists.shrew.net
> *Subject:* Re: [vpn-help] Windows 10 x86_64 Shrewsoft 2.2.2 - DNS for VPN
> domains does not go through VPN
>
>
>
>
> Found the solution. Have to set the metric of the LAN adapter higher than
> the VPN. Once that is done, the DNS of the VPN is hit first.​
>
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.shrew.net/pipermail/vpn-help/attachments/20161008/0f798128/attachment.html>


More information about the vpn-help mailing list