You will see a program listed "Internet Explorer (No Add-ons)". From your Run/Search window, type in "Internet Explorer". But quickly, let's eliminate all problems with IE11. If you don't have another one installed, you probably should. The advice to try another web browser, have you taken that? What I ultimately suspect as the problem is something much more closer to home. They are sometimes able to reroute in the event of an upstream provider outage, but this takes more than what a home internet connection helpdesk person can do and is usually automatically executed.
There is very little that your provider can do to resolve latency issues on networks outside of their control. Of course as you found out, the destination doesn't allow pings all the way to their website.Īlso, your ISP (and the others above me) are correct. The correct tool to use is ping to determine latency and packet loss. This is proven when you have mid-router RTT times which is greater than the ultimate RTT time to the destination, unless of course you believe in time travel. Traffic destined TO them (like those ping packets) has a much lower priority for processing since that is not their main job and this will be reflected in the RTT time. Routers are highly efficient in passing traffic through them. The problem you're having could very well be due to a problem on the ingress path and traceroute can not indicate that.Ģ) Mid-hop RTTs (Round Trip Time) are misleading and high RTT values very rarely indicate an actual problem. The direction data takes from the website to you is quite different.
Given that you were able to resolve not only the website addresses, but all the intermediate router IP addresses, looks like DNS is working just fine to me.įurthermore, traceroute is generally a terrible tool because it is easily misunderstood:ġ) It only shows the path taken in one direction. This is a valid solution IF the DNS servers you have listed are having problems. I agree - different DNS servers won't make a difference.
0 kommentar(er)
