Author Topic: WinMx Connection Solution : Welcome Back Filtering ! (Read 7767 times)

GhostShip · « **Reply #40 on:** July 05, 2007, 09:19:26 am »

The "havng problems" message originates from winmxgroup and if your seeing this then your host file redirect for the udate bar is not being updated when you run the new patch installer, please ensure your MX is closed for 30 seconds before runing the new installation program.

termite · « **Reply #41 on:** July 05, 2007, 10:11:41 am »

All the above remedies failed. I reinstalled WinMx v3.53 (not v 3.54) Ran it and Guess What ? there it was ''Welcome Back'' . and connects. All too much for me to comprehend at the moment . Gonna to chill out for now and share some files....

tig · « **Reply #42 on:** July 05, 2007, 10:59:17 am »

Well Done termite

Happy winmxing

Victim · « **Reply #43 on:** July 05, 2007, 04:06:22 pm »

Excellent, happy MXing!

Cobra · « **Reply #44 on:** July 06, 2007, 04:07:57 am »

So this is supposed to eliminate fake files again?

Who's going to be working to keep the list updated?

tig · « **Reply #45 on:** July 06, 2007, 04:47:40 am »

Hi Cobra

Yes it will eliminate fake files.

As we are now working as team environment. We will all be sharing to keep things up to date.

Cobra · « **Reply #46 on:** July 06, 2007, 06:10:37 am »

Cool.

Thanks!

Happy Dude · « **Reply #47 on:** July 08, 2007, 03:57:23 am »

Something gone wrong?
My WinMX (yet again) refuses to connect, and WinMXWorld.com is timing out on me - had trouble getting here.

tig · « **Reply #48 on:** July 08, 2007, 06:55:26 am »

Hi Happy

Ok try restarting pc for winmx. And again unallow and allow in your firewalls. I hope this helps please let us know if it doesn't.

Also winmxworld have just moved to a new server. We are still sorting out the bugs out to do with that. Sorry about the delay. Everything we will sorted out of the next few days.

winmxusers · « **Reply #49 on:** July 08, 2007, 10:41:14 pm »

Hi, is it possible that the cache servers from all groups be united? It is in the interest of all winmx users to have one set of servers to maximize chances of finding files. If two separate sets of such servers are used, users from one group may never be connected and find files from users on the other group.

There is enough honor to go around for all and the winmx users will greatly appreciate if the leaders of winmxworld could make some "peace" with the other group.

Thanks!

Me Here · « **Reply #50 on:** July 09, 2007, 12:22:11 am »

Hi winmxusers,

Let me reassure you that the caches aka servers do not in any way have anything to do with file sharing or transfers. I would ask that you have a read here to learn more about WinMX Peer Network as its a decentralized system and there for no files are stored anywhere.

https://www.winmxworld.com/tutorials/wpn.html

As you can see the caches being seperate for this has nothing to do with searches or files. Using the dll patch will keep unportected users from connecting to you and this will help to stablize your connection however, this in no way limits the files you can find on the network. The dll will remove search results from Known fake file flooding companies running rampid on pie users connections.

I hope this clears this up for you and reassures you there is no reason to join the caches at this time and it has no effect on how files are transfered.

winmxusers · « **Reply #51 on:** July 09, 2007, 03:33:57 am »

Hi Me Here,

Well, not quite. Lets say there are two groups of Cache servers. And lets say there are two groups of users, each using only one group of Cache servers, but not the other group of Cache servers. Hence, the Prime conncetions can only form mesh WinMX networks among each separate group's users. I.e. a user from one group will never be part of the mesh of users in the other group. The Cache servers is what manages the mesh distribution of WinMx prime connections which are the backbone on which the P2P works for WinMX. Separate the cache servers into two separate groups and you disconnected one group of users from the other. The only way around it, is to manually change cache servers addresses in hosts file from time to time and thus propage some file between the groups above, but most people wont do it.
So again, to explain how WinMX p2p work - the cache servers although have no files directories in them, are esential for the correct meshes formation among users of those cache directores hence searches may yield less finds if you keep two separate cache servers.

SamSeeSam · « **Reply #52 on:** July 09, 2007, 04:10:14 am »

