nedfunnell
Senior member
I'm on the end of a long DSL connection, and while my speed test results come back okay, it often takes a long time to connect. This is what I get for a tracert:
I'm on the end of a long DSL connection, and while my speed test results come back okay, it often takes a long time to connect. This is what I get for a tracert:
![]()
pathping www.google.com
I'm on the end of a long DSL connection, and while my speed test results come back okay, it often takes a long time to connect. This is what I get for a tracert:
![]()
That looks like double nat going on (192.168.2.1 in to 192.168.1.254) remove the second router or put the modem in to bridge mode. I don't quite agree that the ISP is queueing here. adsl-184-148-97-1.... is his modems public ip and the high latency is to the next hop 70.159.232.59 which generally indicates transmission issues or retrains in the DSL line. Basically the DSL circuit is struggling but once it is past that, everything looks normal. Your DSL line needs to be looked at by support.
Even with the double NAT, the connection isnt crappy until it reaches the ISP. Definitely worth calling out a support tech.