Jump to content
Not connected, Your IP: 34.201.121.213

Recommended Posts

AirVPN,

 

I'm having trouble connecting to certain sites using the VPN service.

 

For example, I'm trying to connect to DesignShack.net but I can't seem to do it with the AirVPN Client running.
I have no problem connecting to the site if I'm not running the AirVPN Client.

I've tried the following trouble shooting steps.

 

1) Add other DNS Servers to the airvpn client

   - Error went from DNS_PROBE_FINISHED_NXDOMAIN to Connection Timeout error

 

2) Turn on/off IPv6

 

3) Add other DNS Servers to Wifi network adapter settings.

   - Same as 1)

 

4) Added AirVPN Dns servers on top of the previously added DNS Servers on both AirVPN Client & Wireless adapter.

  - Same as 1)

 

5) Ping Designshack.net

  - Request Timeout errors. 

 

I would say this happens to 3-5% of the sites I'm visiting.

 

I'm running OS X 10.10.5.

I have Network lock turned on, not running any proxies.

 

Any ideas or suggestions would be heartily welcomed.

Thanks in advance.

 

----------------------

 

Log file entries follows :
 

I 2016.05.12 13:25:16 - AirVPN client version: 2.10.3 / x86, System: OSX, Name: 10.10.5 / x64
. 2016.05.12 13:25:17 - Reading options from /Users/FrancisChung/.airvpn/AirVPN.xml
. 2016.05.12 13:25:17 - Data Path: /Users/FrancisChung/.airvpn
. 2016.05.12 13:25:17 - App Path: /Applications/AirVPN.app/Contents/MacOS
. 2016.05.12 13:25:17 - Executable Path: /Applications/AirVPN.app/Contents/MacOS/AirVPN
. 2016.05.12 13:25:17 - Command line arguments (0):
. 2016.05.12 13:25:17 - Updating systems & servers data ...
. 2016.05.12 13:25:17 - Operating System: Unix 14.5.0.0 - Darwin GAMBIT.local 14.5.0 Darwin Kernel Version 14.5.0: Mon Jan 11 18:48:35 PST 2016; root:xnu-2782.50.2~1/RELEASE_X86_64 x86_64
. 2016.05.12 13:25:17 - Systems & servers data update completed
I 2016.05.12 13:25:18 - OpenVPN Driver - Expected
I 2016.05.12 13:25:18 - OpenVPN - Version: OpenVPN 2.3.8 (/Applications/AirVPN.app/Contents/MacOS/openvpn)
I 2016.05.12 13:25:18 - SSH - Version: OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011 (/usr/bin/ssh)
I 2016.05.12 13:25:18 - SSL - Version: stunnel 5.17 (/Applications/AirVPN.app/Contents/MacOS/stunnel)
! 2016.05.12 13:25:18 - Activation of Network Lock - OS X - PF
. 2016.05.12 13:25:19 - OS X - PF rules updated, reloading
I 2016.05.12 13:25:19 - Session starting.
I 2016.05.12 13:25:20 - IPv6 disabled on network adapter (Wi-Fi)
I 2016.05.12 13:25:20 - IPv6 disabled on network adapter (SAMSUNG_Android)
I 2016.05.12 13:25:20 - IPv6 disabled on network adapter (Bluetooth DUN 2)
I 2016.05.12 13:25:21 - IPv6 disabled on network adapter (Thunderbolt Ethernet Slot 1)
I 2016.05.12 13:25:21 - IPv6 disabled on network adapter (Bluetooth PAN)
I 2016.05.12 13:25:21 - IPv6 disabled on network adapter (Thunderbolt Bridge)
I 2016.05.12 13:25:21 - Checking authorization ...
! 2016.05.12 13:25:22 - Connecting to Velorum (Germany, Frankfurt)
. 2016.05.12 13:25:22 - OpenVPN > OpenVPN 2.3.8 x86_64-apple-darwin14.4.0 [sSL (OpenSSL)] [LZO] [MH] [iPv6] built on Aug 13 2015
. 2016.05.12 13:25:22 - OpenVPN > library versions: OpenSSL 1.0.2d 9 Jul 2015, LZO 2.08
. 2016.05.12 13:25:22 - OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3111
. 2016.05.12 13:25:22 - OpenVPN > Control Channel Authentication: tls-auth using INLINE static key file
. 2016.05.12 13:25:22 - OpenVPN > Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.05.12 13:25:22 - OpenVPN > Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.05.12 13:25:22 - OpenVPN > Socket Buffers: R=[196724->131072] S=[9216->131072]
. 2016.05.12 13:25:22 - OpenVPN > UDPv4 link local: [undef]
. 2016.05.12 13:25:22 - OpenVPN > UDPv4 link remote: [AF_INET]46.165.208.69:443
. 2016.05.12 13:25:22 - OpenVPN > TLS: Initial packet from [AF_INET]46.165.208.69:443, sid=2509709c 0cdbc1e1
. 2016.05.12 13:25:22 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org
. 2016.05.12 13:25:22 - OpenVPN > Validating certificate key usage
. 2016.05.12 13:25:22 - OpenVPN > ++ Certificate has key usage  00a0, expects 00a0
. 2016.05.12 13:25:22 - OpenVPN > VERIFY KU OK
. 2016.05.12 13:25:22 - OpenVPN > Validating certificate extended key usage
. 2016.05.12 13:25:22 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
. 2016.05.12 13:25:22 - OpenVPN > VERIFY EKU OK
. 2016.05.12 13:25:22 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org
. 2016.05.12 13:25:23 - OpenVPN > Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
. 2016.05.12 13:25:23 - OpenVPN > Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.05.12 13:25:23 - OpenVPN > Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
. 2016.05.12 13:25:23 - OpenVPN > Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.05.12 13:25:23 - OpenVPN > Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
. 2016.05.12 13:25:23 - OpenVPN > [server] Peer Connection Initiated with [AF_INET]46.165.208.69:443
. 2016.05.12 13:25:25 - OpenVPN > SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
. 2016.05.12 13:25:25 - OpenVPN > ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address
. 2016.05.12 13:25:25 - 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.6.105 255.255.0.0'
. 2016.05.12 13:25:25 - OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified
. 2016.05.12 13:25:25 - OpenVPN > OPTIONS IMPORT: LZO parms modified
. 2016.05.12 13:25:25 - OpenVPN > OPTIONS IMPORT: --ifconfig/up options modified
. 2016.05.12 13:25:25 - OpenVPN > OPTIONS IMPORT: route options modified
. 2016.05.12 13:25:25 - OpenVPN > OPTIONS IMPORT: route-related options modified
. 2016.05.12 13:25:25 - OpenVPN > OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
. 2016.05.12 13:25:25 - OpenVPN > Opened utun device utun0
. 2016.05.12 13:25:25 - OpenVPN > do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
. 2016.05.12 13:25:25 - OpenVPN > /sbin/ifconfig utun0 delete
. 2016.05.12 13:25:25 - OpenVPN > NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
. 2016.05.12 13:25:25 - OpenVPN > /sbin/ifconfig utun0 10.4.6.105 10.4.6.105 netmask 255.255.0.0 mtu 1500 up
. 2016.05.12 13:25:25 - OpenVPN > /sbin/route add -net 10.4.0.0 10.4.6.105 255.255.0.0
. 2016.05.12 13:25:25 - OpenVPN > add net 10.4.0.0: gateway 10.4.6.105
. 2016.05.12 13:25:25 - OpenVPN > /sbin/route add -net 46.165.208.69 192.168.2.1 255.255.255.255
. 2016.05.12 13:25:25 - OpenVPN > add net 46.165.208.69: gateway 192.168.2.1
. 2016.05.12 13:25:25 - OpenVPN > /sbin/route add -net 0.0.0.0 10.4.0.1 128.0.0.0
. 2016.05.12 13:25:25 - OpenVPN > add net 0.0.0.0: gateway 10.4.0.1
. 2016.05.12 13:25:25 - OpenVPN > /sbin/route add -net 128.0.0.0 10.4.0.1 128.0.0.0
. 2016.05.12 13:25:25 - OpenVPN > add net 128.0.0.0: gateway 10.4.0.1
. 2016.05.12 13:25:25 - Starting Management Interface
. 2016.05.12 13:25:25 - OpenVPN > Initialization Sequence Completed
I 2016.05.12 13:25:25 - DNS of a network adapter forced (Wi-Fi)
I 2016.05.12 13:25:26 - DNS of a network adapter forced (SAMSUNG_Android)
I 2016.05.12 13:25:26 - DNS of a network adapter forced (Bluetooth DUN 2)
I 2016.05.12 13:25:26 - DNS of a network adapter forced (Thunderbolt Ethernet Slot 1)
I 2016.05.12 13:25:27 - DNS of a network adapter forced (Bluetooth PAN)
I 2016.05.12 13:25:27 - DNS of a network adapter forced (Thunderbolt Bridge)
I 2016.05.12 13:25:27 - Flushing DNS
. 2016.05.12 13:25:28 - OS X - PF rules updated, reloading
I 2016.05.12 13:25:28 - Checking route
! 2016.05.12 13:25:30 - Connected.
. 2016.05.12 13:25:30 - OpenVPN > MANAGEMENT: Client connected from [AF_INET]127.0.0.1:3111
. 2016.05.12 13:25:30 - OpenVpn Management > >INFO:OpenVPN Management Interface Version 1 -- type 'help' for more info
 

 

