Jump to content

Vsd Update Issues With Verizon Fios Customers


Recommended Posts

Have had a few customers over the last week who are getting Failed VSD updates after installing ESET. The pattern is Verizon FiOS connections. Speedtest shows very fast connections.  After I put in a static DNS like 8.8.8.8 the updates do eventually go through but it takes about 10-15minutes. On my last customer I did a pathping and we are getting 100% loss after it hits one of the Slovaktelekom servers. Strange that it updates but is FIOS possibly have blacklisted some of these servers by mistake or because they are in Slovakia and think that customers are hitting these servers to download illegal content or other material?  Below is the pathping results. The losses are in RED.  

 

Computing statistics for 300 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           eric-PC.home [192.168.1.7]
                                0/ 100 =  0%   |
  1   69ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                0/ 100 =  0%   |
  2  110ms     0/ 100 =  0%     0/ 100 =  0%  L100.RCMDVA-VFTTP-08.verizon-gni.n
et [71.251.232.1]
                                0/ 100 =  0%   |
  3   91ms     0/ 100 =  0%     0/ 100 =  0%  G0-0-1-0.RCMDVA-LCR-21.verizon-gni
.net [130.81.58.60]
                                0/ 100 =  0%   |
  4   80ms     0/ 100 =  0%     0/ 100 =  0%  so-0-1-0-0.RES-BB-RTR1.verizon-gni
.net [130.81.199.56]
                                0/ 100 =  0%   |
  5   75ms     0/ 100 =  0%     0/ 100 =  0%  0.ae5.XL1.IAD8.ALTER.NET [152.63.8
.121]
                                0/ 100 =  0%   |
  6   69ms     0/ 100 =  0%     0/ 100 =  0%  0.xe-10-3-0.GW9.IAD8.ALTER.NET [15
2.63.41.246]
                                0/ 100 =  0%   |
  7   83ms     1/ 100 =  1%     1/ 100 =  1%  tinet-gw.customer.alter.net [152.1
79.50.30]
                                0/ 100 =  0%   |
  8  194ms     0/ 100 =  0%     0/ 100 =  0%  ge-5-1-0.bts10.ip4.gtt.net [141.13
6.107.138]
                                0/ 100 =  0%   |
  9  218ms     0/ 100 =  0%     0/ 100 =  0%  slovaktelekom-gw.ip4.gtt.net [141.
136.101.110]
                                0/ 100 =  0%   |
 10  ---     100/ 100 =100%   100/ 100 =100%  st-static-srk110.87-197-254.teleco
m.sk [87.197.254.110]
                                0/ 100 =  0%   |
 11  ---     100/ 100 =100%   100/ 100 =100%  st-static-srk110.87-197-254.teleco
m.sk [87.197.254.110]

                                0/ 100 =  0%   |
 12  209ms     0/ 100 =  0%     0/ 100 =  0%  um04.eset.com [91.228.166.16]

Trace complete.

Link to comment
Share on other sites

Do you get the same results using a different DNS ?

Try OpenDNS and let us know results.

 

  • 208.67.222.222
  • 208.67.220.220

What about the ISP's DNS servers ?

Link to comment
Share on other sites

Do you get the same results using a different DNS ?

Try OpenDNS and let us know results.

 

  • 208.67.222.222
  • 208.67.220.220

What about the ISP's DNS servers ?

did not have enough time with customer to try out other DNS'. Once the update went through finally he had to continue with his work.  The DNS I had at the time when I did the pathping was Google's  8.8.8.8. It failed to update with this AUTO DNS from NIC.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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