While both of the previous explanations are applicable in some cases, neither are applicable here. The problem here is a single network listing four different network names. Since MX, and all other clients, use the network name to tell them what networks they are already connected to, and therefore should no longer attempt further connections, when a network does not use a consistent name, this is the result. His client thinks well OK. i am already connected to Rise of the Phoenix, but not Apollo, when it actually already is connected to Apollo (and the other 2 as well). This is a simple case of a network misusing the network name field. All of the servers in that image are linked to each other, and yet each one lists a different network name. The wasted attempts and confusion are the inevitable result.