Hi Tony,
The last time I could do a tracert (Denial of Service attacks have caused most admins to shut off ping responses and I haven't been able to do a clean tracrt for a couple of years) from here to cnn.com there was 28 hops.
The last time I actually worked on this stuff was long before the term "Denial of Service" was conjured up... <g>
Seriously, it's been 4 to 5 years now since I worked in technology, and I'm sure advances have been made since I left. However, some things never change. When I left, no one was making any actual changes to TCP because "the newer stuff will obsolete TCP"... Well, that was 5 years ago now, and TCP is still around, and it's not much improved since then... So when I spoke of noise, noise was the more serious problem 5 years ago. I'll take your good word for it that changes due to DoS is a bigger problem today. <ggg>
Back to the other guy's problems... If he can access using a dial-up with no problems, and using ADSL he's getting truncation errors, then the places to search for problems are quite narrowed. I'd first check out the router on my system and make sure that I don't have an incorrect buffer default setting somewhere. Presuming that everything is okay on the home system, the next most likely place for problems is with the default settings on the ADSL account. Usually these settings can be modified, and it's the most likely source for a truncation problem. If the ADSL account is okay, then it's possible that the ISP provider has an internal problem in its own system or router. And lastly, the problem could be congestion or noise. But congestion and noise could/would be somewhat random in nature and the poster should "see" random problems. For example, this transmission was truncated at say 500 characters and the next one went to 1770 characters before it died. Then back to 1000 and so on. If he's consistently being truncated at the the exact same spot (or character) in his post(s), then a buffer setting is a far more likely cause.
KJC
EDIT: Grub... Double Zero... |