Share this post


Link to post

I have just tried Menkab (Sweden) and I can get to DesignShack.net.

However, using Velorum (Germany) and I can't seem to get through, 
The plot thickens ....

Share this post


Link to post

Thanks Zhang888.

 

It looks like routing to DesignShack is failing on couple of AirVPN servers.

Why would the routing fail on some servers and work on others?

Share this post


Link to post

Thanks Zhang888.

 

It looks like routing to DesignShack is failing on couple of AirVPN servers.

 

Why would the routing fail on some servers and work on others?

 

perhaps they've blocked IP address ranges that include some AirVPN servers.

Share this post


Link to post

see if the air vpn can't connect to your device then it might be that there is some problem in the dns of your device...to which tech geeks generally call "dns_probe_finished_nxdomain" problem well you are encountering the problem because of dns problem...no need to worry i very esy to resolve it...just solve the given steps in the article : http://errorcodespro.com/error-code-dns_probe_finished_nxdomain/

 

Share this post


Link to post
The reason for DNS_PROBE_FINISHED_NXDOMAIN is typically due to a misconfiguration or problem with your DNS. DNS is short for Domain Name System, which helps direct traffic on the internet by connecting domain names with actual web servers. Essentially, it takes a human-friendly request – a domain name like kinsta.com – and translates it into a computer-friendly server IP address – like 216.3.128.12.

 

When a user enters a URL in their web browser, DNS gets to work to connect that URL to the IP address of the actual server. This is called DNS name resolution and involves a DNS recursor querying various nameservers to figure out the actual IP address of a server. If DNS fails to resolve the domain name or address then you might receive the DNS_PROBE_FINISHED_NXDOMAIN error

 

There are simple steps that can lead to solving these problems. It is likely that you would not require any expert help because you can perform many of these techniques by yourself. The following are some of the steps you can adopt for solving the error DNS_PROBE_FINISHED_NXDOMAIN:

 

Alter the DNS IP address

Flushing the DNS

Restarting the DNS Client

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Security Check
    Play CAPTCHA Audio
    Refresh Image

×
×
  • Create New...