<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Tahoma">Thank you for your reply Jim.<br>
<br>
I do not see a place to select any adapter settings in the policy
area, unless perhaps I am missing something or need to change
another setting to allow that?</font><br>
<br>
<div class="moz-cite-prefix">On 9/23/2015 8:49 AM, Jim Dettman
wrote:<br>
</div>
<blockquote cite="mid:6791AF37F962498DB6C441A0F266FD60@XPS"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 8.00.6001.23588">
<div dir="ltr" align="left"> </div>
<div dir="ltr" align="left"><span class="328054712-23092015"><font
color="#0000ff" size="2" face="Arial"> If I remember
correctly from when I tripped over this, the issue was that
I didn't select the virtual adapter in the policy.</font></span></div>
<div dir="ltr" align="left"><span class="328054712-23092015"></span> </div>
<div dir="ltr" align="left"><span class="328054712-23092015"><font
color="#0000ff" size="2" face="Arial">Jim.</font></span></div>
<br>
<div dir="ltr" class="OutlookMessageHeader" align="left"
lang="en-us">
<hr tabindex="-1">
<font size="2" face="Tahoma"><b>From:</b> vpn-help
[<a class="moz-txt-link-freetext" href="mailto:vpn-help-bounces@lists.shrew.net">mailto:vpn-help-bounces@lists.shrew.net</a>] <b>On Behalf Of </b>Brian<br>
<b>Sent:</b> Wednesday, September 23, 2015 08:36 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:vpn-help@lists.shrew.net">vpn-help@lists.shrew.net</a><br>
<b>Subject:</b> [vpn-help] Windows 10 - Cisco ASA - DNS Not
Working<br>
</font><br>
</div>
<font face="Tahoma">Hello All.<br>
<br>
I purchased the Shrew VPN client a few weeks ago as I upgraded
my laptop to Windows 10, knowing that the Cisco client does not
work on Windows 10 and I had good success using the free Shrew
version on my tablet that had Windows 8.<br>
<br>
The endpoint of the network I am trying to link in to is a Cisco
ASA (unsure of model). Using Windows 7 and the Cisco client, I
could connect and access anything on the other end using IP or
DNS names.<br>
<br>
Using Shrew though, I can connect to the VPN and ping things on
the other side of the network. I can access things using IP
addresses and I can also access servers using DNS names but ONLY
if the server has no public DNS already. Any server that has a
public DNS seems to get resolved by my router at my house and is
not sent over the tunnel. In many cases, we have a public DNS
to a server that people might use for FTP connectivity, but I
may want to RDP in to that server from the VPN side of things.
But, when I connect to the VPN and then try and RDP, I get the
public IP of the server and thus the RDP fails to connect.<br>
<br>
I've tried lots of combinations of Split DNS, forcing DNS
servers, and policy setups and nothing seems to force the VPN to
be the first option for DNS lookup. I would even be OK with
routing ALL the traffic over the VPN if needed, although that is
not optimal, I know.<br>
<br>
Does anyone have suggestions on what might be causing the VPN to
not be the default for lookups like the Cisco VPN client was
doing?<br>
<br>
Thanks for any help you can provide!<br>
</font>
</blockquote>
<br>
</body>
</html>