There is just one group of winmx users
Just one
The difference is the way in which they connect in this group that's all
If you connect via dll and I by pie, I will still be able to see your results in searches and still be able to pm you, download from you, upload to you, join the room you host and do anything else two users normally can with eachh other.

The peer caches have a list of active primary ips which are sent to users wishing to connect to them.
Once connected, then the role of peer caches is over. If say 10 secs after you connected, the peer caches went down, then still you will not notice it unless you try to reconnect to winmx.

I believe the caches hold ips of users irrespective of the patch they use. The dll patch blocks the fake results of users by ip and not the primary they are connected to

Hope this clears things up

Cheers

winmxusers · « **Reply #53 on:** July 09, 2007, 05:41:20 am »

Quote from: SamSeeSam on July 09, 2007, 04:10:14 am

The peer caches have a list of active primary ips which are sent to users wishing to connect to them.
Once connected, then the role of peer caches is over. If say 10 secs after you connected, the peer caches went down, then still you will not notice it unless you try to reconnect to winmx.

Hi Sam,

Are you saying that the other source of patch for WinMX from the other group, is using the SAME cache servers as winmxworld? If all are using the same servers then all is fine regardless indeed the patch used.

Cheers,

GhostShip · « **Reply #54 on:** July 09, 2007, 04:31:54 pm »

Hi Winmxusers, please rest assured that there is a mechanism inside the winmx primary protocol that helps bind all the networks clients together by exchanging primary node information, as such your concerns are well meaning but unfounded, I had noticed you posed the same question on an mxpie forum with little success in obtaining this information.

Now to the more important aspects of how we can all move forward, as your possibly aware we are divided with the other groups over what amounts to one or two simple issues, namely blocking and filtering and personality disputes with cache operators.

I will be calling for an internal winmxworld meeting and hopefully discussing the matter with them all over how to move us forward into further decentralised realms that will not see a repeat of any single closure impacting on the rest of the community, I hope this leads to further dialogue with the other groups with a view to discussing some of the thorny issues but that would be premature of me to announce until both our own group and the other groups are willing to sit around the table without animosity and with a sensible set of proposals to bring to the discussion.

I hope this information is what you where seeking and hopefully I shall have more if and when any meaninful discussion is arranged.

winmxusers · « **Reply #55 on:** July 11, 2007, 10:22:40 pm »

Hi GhostShip,

Indeed I posted the same question on the pie forum. I am not politically assigned to any group, simply I think I represent many WinMX users whom would like to see all forces united again.

Really appreciate much your efforts to reach out to the other group. I will continue post on the pie forum asking for them doing same (of course they may ban me, but sincerly I have no agenda other than seeing you all work together in peace and so I believe many WinMX users will benefit from).

Having same caches for all is a key to keep winmx mesh connected. If you let me know where, I can chat and explain why it is a must. Using difference groups of caches servers will not connect among primary nodes and hence the mesh formed between Winmxworld and Pie will be separated.

I feel you are a very reaosinable leader and I am sure you will do what it takes to try work with the other group. I can guess there were a lot of issues and fights but for the benefit of our WinMX community I think I can speak in the name of all users whom greatly appreciate your hard work, and Winmxworld team work, to say let us make an effort to unite.

Thank you very much,

Winmxusers

winmxusers · « **Reply #56 on:** July 13, 2007, 08:52:24 pm »

Hi GhostShip,

I got an answer on the other forum. It seems that a primary connection can connect to other primary connections from both WMW and other group's. Hence primary connections, regardless of the patch used, will be form between nodes using your and other patch. I do not quite understand how this is possible, in terms of not allowing the cache servers to communicat among the two groups, but at least this is the answers I got.

If this is correct, then indeed no need to worry and different patch and different cache servers can be used and still keep any winmx user connected to the one mesh. Now how a node that uses, say, your patch, knows to connect to nodes using the others group patch and different cache servers that communicate between themselves, is something I don't fully understand... but this is what was stated.

With regards,

WinMXusers

GhostShip · « **Reply #57 on:** July 13, 2007, 10:40:08 pm »

To hold the network together the clients exchange node information between themselves for the scenarios of joining and leaving the network, as I stated above a special packet is in use between all primary nodes that shares information on other connected nodes thereby ensuring a stable and persistant network regardless of how the primary clients join it, I too had the same concerns as yourself until research revealed the packet and its function.

