John said:
I'm getting used to the false appearance that my post was not
posted. But in fact the post almost always shows up having been
posted. So of course I check before clicking the "send" button
again. Seems to be occurring much more frequently lately. I guess
it might be a local problem.
Not a big deal, mostly curious.
Post to eternal-september.support . The admin isn't going to
see your complaint, if you just put it here.
The server actually has a few problems. One other problem,
is something happens to network connections at a particular
hour of the day. This results in a claim that you have made
"multiple connections", when you haven't made any connections
with your current IP address. This seemed to happen after the
server config was fixed up a little bit, to make it "DNS clean"
some time ago.
I've run into your "post timeout" thing recently, but only
the one time. Post was actually accepted, but appeared to fail
as far as my newsreader was concerned. Later, I could see the
post had made it to the server. It's not happening enough for
me to complain about it. If it's reproducible on your end,
that'll make it easier for "Ray Banana" to check
the logs and see your attempts.
Your newsreader doesn't maintain a constantly-open
connection to the server at all times. After a short
timeout period, the connection (and authentication)
is dropped. When you post, either you're currently connected,
or no connection is present, and then the whole login process
has to happen before the post will happen. You can watch
this with a packet sniffer (Wireshark). When I have a problem
with a post, I check the Wireshark log, and see what packets
were sent and received, to E-S port 119. So when I eventually
get off my lazy ass and complain to Ray, I usually include
whatever trace I have in the packet sniffer. Usually, Ray
doesn't need that info, to figure it out. So his logs are
pretty good at his end. But posting the stuff, makes me
feel better.
Paul
