Don't you just love computers and there consistency?

Just when you are ready to close in on a bug and stomp it out, it goes
into hiding.

I hope your problem stays away.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm


"AHAllen" wrote in message
...
Gentlemen: I have some great (but puzzling) news to report. Yesterday,
to try
to run another log on trying to connect, the connection was made and
newsgroups downloaded! Seems to have started working fine. I waited to
try
again today and again, everything seems to be back to normal. I will,
of
course save all of your suggestions - I printed most of them - in case
the
problem mysteriously comes back. I sincerely appreciate the relentless
help
and suggestions made by each of you! Best regards.... Alex Allen

"vrbancic mario" wrote:


"Robert Aldwinckle" schrieb im Newsbeitrag
...
"AHAllen" wrote in message
...
Mike: I let it time out twice: Below is the log.....

Microsoft Internet Messaging API 6.00.2900.3028
(xpsp_sp2_gdr.061107-0012)
NNTP Log started at 01/13/2007 17:42:35
NNTP: 17:42:35 [db] Connecting to 'msnews.microsoft.com' on port
119.
NNTP: 17:42:35 [db] srv_name = "msnews.microsoft.com" srv_addr =
207.46.248.16
NNTP: 17:42:35 [rx] 200 NNTP Service 6.0.3790.1830 Version:
6.0.3790.1830
Posting Allowed
NNTP: 17:42:35 [tx] MODE READER


You should try simulating this command through telnet too.
Then WAIT. It's possible that the 1 minute timeout you have is
not
enough for some reason.

Is there a proxy server involved? Even though you are going to
msnews
if a proxy server was involved it would be doing the same thing in
each
case
regardless of the final destination server.

Pass these additional symptoms on to your ISP. Escalate if
necessary.
I think you have proven that OE is not a factor in your primary
symptom,
which you have now refined to be: "no response (or perhaps
extremely
delayed response) to NNTP MODE command".


Good luck

Robert Aldwinckle
---