With regard to inter group co-operation, whilst I have been able to make an initial contact with one group, the pie.info group are refusing point blank to even enter into discussions regarding supporting a more wider community framework, Sabre did make an offer to purchase winmxgroup for an unstated purpose, but made no effort or offer to aid anyone through the recent crisis and therefore his actions are those of someone who is not looking to the future for all just his own group, very disappointing all in all.

As I stated in another post the doors here are always open to pro winmx users with plans, ideas, or for exchanging information that will aid the entire poulation of users, its in no ones interest to allow a rerun of some of the less reputable times we have passed through, lets hope many step forward to do what others will not for the good of the community.

winmxusers · « **Reply #58 on:** July 13, 2007, 10:53:26 pm »

Hi GhostShip,

I indeed sense issues between Winmxwolrd and pie. I wish I could help but realistically I cannot. I hope it will one day be solved but I can only wish such.

As for the matter at hand. I still do not know how in practice a winmxworld patch and cache server user with a primary connection, can ever find a pie patch and cache server user with a primary connection so to for connections netween primary to primary. Without having a common node, or exchanging information between cache servers, I do not see how such info gets to a winmx user with a primary connection. This has nothing to do with the protocol used but it has to do with a separated connectivity graph. Simply information on say prime pie connecting nodes cannot be known to the caches of winmxworld and thus to the prime winmxworld nodes without either connecting to the pie caches or having winmxworld caches connect to pie caches to exchange info of such pie pirme connecting nodes IP.

Unless of course there is a hidden such connections that is not advertized where you manually configure the cache servers to look for such nodes on the other pie cache servers.

But since there will be no resolution to this question, and given the deep gap between the groups, I cannot step in the middle of a fire field and get shot...

The best way would also be to just publish the list of cache servers so one can simply manually update the hosts file without going through all those update issues, blocking etc. Of course for some users this may be helpful if they don't know how to do such manually, but its much safer to have an IP replacment in the hosts file with just new cache IPs for the original winmx cache servers vs. having the added functions, updates, blocking etc. - if one user does not want to use such let he or she have an option if they want to risk getting fake files with fake hash or use the patch.

Thanks again for your help,

Winmxusers

GhostShip · « **Reply #59 on:** July 14, 2007, 03:05:59 am »

The issues are simple as previously explained, winmxworld does not feel its in the best interests of the network to allow it to be flooded and users attacked with ddos attacks originating from host file users, to ask folks to sit by for two years as pie.info have done while they attack the rest of the network is selfish and shows the technology and credibility gap between both groups.

I will try once more to rest your fears, as folks join the network they have to receive at least one live primary out of the ten the cache gives them to get things like a room-list, the live primaries are taken from the existing network, if your not connected to the WPN you wont be able to search for files either, this then is a clue that your simply connecting to the same network whether it be via sabre or the community caches indexed by winmxworld, put this together with the information I mentioned in previous posts and its plain that there can be no splitting of the network, indeed its only possible to do in one case, I don't want to give others ideas so I'd rather not mention the details.

This is a list of caches

http: //www.winmxworld.com/caches.php

You'll notice they are not in IP format as its pointless to point users to out of date cache IP addresses, you would be shocked by the amount of carnage that is caused by giving out host files that need updating as cache operators have either changed IP or no longer operate a cache, such schemes are poorly thought out and inflexible, utilising DNS as KM demonstrated makes the entire system flexible and minimalizes patch updates to something like one a year if that regardless of either how many or on what IP the caches operate, in short I don't see the point in throwing a superior system into the dustbin because others are either too unwilling or have dug themselves a pit with negative propaganda over using such improvements that have been proven as such.

Btw its actually not safer to ask users to help flood the network by not using blocking or filtering, it wont surprise you that many calling for no filtering or blocking are not active winmx users and therefore have no care over the damage it causes, this is not the case on this site.

Please read this and help me move the community forward on technical facts and open information.

https://www.winmxworld.com/tutorials/fake_file_info.html

Any primary not blocking fakes is being used as a weapon against fellow users, it cannot be made more clear or bluntly than that.