Morpheus/kazaa

[Gayowulf]

I've noticed recently that there are never more than 100 users online, and absolutely no music available.

Anyone know whats up with this?

[Akalon]

Damn :confused:

I'm not on my computer now so I can't check :(

[Coolin]

I still get about 400,000 users online right now.

[keith]

kazaa sucks bigtime. use audiogalaxy and their software, tons better.

[Coolin]

Originally posted by keith
kazaa sucks bigtime. use audiogalaxy and their software, tons better. kazaa may suck.
But Morpheus owns.

[Bruce]

Morpheus does own. Almost everything is filtered through Audiogalaxy now.


I haven't noticed that, Gayowulf.

Here are the current stats that I'm getting.
879,428 users online sharing 135936k files (7403918.3 GB)

[LastActionHero]

Nope, nothing here
517,826 users online 70476K files (388080 GB).

Myabe your copy failed to connect to any big super node.

[neG.oNe]

kazaa may suck.
But Morpheus owns.
right on!

[Gayowulf]

Originally posted by LastActionHero

Myabe your copy failed to connect to any big super node.

must be. i only get 34 users 0.0GB available.

Nothing is going right for me these days:mad:

[Bruce]

Are you using the latest version? I had some problems with an older version a few days ago.

[Gayowulf]

i'm usingtheold version, but only becauase downloading the new version crashes my computer.

[keith]

and therein lies the answer. get a new computer. :cool:

[Coolin]

Originally posted by demise

right on! I'm glad many agree with me. :)

[rapmaster]

I've been getting the same thing, 30users sharing jack do-do, I've tried installing the latest version but it wont install or something cuz it just says something about my share info was changed then fires off morpheous only to sit there trying to connection for ever

[DJsexie]

I'm using the lastest version of Morpheus(1.3.3) and it works perfectly fine for me

[Gayowulf]

the highest version i can find is 1.3

where can i get 1.3.3?

[Coolin]

Originally posted by Gayowulf
the highest version i can find is 1.3

where can i get 1.3.3? You download 1.3 and log onto Morpheus. It should ask you to update. If it doesn't happen, search for Morpheus update on the file search. (If you can get any search results at all of course)

[Gayowulf]

that automatic update never updates.

[LastActionHero]

uinstall and reinstall morpheus.

and check for morpheus updates in file search

here is how morpheus/kazza work


KaZaA, MusicCity, and Grokster each operate a central log-in server. The
addresses of these servers are hard-coded into the application. At log-in, the
peer sends one packet of data to the server, and the server returns two
packets. The transmissions presumably involve log-in information from the peer
and acknowledgement and confirmation from the server. This function appears to
be similar for each of the three entities. In addition, Vidius reports that, at
least with the KaZaA application, there is a commun-ication regularly every 12
hours between the log-in (.37) server and the user (whether in peer or
supernode status) [we do not know the nature of these communications].

Notably, the log-in server is not essential to a peer’s use of the net-work. If
the log-in server is not avail-able, the application nevertheless attempts to
connect to a supernode using the list contained in the registry (whether it is
the preset list for a new user or the most recent update for a repeat user).

After log-in, the peer then attempts to connect to a supernode, using a list of
super-node addresses stored in the software application. That list is supplied
by the applica-tion devel-oper, and is identical across KaZaA, Morpheus, and
Grokster. The list includes IP addresses at universities and other institutions
such as the NASA Jet Propul-sion Laboratory. The list of supernodes has changed
with each new version of the application. In the newest version of the
application, the list also includes an IP address at Disney,
rnd11-200.rd.wdi.disney.com. The IP addresses listed in the registry do not all
function as supernodes at any given time; in fact, most do not. After logging
in, a peer works through the list in its registry until its finds a supernode
it can connect to. When the peer connects to a supernode for the first time, it
receives an updated list of supernodes, which over-writes the preset list in
the registry. [we do not know how the suprnode obtains this updated list of
supernodes to distribute]. The list of supernodes in the registry is then
updated every time the peer connects to a supernode. Thus, a peer always has
the most recent possible list of com-pu-ters that have functioned as
supernodes, thereby increasing the odds of a successful connection during the
next session. After initially making contact with a supernode, a peer may be
shunted around the network as the system attempts to match the peer with the
most appropriate super-node.

If the registry is somehow corrupted, the application causes the peer to
contact another server controlled by KaZaA, supernode.kazaa.com
(213.248.112.38). This address is also hard-coded into the application. This
means that the KaZaA network maintains a dynamic list of active supernodes [we
do not know how this happens]. Upon connecting to that server, the peer will
receive a list of known supernodes. All three applications direct the user to
the KaZaA (.38) server in this circum-stance.

KaZaA operates another server in addition to the log-in (.37) server and the
(.38) server described above. That is alpha.kazaa.com (213.248.112.34), the
address of which, as with the other two, is hard-coded into the application.
The (.34) server communica-tes with supernodes [we do not know the nature of
the communication]. During an interval when a Vidius machine was acting as a
supernode, there were 12 different attempts by the (.34) server to connect to
the supernode. Vidius reports that in a completed transaction the (.34) server
sends approximately 1600 bytes of information to the super-node. In addition,
as noted above, a supernode makes periodic connection with the KaZaA log-in
(.37) server.