From: il barbi on
I have a problem with my newsserver, the first time I click to open a news
OE hangs for 30" and I get this message "NNTP server NNTP did not answer
after 30", retry or break?", I hit "break" then I click on the same news and
I can read it. The same problem arises after some minutes of inactivity on
OE. Summing up I often am forced to stay 30" waiting for OE restarting.
My provider says he is not able to reproduce the malfunction and that's
all...
I tried to search in the Windows registry with Regedit and I found this
interesting key:
HKCU\Identities\{ident.account}\software\microsoft\Internet Account
>> Manager\Accounts\{account number of my newsserver}\NNTP Timeout
being set to hex 1E (decimal 30), then I lowered it to hex 0A (decimal 10)
but nothing changed.
I also tried to trace the malfunction with Wireshark utility (I was able to
read line tracing when I worked) and at NNTP level I see something like
that:
time 23.95 Request group microsoft.public.it.windows.vista
time 26.21 TCP retransmission of the previous request
time 30.80 TCP retransmission of the previous request
time 39.99 TCP retransmission of the previous request
time 58.58 TCP retransmission of the previous request - but at this moment
the 30" timeout must alrealy have elapsed
time 67.60 response from newsserver (I can't know what it means)
time 67.60 request mode reader
time 67.78 response from newsserver (I can't know what it means)
time 67.78 request group microsoft.public.it.windows.vista
time 67.96 response from newsserver (I can't know what it means)
time 67.96 request article 150228
time 68.15 response carrying the text of the news I clicked

someone can help?
il barbi



From: PA Bear [MS MVP] on
Does the behavior persist when you access the same newsgroup via the same
newsserver in a new identity?

il barbi wrote:
> I have a problem with my newsserver, the first time I click to open a news
> OE hangs for 30" and I get this message "NNTP server NNTP did not answer
> after 30", retry or break?", I hit "break" then I click on the same news
> and
> I can read it. The same problem arises after some minutes of inactivity on
> OE. Summing up I often am forced to stay 30" waiting for OE restarting.
> My provider says he is not able to reproduce the malfunction and that's
> all...
> I tried to search in the Windows registry with Regedit and I found this
> interesting key:
> HKCU\Identities\{ident.account}\software\microsoft\Internet Account
>>> Manager\Accounts\{account number of my newsserver}\NNTP Timeout
> being set to hex 1E (decimal 30), then I lowered it to hex 0A (decimal 10)
> but nothing changed.
> I also tried to trace the malfunction with Wireshark utility (I was able
> to
> read line tracing when I worked) and at NNTP level I see something like
> that:
> time 23.95 Request group microsoft.public.it.windows.vista
> time 26.21 TCP retransmission of the previous request
> time 30.80 TCP retransmission of the previous request
> time 39.99 TCP retransmission of the previous request
> time 58.58 TCP retransmission of the previous request - but at this moment
> the 30" timeout must alrealy have elapsed
> time 67.60 response from newsserver (I can't know what it means)
> time 67.60 request mode reader
> time 67.78 response from newsserver (I can't know what it means)
> time 67.78 request group microsoft.public.it.windows.vista
> time 67.96 response from newsserver (I can't know what it means)
> time 67.96 request article 150228
> time 68.15 response carrying the text of the news I clicked
>
> someone can help?
> il barbi

From: il barbi on
"PA Bear [MS MVP]" <PABearMVP(a)gmail.com> ha scritto nel messaggio
news:OfZTdhktKHA.4752(a)TK2MSFTNGP04.phx.gbl...
> Does the behavior persist when you access the same newsgroup via the same
> newsserver in a new identity?
>
now I'm trying with a new identity and apparently the problem does not
arise. Do you think my first identity has been marked as "bad" by my
provider?
il barbi


From: PA Bear [MS MVP] on
il barbi wrote:
<paste>
>> I have a problem with my newsserver, the first time I click to open a
>> news
>> OE hangs for 30" and I get this message "NNTP server NNTP did not answer
>> after 30", retry or break?", I hit "break" then I click on the same news
>> and
>> I can read it. The same problem arises after some minutes of inactivity
>> on
>> OE. Summing up I often am forced to stay 30" waiting for OE restarting.
>> My provider says he is not able to reproduce the malfunction and that's
>> all...
>> I tried to search in the Windows registry with Regedit and I found this
>> interesting key:
>> HKCU\Identities\{ident.account}\software\microsoft\Internet Account
>> Manager\Accounts\{account number of my newsserver}\NNTP Timeout
>> being set to hex 1E (decimal 30), then I lowered it to hex 0A (decimal
>> 10)
>> but nothing changed.
>> I also tried to trace the malfunction with Wireshark utility (I was able
>> to
>> read line tracing when I worked) and at NNTP level I see something like
>> that:
>> time 23.95 Request group microsoft.public.it.windows.vista
>> time 26.21 TCP retransmission of the previous request
>> time 30.80 TCP retransmission of the previous request
>> time 39.99 TCP retransmission of the previous request
>> time 58.58 TCP retransmission of the previous request - but at this
>> moment
>> the 30" timeout must alrealy have elapsed
>> time 67.60 response from newsserver (I can't know what it means)
>> time 67.60 request mode reader
>> time 67.78 response from newsserver (I can't know what it means)
>> time 67.78 request group microsoft.public.it.windows.vista
>> time 67.96 response from newsserver (I can't know what it means)
>> time 67.96 request article 150228
>> time 68.15 response carrying the text of the news I clicked
</paste>
> PA Bear wrote:
>> Does the behavior persist when you access the same newsgroup via the same
>> newsserver in a new identity?
>>
> now I'm trying with a new identity and apparently the problem does not
> arise. Do you think my first identity has been marked as "bad" by my
> provider?

No, I think your original identity was/is damaged, especially if it is the
default Main Identity.

Assuming all is well now *and* you've added all of your Mail accounts to the
news identity, (1) compact all folders in the old identity, (2) import
messages from the old identity into the new one, and then (3) delete the old
one (File | Identities | Manage Identities).

To avoid such corruption in future:

- Don't use Inbox or Sent Items to archive messages. Move them to local
folders created for this purpose.

- Empty Deleted Items folder daily.

- Frequently perform a manual compact of all OE folders while "working
offline". More at http://www.insideoe.com/files/maintain.htm

- Do not cancel Automatic Compacting, should it occur, and do not attempt to
close OE via Task Manager or shutdown your machine if Automatic Compacting
is taking place.

- Disable email scanning by your anti-virus application. It can cause
corruption (i.e., loss of messages) and provides no additional protection:

Why you don't need your anti-virus to scan your email
http://thundercloud.net/infoave/tutorials/email-scanning/index.htm
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002

From: il barbi on
"PA Bear [MS MVP]" <PABearMVP(a)gmail.com> ha scritto nel messaggio
news:%23wo6w29tKHA.5036(a)TK2MSFTNGP02.phx.gbl...
>>> Does the behavior persist when you access the same newsgroup via the
>>> same
>>> newsserver in a new identity?
>>>
>> now I'm trying with a new identity and apparently the problem does not
>> arise. Do you think my first identity has been marked as "bad" by my
>> provider?
>
> No, I think your original identity was/is damaged, especially if it is the
> default Main Identity.
>
Thank you very much for your valuable advices, I'll follow them soon
anyway I can't understand how the items you quoted can damage my identity,
for instance why folder compacting is recommended, can you suggest some
explanatory link?
il barbi