My last suggestion was to run hijactThis. How Article - 299357 came into
play I do not know.
http://groups.google.ca/groups?hl=en&lr=lang_en|lang_fr&ie=UTF-8&oe=UTF-8&newwindow=1&threadm=vrkbmeig4tc7fd%40corp.supernews.com&rnum=2&prev=/groups%3Fq%3DAdnuker%26hl%3Den%26lr%3Dlang_en%257Clang_fr%26ie%3DUTF-8%26oe%3DUTF-8%26newwindow%3D1%26sa%3DG%26scoring%3Dd
--
Henri Leboeuf
Web page:
http://www.generation.net/~hleboeuf/index.htm
"Iolo" <(E-Mail Removed)> wrote in message
news:Xns9437C5EE8472ioloiolonetnet@207.217.77.202...
> Following H Leboeuf's tips I found that resetting the IP stack for Windows
> XP cleaned out the problem caused by Adnuker.
>
> Microsoft Knowledge Base Article - 299357
>