|
Re: ping and tracert networking question
It could be DNS resolution. Most implementations of tracert will attempt to resolve each IP along the way, and this can take a long time with a flaky DNS server.
A couple suggestions:
a) Try running tracert with the -d flag (Windows) or -n (Linux).
b) Try using an open DNS service, like OpenDNS (208.67.222.222/208.67.222.220) or Google Public DNS (8.8.8.8/8.8.4.4).
Last edited by Jared Russell : 21-11-2013 at 22:25.
Reason: Clarified that -d is only for Windows
|