<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23588"></HEAD>
<BODY bgColor=#ffffff text=#000000>
<DIV dir=ltr align=left><FONT color=#0000ff size=2
face=Arial></FONT> </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><FONT color=#0000ff
size=2 face=Arial></FONT></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 lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> vpn-help
[mailto:vpn-help-bounces@lists.shrew.net] <B>On Behalf Of
</B>Brian<BR><B>Sent:</B> Wednesday, September 23, 2015 08:36 AM<BR><B>To:</B>
vpn-help@lists.shrew.net<BR><B>Subject:</B> [vpn-help] Windows 10 - Cisco ASA -
DNS Not Working<BR></FONT><BR></DIV>
<DIV></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></BODY></HTML>