Author Topic: WinMXWorld's Monopolistic Regme Revealed. GhostShip Beats His Wife! (Read 6773 times)

GhostShip · « **Reply #20 on:** June 11, 2011, 12:42:11 am »

How helpful you are Stripes

With friends like you who needs enemies

White Stripes · « **Reply #21 on:** June 11, 2011, 07:15:50 am »

* Silver Stripes shrugs

if they dont want the list then thats one way to not get the list..... there are others ofc... but i doubt you want me posting those...

also... try connecting as primary with that file.... seems it doesnt want winmx itself to do so... at least in my tinkering (eagles patch kms old patch and a modded hosts file all work....)

also interesting its compiled with msvc 6 while eagles patch was compiled with mingw... makes one wonder just where that file came from....

and since we are being 'friends' and all ... guess i should point out you have a broken cache server;

$ telnet 79.161.83.40 7930
Trying 79.161.83.40...
Connected to 79.161.83.40.
Escape character is '^]'.
»Media-Defender :12.158.234.0-12.158.234.255
Media-Defender :38.107.160.0-38.107.160.255
Media-Defender :38.107.164.0-38.107.164.255
PSINet-Cognet :38.113.165.68-38.113.165.86
PSINet-COGENT :38.102.226.0-38.102.227.255
PSINet-COGENT :38.102.241.0-38.102.241.255
PSINet-COGENT :38.104.82.28-38.104.82.31
PSINet-COGENT :38.104.82.72-38.104.82.75
PSINet-COGENT :38.107.161.0-38.107.161.255
Sabre :65.75.216.5-65.75.216.8
Sabre :82.43.229.238-82.43.229.238
Sabre :205.238.40.1-205.238.40.2
Sabre :205.238.40.54-205.238.40.54
SearchBot :118.237.75.233-118.237.75.233
JRIA :124.154.182.245-124.154.182.245
IIJ :58.138.0.0-58.138.63.255
IIJ :113.197.128.0-113.197.191.255
IIJ :121.102.0.0-121.102.127.255
IIJ :124.147.64.0-124.147.127.255
IIJ :210.148.128.0-210.148.139.255
IIJ :219.111.0.0-219.111.127.255
IIJ :220.100.0.0-220.100.127.255
IIJ :220.100.222.0-220.100.229.255
IIJ :220.100.248.0-220.100.255.255
IIJ :220.156.96.0-220.156.115.255
IIJ :220.210.128.0-220.210.191.255
Temp :77.247.181.164-77.247.181.165
Connection closed by foreign host.

the 'temp' range on that server is still there even tho the .txt file on wmw has long been changed to remove it.... hope an ip added in an emergency makes it to the caches.... (remember the promise of 5min update times?)

should put a monitoring system in place.... the users want a trusted list after all...

silicon_toad2000 · « **Reply #22 on:** June 11, 2011, 07:23:23 am »

thanks stripes

Joshua203 · « **Reply #23 on:** June 11, 2011, 10:29:02 am »

Well as long as someone is going to take a look at the caches anyway..

You might also want to remove the X.X.X.195 ziggo cache (it's been down for a week or more now) and X.X.X.192 comcast cache (wich has a new IP that has already been added but the old one is also still used by the patch).
Sure it will not fix the attacks but it should help connection speeds.

I don't know why but the group.net cachechecker does not seem to reflect the real situation

Greetings,
...Joshua203

tig · « **Reply #24 on:** June 11, 2011, 10:41:58 am »

thanks Joshua203

Joshua203 · « **Reply #25 on:** June 11, 2011, 10:44:21 am »

you re welcome Tig

White Stripes · « **Reply #26 on:** June 11, 2011, 06:14:28 pm »

list on 79.161.83.40 changed ... but for the even stranger... it went further back in time o_O

GhostShip · « **Reply #27 on:** June 11, 2011, 06:18:21 pm »

Some of the problems mentioned in this thread are already known about but have not been undertaken for logistical reasons such as key staff being away for some days etc however as we all know the system has redundancy and continues to work fine albeit with a slightly longer connection delay, this is fully acceptable until the relevant staff are back on station but thanks as always for the heads up Stripes and Joshua.