No Remote names could be resolved

[KelDG 0]

Been having trouble for the past week and still cant figure out what the problem is

 

When I try to connect I get the error  "W 2016.12.24 19:08:28 - The remote name could not be resolved: 'maasym_exit.airservers.org'"

 

This happens for all servers, it happens after "checking route" has been running for a while, if I disable checking route it does it after "Checking DNS" has been running for a while.  If I install Air on my other PC it connects fine.

 

I have tried all at the same time uninstalling AIR client fully / uninstalling TAP driver / Doing a winsock reset, but when I reinstall I get the same problem.  Any ideas what I could do change etc?

 

This is my error log with check route disabled

 

I 2016.12.24 19:07:32 - AirVPN client version: 2.10.3 / x86, System: Windows, Name: Microsoft Windows NT 6.2.9200.0 / x64
. 2016.12.24 19:07:32 - Reading options from C:\Users\Kel\AppData\Local\AirVPN\AirVPN.xml
. 2016.12.24 19:07:33 - Data Path: C:\Users\Kel\AppData\Local\AirVPN
. 2016.12.24 19:07:33 - App Path: C:\Program Files (x86)\AirVPN
. 2016.12.24 19:07:33 - Executable Path: C:\Program Files (x86)\AirVPN\AirVPN.exe
. 2016.12.24 19:07:33 - Command line arguments (1): path="home"
. 2016.12.24 19:07:33 - Operating System: Microsoft Windows NT 6.2.9200.0
. 2016.12.24 19:07:33 - Updating systems & servers data ...
. 2016.12.24 19:07:33 - Systems & servers data update completed
I 2016.12.24 19:07:33 - OpenVPN Driver - TAP-Windows Adapter V9, version 9.21.1
I 2016.12.24 19:07:33 - OpenVPN - Version: OpenVPN 2.3.8 (C:\Program Files (x86)\AirVPN\openvpn.exe)
I 2016.12.24 19:07:33 - SSH - Version: plink 0.63 (C:\Program Files (x86)\AirVPN\plink.exe)
I 2016.12.24 19:07:33 - SSL - Version: stunnel 5.17 (C:\Program Files (x86)\AirVPN\stunnel.exe)
! 2016.12.24 19:07:33 - Ready
I 2016.12.24 19:07:53 - Session starting.
I 2016.12.24 19:07:54 - IPv6 disabled.
I 2016.12.24 19:07:54 - Checking authorization ...
! 2016.12.24 19:07:54 - Connecting to Maasym (Netherlands, Alblasserdam)
. 2016.12.24 19:07:54 - OpenVPN > OpenVPN 2.3.8 i686-w64-mingw32 [sSL (OpenSSL)] [LZO] [iPv6] built on Aug 13 2015
. 2016.12.24 19:07:54 - OpenVPN > library versions: OpenSSL 1.0.2d 9 Jul 2015, LZO 2.08
. 2016.12.24 19:07:54 - OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3100
. 2016.12.24 19:07:54 - OpenVPN > Control Channel Authentication: tls-auth using INLINE static key file
. 2016.12.24 19:07:54 - OpenVPN > Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.12.24 19:07:54 - OpenVPN > Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.12.24 19:07:54 - OpenVPN > Socket Buffers: R=[65536->131072] S=[65536->131072]
. 2016.12.24 19:07:54 - OpenVPN > UDPv4 link local: [undef]
. 2016.12.24 19:07:54 - OpenVPN > UDPv4 link remote: [AF_INET]213.152.162.103:443
. 2016.12.24 19:07:54 - OpenVPN > TLS: Initial packet from [AF_INET]213.152.162.103:443, sid=0f218df1 e8e60f9c
. 2016.12.24 19:07:54 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org
. 2016.12.24 19:07:54 - OpenVPN > Validating certificate key usage
. 2016.12.24 19:07:54 - OpenVPN > ++ Certificate has key usage  00a0, expects 00a0
. 2016.12.24 19:07:54 - OpenVPN > VERIFY KU OK
. 2016.12.24 19:07:54 - OpenVPN > Validating certificate extended key usage
. 2016.12.24 19:07:54 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
. 2016.12.24 19:07:54 - OpenVPN > VERIFY EKU OK
. 2016.12.24 19:07:54 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org
. 2016.12.24 19:07:56 - OpenVPN > Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
. 2016.12.24 19:07:56 - OpenVPN > Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.12.24 19:07:56 - OpenVPN > Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
. 2016.12.24 19:07:56 - OpenVPN > Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.12.24 19:07:56 - OpenVPN > Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
. 2016.12.24 19:07:56 - OpenVPN > [server] Peer Connection Initiated with [AF_INET]213.152.162.103:443
. 2016.12.24 19:07:58 - OpenVPN > SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
. 2016.12.24 19:07:58 - OpenVPN > PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 10.4.0.1,comp-lzo no,route-gateway 10.4.0.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.4.37.104 255.255.0.0'
. 2016.12.24 19:07:58 - OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified
. 2016.12.24 19:07:58 - OpenVPN > OPTIONS IMPORT: LZO parms modified
. 2016.12.24 19:07:58 - OpenVPN > OPTIONS IMPORT: --ifconfig/up options modified
. 2016.12.24 19:07:58 - OpenVPN > OPTIONS IMPORT: route options modified
. 2016.12.24 19:07:58 - OpenVPN > OPTIONS IMPORT: route-related options modified
. 2016.12.24 19:07:58 - OpenVPN > OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
. 2016.12.24 19:07:58 - OpenVPN > do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
. 2016.12.24 19:07:58 - OpenVPN > open_tun, tt->ipv6=0
. 2016.12.24 19:07:58 - OpenVPN > TAP-WIN32 device [Ethernet 2] opened: \\.\Global\{71DECC24-D9A0-4FFF-BA6D-F20463DE4111}.tap
. 2016.12.24 19:07:58 - OpenVPN > TAP-Windows Driver Version 9.21
. 2016.12.24 19:07:58 - OpenVPN > Set TAP-Windows TUN subnet mode network/local/netmask = 10.4.0.0/10.4.37.104/255.255.0.0 [sUCCEEDED]
. 2016.12.24 19:07:58 - OpenVPN > Notified TAP-Windows driver to set a DHCP IP/netmask of 10.4.37.104/255.255.0.0 on interface {71DECC24-D9A0-4FFF-BA6D-F20463DE4111} [DHCP-serv: 10.4.255.254, lease-time: 31536000]
. 2016.12.24 19:07:58 - OpenVPN > Successful ARP Flush on interface [16] {71DECC24-D9A0-4FFF-BA6D-F20463DE4111}
. 2016.12.24 19:08:03 - OpenVPN > TEST ROUTES: 1/1 succeeded len=0 ret=1 a=0 u/d=up
. 2016.12.24 19:08:03 - OpenVPN > C:\WINDOWS\system32\route.exe ADD 213.152.162.103 MASK 255.255.255.255 192.168.0.1
. 2016.12.24 19:08:03 - OpenVPN > ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=35 and dwForwardType=4
. 2016.12.24 19:08:03 - OpenVPN > Route addition via IPAPI succeeded [adaptive]
. 2016.12.24 19:08:03 - OpenVPN > C:\WINDOWS\system32\route.exe ADD 192.168.0.1 MASK 255.255.255.255 192.168.0.1 IF 7
. 2016.12.24 19:08:03 - OpenVPN > ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=35 and dwForwardType=4
. 2016.12.24 19:08:03 - OpenVPN > Route addition via IPAPI succeeded [adaptive]
. 2016.12.24 19:08:03 - OpenVPN > C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.4.0.1
. 2016.12.24 19:08:03 - OpenVPN > ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=35 and dwForwardType=4
. 2016.12.24 19:08:03 - OpenVPN > Route addition via IPAPI succeeded [adaptive]
. 2016.12.24 19:08:03 - OpenVPN > C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.4.0.1
. 2016.12.24 19:08:03 - OpenVPN > ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=35 and dwForwardType=4
. 2016.12.24 19:08:03 - OpenVPN > Route addition via IPAPI succeeded [adaptive]
. 2016.12.24 19:08:03 - Starting Management Interface
. 2016.12.24 19:08:03 - OpenVPN > Initialization Sequence Completed
I 2016.12.24 19:08:04 - DNS of a network adapter forced (Realtek PCIe GBE Family Controller)
I 2016.12.24 19:08:04 - DNS of a network adapter forced (TAP-Windows Adapter V9)
I 2016.12.24 19:08:04 - Flushing DNS
I 2016.12.24 19:08:04 - Checking DNS
W 2016.12.24 19:08:28 - The remote name could not be resolved: 'maasym_exit.airservers.org'
! 2016.12.24 19:08:28 - Disconnecting
. 2016.12.24 19:08:28 - Management - Send 'signal SIGTERM'
. 2016.12.24 19:08:28 - OpenVPN > MANAGEMENT: CMD 'signal SIGTERM'
. 2016.12.24 19:08:28 - OpenVPN > SIGTERM received, sending exit notification to peer
. 2016.12.24 19:08:28 - OpenVpn Management > >INFO:OpenVPN Management Interface Version 1 -- type 'help' for more info
. 2016.12.24 19:08:33 - OpenVPN > C:\WINDOWS\system32\route.exe DELETE 213.152.162.103 MASK 255.255.255.255 192.168.0.1
. 2016.12.24 19:08:33 - OpenVPN > Route deletion via IPAPI succeeded [adaptive]
. 2016.12.24 19:08:33 - OpenVPN > C:\WINDOWS\system32\route.exe DELETE 192.168.0.1 MASK 255.255.255.255 192.168.0.1
. 2016.12.24 19:08:33 - OpenVPN > Route deletion via IPAPI succeeded [adaptive]
. 2016.12.24 19:08:33 - OpenVPN > C:\WINDOWS\system32\route.exe DELETE 0.0.0.0 MASK 128.0.0.0 10.4.0.1
. 2016.12.24 19:08:33 - OpenVPN > Route deletion via IPAPI succeeded [adaptive]
. 2016.12.24 19:08:33 - OpenVPN > C:\WINDOWS\system32\route.exe DELETE 128.0.0.0 MASK 128.0.0.0 10.4.0.1
. 2016.12.24 19:08:33 - OpenVPN > Route deletion via IPAPI succeeded [adaptive]
. 2016.12.24 19:08:33 - OpenVPN > Closing TUN/TAP interface
. 2016.12.24 19:08:33 - OpenVPN > SIGTERM[soft,exit-with-notification] received, process exiting
. 2016.12.24 19:08:33 - Connection terminated.
I 2016.12.24 19:08:33 - DNS of a network adapter restored to original settings (Realtek PCIe GBE Family Controller)
I 2016.12.24 19:08:33 - DNS of a network adapter restored to original settings (TAP-Windows Adapter V9)
I 2016.12.24 19:08:35 - Cancel requested.
I 2016.12.24 19:08:35 - IPv6 restored.
! 2016.12.24 19:08:36 - Session terminated.
 

 

Thanks

[cm0s 118]

hey KelDG a happy and safe holidays to you

 

was curious on this myself not sure if i found the answer but

 

i did some searching found one post on the forum see if it helps you out at all...

 

https://airvpn.org/topic/20853-the-remote-name-could-not-be-resolved/?hl=%2Bremote+%2Bname+%2Bcould

 

i'm trying to learn 'troubleshooting' logs

 

you know more about windows, eddy your config than i do it does sound like something is goofing your dns up obviously

 

i'll keep checking on this just to see if ya get things fixed if you do please post up your fix coz saw others online same error

 

sincerely,

 

cm0s

[LZ1 662]

Hello!

 

Have you tried different servers and protocols? Alternatively, you could also try the Beta client.

[KelDG 0]

Hello!

 

Have you tried different servers and protocols? Alternatively, you could also try the Beta client.

I don't really understand the different protocols, will try the Beta though, it is something screwy with the client though as OpenVPNGUI connects fine, but I don't like using that as I cant figure out how to get a network lock going on it.

[LZ1 662]

Network Lock is exclusive to the Eddie client .