 | | Re: Sluggish nntp performance
|
|
(...) Oof. I shoulda seen that one! :-, What does the 115M mean? 155 megabits per second? Cheers, - jsproat (25 years ago, 13-Oct-99, to lugnet.off-topic.geek)
|
| |
| | Re: Sluggish nntp performance
|
|
(...) nslookup. It's prettier than 'host', but tells you basically the same thing. I got the 155M out of the hostname. It's nice when people name their routers meaningfully. :) (25 years ago, 13-Oct-99, to lugnet.admin.general, lugnet.off-topic.geek)
|
| |
| | Re: Sluggish nntp performance
|
|
Sorry, bad choice of words in that last post. I knew that the problem wasn't at your end. -- Scott Smallbeck scotts@contactics.com (URL) Lehman <lehman@javanet.com> wrote in message news:3804b7b9.795349...net.com... (...) now (...) (25 years ago, 13-Oct-99, to lugnet.admin.general, lugnet.off-topic.geek)
|
| |
| | Re: Sluggish nntp performance
|
|
(...) It's not LUGNET's NNTP performance that you're having touble with. It's some net clog problem somewhere. Maybe multiple problems. --Todd (25 years ago, 13-Oct-99, to lugnet.admin.general, lugnet.off-topic.geek)
|
| |
| | Re: Sluggish nntp performance
|
|
(...) What tool do you use for that? whois comes up with a blank, and host (1) just says "pos3-1-155M.cr1.JFK...nter.net". Anyway, my packets don't even see that network -- they get stuck somewhere between: 6 <10 ms 10 ms <10 ms (...) (25 years ago, 13-Oct-99, to lugnet.admin.general, lugnet.off-topic.geek)
|
