install 2.0-noMX

[so_]

Holy crap, I just did this update, and within minutes of connecting to a primary, I had close to 100 hits in my peer guardian. Most of them were from,

MVSN-sympatico
globix
Performance Systems International-ed2k/ap2p
Macrovision Corp.
Macrovision -IGS
Macrovision-Globix

All the source ip's were different, all were TCP protocol and action taken against all of them were blocked.

Even after disconnecting from winmx I continued to get these hits.
Before I did this 2.0 update, I had 1.9 v of the patch, and never got this many hits. On my last shutdown of winmx, I was running a secondary connection, with 0 hits in peer guardian.

What gives?

so_

[Anonymous]

BTW, Im running 3.5.4.0 beta. on winxp pro, sp2. cable connection.

[Anonymous]

I continued to get hits in PG for 20 or so minutes after disconnecting from winmx, so I went in and closed the ports I was using for winmx, and no more hits. I was using 26699 TCP, and 26257 UDP. This has never happened before with winmx, until I did the 2.0 upgrade. Can anyone explain this to me?

ps> sorry for all the replys, no edit.

so_

[Anonymous]

Well, I uninstalled everything and started over. Used 1.9 this time and everything seems to be ok for now.

I did the 2.0 upgrade by clicking on the "update available" from the winmx window. I just went back and looked at it again and it's from "winmx group". I never payed any attention to that earlier. WTF is this winmx group? Bogus?

so_

[Me Here]

HI So_
Yes we are being hit hard by the Macrovision flooding the network and trying their best to attach themselves to primaries and use their bandwidth to carry out DOS (Denial Of Service) attacks on us.

What your seeing on Peer Guardian is nothing new to most, its quite normal for them to stay trying to attach to you for hours after turning off WinMX even.

This is why we are preaching the need for every primary to use something to block them as you are now using pg2 with our block list to ensure its up to date for WinMX.. Good job!!

The 2.0 upgrade is just that, its a fixed dll patch for your WinMx, the main differences are that this one does block the riaa for 98/ME users!!
WinMxGroup has been developing this patch and its been in use since nearly the beginning of our new caches.  That patch was made by KM, who is also running one of the main caches we all use to connect.  You can most certainly trust that this is a upgrade patch to the Install 1.9 and should see better performance from this upgrade as well.  

With the 1.9 patch, when running pg2 along with it, you may have seen those hits on pg2 as it receives the request for a connection before the dll, this means that although the ws2_32.dll patch for XP also blocked the dangerous connection you still would have seen them first on Pg2.  Its not a problem to run the pg2 and use the 2.0 patch.  Obviously the patch helps you to connect to WinMx with the added bonus of blocking IPs from the RIAA, and PG2 also blocks these same IPs if you have our block list added.

Hope this helps to clear some of this up for you, if there is anything i didnt clear up or didnt make clear let me know..

[Anonymous]

Thanks Me Here, yes this does clear up alot of questions I had. Never really paid any attention before, that the updates were from winmx group, just always assumed they were from here.

I will go ahead with the 2.0 upgrade again, and yes PG is updated regularly with your blocklist.

You are so right about being hit hard by the flooding. I ran a secondary all night with roughly 20 hits in PG, then switched to primary this morning, and had hundreds of hits within a couple of minutes. So your saying as long as I keep my PG blocklist up to date, patches up to date, I will be safe?

Thanks again Me Here for your help.

so_

[Me Here]

Yes, that should keep you fine, and your doing your part to protect other users as well..

If you have anyother questions about it all just hollar at us here..

[itsbry]

I always wondered if PG2 was doing it right... the list just continuously flows with 5or 6 per second blocked... cool.