Re: Problem with SOUP and cable ISP

From: Allen Scott-Thoennes (sthoenna@efn.org)
Date: Mon, 15 Sep 1997 21:00:37 -0700

In article <wIUH0Umo3M7K092yn@mcs.com>, bobr@mcs.com (Robert P. Rush) wrote:
>Hello Gerry and fellow Yarners,
>
>On Sun, 14 Sep 97 22:57:05 -0800,
>In article <97Sep15.015122-0400_edt.342473-16045+3053@mail.bc.rogers.wave.ca>,
>"Gerry Britton" <gbritton@mail.bc.rogers.wave.ca> wrote:
>> I'm having serious probs using VSOUP with my ISP. I'm on a 7/24 cable
>> modem hookup. VSOUP usually just reboots the system after reaching
>> the ISP, but at least once it's given me this:
>>
>> ill URL gbritton
>>
>> SOUPER works, but often chokes part way through a fetch, just sitting
>> there like a lump. I usually have to unsubscribe a group, then
>> subscribe again.
>>
>> Other command line Usenet utilities sometimes report strangely, like
>> "no slave processes allowed", or some such(it's difficult to capture
>> these, as a proggie exits after returning these).
>>
>> Undoubtedly it's the ISP's setup :) However I'd like some ammunition
>> to use with the ISP. Any hints or suggestions?
>
>It definitely sounds like problems on the ISPs end.
>
>I assume you tried testing other protocols (ftp, http (web), smtp
>(send mail), pop3 (get mail), and telnet) with both their site and
>other sites, and that those all work.

[lots of helpful stuff snipped]

>I could add code to Souper to write a log file for the communications
>between Souper and their NNTP server. Perhaps the same could be done
>for vSoup. This log file could then be checked for discreptencies in
>the NNTP protocol.

Hmmm. Just going to throw out a few random guesses/questions based on the
above. I assume that since unsubscribing and subscribing to a group
seems to affect souper that it is actually a news problem and that
it is not choking while getting mail. Is this in fact always the case?
Is it possible you are using the same newsrc file for vsoup/souper as for
yarn and the isp's server is (inappropriately) choking on (to it) bizarre
article numbers?
Hardy or Bob, could you send a list of the actual nntp commands that
your programs go through up through the point of fetching the first article
and Gerry could try them through a telnet session and post the results (i.e.
incoming and outgoing data)? That way we could at least see what kind of
nntp server we are dealing with. Hardy, does the above "ill URL" message
come from vsoup? If not, is it possible (horror of horrors) that the
1SP could be running a http server on the std nntp port 119!?
I'm afraid none of the above will be of any help, but it never hurts to try.

-- 
I am not the sort of person that goes to bed
at night thinking, "Gee, I wonder what I can
do to make life difficult for systems
administrators." -Eric Allman, author:sendmail