Subject:
|
Re: Sluggish nntp performance
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Sun, 10 Oct 1999 17:51:00 GMT
|
Reply-To:
|
jsproat@io.NOSPAMcom
|
Viewed:
|
328 times
|
| |
|
|
Todd Lehman wrote:
> As far as I can tell, it's some sort of ISP networking traffic thing...?
> Pinging www.lugnet.com reports "Request timed out" at the sames times that
> pinging www.pair.com reports the same, while pinging other sites like
> www.yahoo.com and www.netscape.com report normal replies. What do you see
> when you ping?
traceroute was taken during ho-hum performance; I'll take another one during
really flaky performance.
<PING>
c:\pub>ping lugnet.com
Pinging lugnet.com [209.68.63.236] with 32 bytes of data:
Reply from 209.68.63.236: bytes=32 time=60ms TTL=244
Reply from 209.68.63.236: bytes=32 time=50ms TTL=244
Reply from 209.68.63.236: bytes=32 time=60ms TTL=244
Reply from 209.68.63.236: bytes=32 time=51ms TTL=244
</PING>
And a traceroute. NOTE: Novell router addresses kifed by paraoid policy of
Novell IS&T.
<TRACEROUTE>
c:\pub>tracert lugnet.com
Tracing route to lugnet.com [209.68.63.236]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms #############.###.novell.com [137.65.###.###]
2 <10 ms <10 ms <10 ms #############.###.novell.com [137.65.###.###]
3 <10 ms <10 ms <10 ms #############.###.novell.com [137.65.###.###]
4 <10 ms <10 ms <10 ms #############.###.novell.com [137.65.###.###]
5 <10 ms <10 ms 10 ms Serial5-1-1.GW1.SLT1.ALTER.NET
[157.130.162.77]
6 <10 ms <10 ms 10 ms 137.39.167.101
7 <10 ms <10 ms 10 ms 195.ATM2-0.TR1.SLT3.ALTER.NET [146.188.224.2]
8 41 ms 50 ms 50 ms 113.ATM6-0.TR1.DCA1.ALTER.NET
[146.188.137.209]
9 40 ms 50 ms 50 ms 199.ATM7-0.XR1.DCA1.ALTER.NET
[146.188.161.133]
10 50 ms 70 ms 70 ms 193.ATM8-0-0.GW1.PIT1.ALTER.NET
[146.188.162.81]
11 50 ms 61 ms 60 ms pairnetworks-gw.customer.ALTER.NET
[157.130.32.178]
12 * * * Request timed out.
13 60 ms 60 ms 61 ms lugnet.com [209.68.63.236]
Trace complete.
</TRACEROUTE>
That router #12 always times out. I'm sure it just means that it's set up to
not respond to ping from outside the firewall...
LUGNET.COM responds to ping fairly quickly, as always.
> p.s. HTTP, unlike NNTP, is stateless, so it's a lot easier for NNTP
> connections to drop and cause headaches than HTTP. Your web browser might
> also have higher TCP/IP timeouts or latency tolerances than your newsreader.
Hmmm... I haven't thought of this. Monday when I'm at work again, I'll put a
packet sniffer on it and see if I'm getting a lot of timeouts...
Cheers,
- jsproat
--
Jeremy H. Sproat <jsproat@io.com> ~~~ http://www.io.com/~jsproat/
Jeremy: "Hi, My name is Jeremy Sproat, and I'm a...Slashdot Lemming."
All: "Hi, Jeremy."
|
|
Message has 2 Replies:
 | | Re: Sluggish nntp performance
|
| (...) traceroute taken during bad performance showed about the same times. <TRACEROUTE> c:\pub>tracert lugnet.com Tracing route to lugnet.com [209.68.63.236] over a maximum of 30 hops: 1 <10 ms <10 ms <10 ms ###...###.###.novell.com [137.65.###.###] (...) (25 years ago, 11-Oct-99, to lugnet.admin.general)
| | | Re: Sluggish nntp performance
|
| Time to connect is now up to 38 seconds. Doesn't seem to ever be better or worse, consistently 30+ seconds. Tracert looks pretty good, 6 alter.net routers to pairnetworks and they pass through very quick. Losing about 10% of the packets pinging (...) (25 years ago, 11-Oct-99, to lugnet.admin.general)
|
Message is in Reply To:
| | Re: Sluggish nntp performance
|
| (...) Something really net.weird is going on today, but I don't see special notices at Pair yet: (URL) I'm seeing when I look inward from the outside is lots and lots of packet drops and broken connections. Yesterday was bad too, but today is really (...) (25 years ago, 8-Oct-99, to lugnet.admin.general)
|
42 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
