Agent Premium News Server stalls
QX
I noticed it starting a couple of weeks ago. Seems to be getting
a bit worse also.
I retrieve my headers OK, but once I start D/L bodies,
I get a few, then everything stops dead.
To get things going again, I have to close Agent, and then
request the bodies again. I'll get a few message bodies, then the
server seems to stall again. Very frustrating. It affects binaries &
text groups.
My net connection is good, since I can use my browser without a
problem while APN is stalled.
Agent 4.32
TIA
Rich Webb
It could be a load problem at the server (APN resells EasyNews).
It could also be a bottleneck somewhere between your machine and the
news server that doesn't affect browsing to other sites (that may not
use the route with the bottleneck).
If it's a network problem, one tool (among several, of course) that you
can use is http://www.pingplotter.com/. They have a free version that
gives you a snapshot of the ping latency to a target machine as well as
an inexpensive licensed version that includes plots of the routes over
time.
FWIW, I'm not seeing any particular issues with APN at this time. There
was a period several weeks ago when things were a bit bumpy but it's
clean now, here.
--
Rich Webb Norfolk, VA
Nicetameetya
[Default] On Wed, 04 Nov 2009 05:31:36 -0800, QX <nom...@nospam.com>
declared to all and sundry:
It's part of the ongoing problems APN has been experiencing since they
hooked up with Easynews. It's also the reason I dumped APN after being
with them for years. All Fort� will tell you is: "Sorry. We're working
on it." After hearing that long enough you'll probably dump them too.
nob...@somewhere.zzz
Me, too. I switched to Giganews 6 months ago, and couldn't be
happier. And, Giganews has much longer binary retention, over a year.
Nicetameetya
[Default] On Wed, 11 Nov 2009 05:21:13 +0000, Ian Anderson
<an...@127.0.0.1.invalid> declared to all and sundry:
>On Wed, 04 Nov 2009 05:31:36 -0800, QX <nom...@nospam.com> wrote:
>
>>Any idea why the APN server is stalling?
>>I noticed it starting a couple of weeks ago. Seems to be getting
>>a bit worse also.
>>I retrieve my headers OK, but once I start D/L bodies,
>>I get a few, then everything stops dead.
>
>Because of my TimeZone (Eastern Australia) I have little trouble.
>
>>To get things going again, I have to close Agent, and then
>>request the bodies again. I'll get a few message bodies, then the
>>server seems to stall again. Very frustrating. It affects binaries &
>>text groups.
>>My net connection is good, since I can use my browser without a
>>problem while APN is stalled.
>
>While you maybe asleep I could be downloading messages or replying.
And I'm in New Zealand. But APN's unreliable, inconsistent and
unacceptable timeouts and repeated errors led to me canceling my
account and changing to a provider that was FAR more reliable.
Nicetameetya
[Default] On Thu, 12 Nov 2009 05:00:28 +0000, Ian Anderson
<an...@127.0.0.1.invalid> declared to all and sundry:
>On Wed, 11 Nov 2009 21:01:15 +1300, Nicetameetya <gd...@invalid.invalid>
>wrote:
>So "individual.net" they are often highly recommended, I'll keep them in
>mind if I start having regular problems with APN.
After trying out Giganews and Astraweb I chose Individual.net and have
been using them for text newsgroups ever since.
QX
<gd...@invalid.invalid> wrote:
Agent folks have said they are getting no reports of problems from
anyone else, yet my service is still stalling. He said it's probably
my path, but when I encounter a stall, I ping them and get excellent
times, no losses, over and over again.
ping news20.forteinc.com
Pinging forte.easynews.com [69.16.186.50] with 32 bytes of data:
Reply from 69.16.186.50: bytes=32 time=83ms TTL=59
Reply from 69.16.186.50: bytes=32 time=105ms TTL=59
Reply from 69.16.186.50: bytes=32 time=102ms TTL=59
Reply from 69.16.186.50: bytes=32 time=93ms TTL=59
Ping statistics for 69.16.186.50:
Packets: Sent = 4, Received = 4, Lost = 0 <0% Loss>,
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 105ms, Average = 95ms
The above is typical of what I get when the server seems to be
stalled. I can ping over and over and over and all the results are
about the same.
Steve Urbach
I suspect port blocking or traffic shaping on port 119 since the route is open
otherwise. :/
Geoff
no data is flowing. Sessions have partial file downloads on binaries
and then at some random point the session stalls with xx% downloaded.
Sometimes kicking in a priority article download with the enter key
can wake things up. The new session at least completes without
problems even if the other one is still stalled.
AFAIK, Verizon is not shaping NNTP for FiOS customers.