Nice trolling, however, there is a way to block such things. USE
FIREFOX OR OPERA!

Thank you, drive through and welcome to my Trollblocking filter.


Susan Sharm wrote:
> Daniel Crichton wrote:
>
>>you have been infected by something else that has set up rad.msn.com
>>in your hosts file to point to a non-MS site that attempts to download
>>that DLL.
>
>
> I added the 127.0.0.1 loopback back to my own machine to the Windowx XP
> c:\winnt\system32\drivers\etc\hosts file based on well known advice
> from a variety of sites such as
> http://accs-net.com/hosts/how_to_use_hosts.html
>
> The 127.0.0.1 is simply a way to redirect all requests to the Microsoft
> Repeat Advertising Server (rad.msn.com) to the local machine so it
> never gets to the Internet.
>
> This is so common a workaround that almost every single hosts file on
> the Internet has this "127.0.0.1 rad.msn.com" redirect as shown by the
> following.
> http://everythingisnt.com/hosts
> http://tylercole.info/removeads.php
> http://www.infonomicon.org/text/hosts
> http://www.avidware.net/spyware/dete...-host-file.asp
> http://www.bleedingsnort.com/forum/v...1&showtopic=98
> http://www.genericgeek.com/index.php?q=node/538
> http://www.erickson.stfrancisville.com/tools/index.htm
> http://www.lurkhere.com/cgi-bin/foru...m= 527&omm=44
> http://www.mytechsupport.ca/helpwith...?TOPIC_ID=4586
>
> Judging from all these attempts at BLOCKING the request TRANSPARENTLY,
> this is a common as yet unsolved problem:
> http://lamerkatz.com/forum/viewtopic...3fca2 7fbab6a
> http://www.bleedingsnort.com/forum/v...1&showtopic=98
> http://www.darksun.ws/PHPBB2/viewtop...&view=previous
> http://www.neilpwc.co.uk/neonblog/ms...dvert-removal/
> http://www.cableforum.co.uk/board/sh...8&page=2&pp=15
> http://forums.techguy.org/archive/t-405673.html
> http://outpostfirewall.com/forum/sho...46&postcount=3
> http://www.msghelp.net/showthread.php?tid=34015&page=3
>
> Maybe I'm wrong (Rod Speed will certainly provide the solution for us
> since he is the world's best 14-year old expert on the Windows PC) but
> it seems like:
> 1. This is a very common problem.
> 2. Nothing yet transparently blocks the request.
> 3. If you don't get the request, that means you are infected.
> 4. The best we can do (so far) is a workaround.
> 5. What we're asking is if there is an expert (greater than 14 years
> old) who knows how to TRANSPARENTLY STOP this request from Microsoft
> from infecting our systems.
>
> Thank you in advance for your expert guidance,
> Susan Harm
>