Chris - AMWSO
February 23rd, 2005, 09:03 AM
Hi All
One of our affiliates found that he couldn't make LinkShare links work on his PC, upon checking further he found a range of changes to his HOSt file that had been done by Kazaa Lite, once removed the changes stayed...which from what (little I know of host files) of the below means that he could not access anything to fo with LS once removed as the local pointing IP had nothing to refer too...anyone care to expand or put me right please? I have sent to LS to review too.
HOST Changes by Kazaa Lite
127.0.0.1 ad.linksynergy.com
127.0.0.1 click.linksynergy.com
127.0.0.1 www.linkshare.com
127.0.0.1 uk1.linksynergy.com
127.0.0.1 uk2.linksynergy.com
127.0.0.1 uk3.linksynergy.com
127.0.0.1 uk4.linksynergy.com
127.0.0.1 uk5.linksynergy.com
One would imagine that the 127 IP is a local one run through the
software that cause all traffic to be tagged... .
When Kazaa is removed... LinkShare is no longer accessible as this
host file change remains in place
Thanks
Chris
One of our affiliates found that he couldn't make LinkShare links work on his PC, upon checking further he found a range of changes to his HOSt file that had been done by Kazaa Lite, once removed the changes stayed...which from what (little I know of host files) of the below means that he could not access anything to fo with LS once removed as the local pointing IP had nothing to refer too...anyone care to expand or put me right please? I have sent to LS to review too.
HOST Changes by Kazaa Lite
127.0.0.1 ad.linksynergy.com
127.0.0.1 click.linksynergy.com
127.0.0.1 www.linkshare.com
127.0.0.1 uk1.linksynergy.com
127.0.0.1 uk2.linksynergy.com
127.0.0.1 uk3.linksynergy.com
127.0.0.1 uk4.linksynergy.com
127.0.0.1 uk5.linksynergy.com
One would imagine that the 127 IP is a local one run through the
software that cause all traffic to be tagged... .
When Kazaa is removed... LinkShare is no longer accessible as this
host file change remains in place
Thanks
Chris
