Hey All.....
Want to thank everyone for the help here with my issue, however I got it corrected, just installed my new fios router and had to call fios support to get it activated. There was something on the connection itself that prevented the new router from activating, once the fios tech reset my internet connection (and after explaining the issue to him) he was well aware of the problem of tracert dropping after iad8.alter.net (i didnt even tell him where it stopped as he knew it right off the top of his head). Once my connection was reset and my fios router initialized, aol.com took about 1.5 sec to load up on ie and now i can run a tracert all the way to net.aol.com (11 hops).
Thanks again all
Rov
I'm glad you got it sorted out and thanx for the update.
Glad to hear it's fixed!
The reason why I suggested a trace to both aol.com and www.aol.com is due to the way they have the DNS records configured. They point to different servers so to speak, and one of the records has an AAAA (IPv6) record associated with it. I'm simply accounting for both user situations. Now as for ping, I simply asked for that since in some cases, you can ping websites but cannot trace them.
Start a new topic or ask questions in the open forum.
