Jump to content

Update EIS failed with VYPRvpn


bernx
 Share

Recommended Posts

I've attached a ZIP archive to this message called traceroute_batch_file.zip which contains a batch file that will run some checks to see if your computer can connect to our update servers. Please save this ZIP archive somewhere easy to find (such as on your desktop), and then right-click on it and select to extract it. After extracting it, connect your VPN, then find the file called traceroute_emsisoft_update_servers (it may be in a new folder that was created when extracting the traceroute_batch_file ZIP archive), and right-click on the traceroute_emsisoft_update_servers file and select to Run as administrator.

traceroute_batch_file.zip

Usually the batch file will run for a few minutes, and then a log will open in Notepad. Please save the log somewhere easy to find (such as on your desktop), and then attach it to a reply by using the More Reply Options button to the lower-right of where you type your reply.

Link to comment
Share on other sites

The VPN has a DNS problem. The log shows the attempts to resolve the addresses for our update servers failing.

If you know how to edit the HOSTS file, then that can be used as a simple workaround. Assuming you are connecting to a European VPN, the entries to the HOSTS file should look like the following:

93.184.221.133	dl.emsisoft.com
80.237.191.2	update.emsisoft.com
Regardless of whether you use this workaround or not, the best solution is for the VPN provider to look into what is causing this issue.
Link to comment
Share on other sites

Tested now on "france" and no problem...

did you clear your DNS cache before testing it? when i'm trying w/vyprdns enabled, it fails to resolve dl.emsisoft.com or update.emsisoft.com using nslookup before timing out.

 

@bernx maybe try disabling dns leak protection, reconnecting and seeing if it works after that (you can try it w/either VyprDNS or another DNS provider specified)

Link to comment
Share on other sites

did you clear your DNS cache before testing it? when i'm trying w/vyprdns enabled, it fails to resolve dl.emsisoft.com or update.emsisoft.com using nslookup before timing out.

Flashed... no problem as before... I must be the only one for which it works :D

Link to comment
Share on other sites

Flashed... no problem as before... I must be the only one for which it works :D

if you run nslookup dl.emsisoft.com from cmd, what dns server does it say it's using? i'm wondering if the vpn client isn't properly pushing a DNS server. when i looked at @bernx's dns batch test result, it seems like it's trying to reach the DNS server on their LAN (192.168.0.254) - if you specified a local dns cache (say, the IP address of your router, if it's running as a local forward resolver) i wonder if it would fail as well. in my case, it's failing because windows prefers IPv6 in all cases, and VyprVPN breaks IPv6 connectivity when you connect to prevent IP leakage.

 

@bernx if you go into windows adapter settings on either computer and specify IPv4 DNS servers of 208.67.222.222/208.67.220.220 and reconnect to the vpn, does it work then?

Link to comment
Share on other sites

if you run nslookup dl.emsisoft.com from cmd, what dns server does it say it's using? i'm wondering if the vpn client isn't properly pushing a DNS server. when i looked at @bernx's dns batch test result, it seems like it's trying to reach the DNS server on their LAN (192.168.0.254) - if you specified a local dns cache (say, the IP address of your router, if it's running as a local forward resolver) i wonder if it would fail as well. in my case, it's failing because windows prefers IPv6 in all cases, and VyprVPN breaks IPv6 connectivity when you connect to prevent IP leakage.

 

@bernx if you go into windows adapter settings on either computer and specify IPv4 DNS servers of 208.67.222.222/208.67.220.220 and reconnect to the vpn, does it work then?

nslookup fails but it seems that it not a good way to test as everything works fine (EIS updates without problems and from ipconfig all is configured as intended).

post-34417-0-51088700-1449943616_thumb.jpg

post-34417-0-04266400-1449943625_thumb.jpg

post-34417-0-81237700-1449943632_thumb.jpg

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...