eMule can use two discovery networks: server-based eD2K and decentralised Kad. They help your client find files and other users offering them. The actual file data normally comes from those users, rather than from an eD2K server's disk.
eD2K uses servers to help find sources
You connect to an eD2K server and ask it for information about matching files or sources. Local server searches and Global server searches have different scopes. The server list tells the client where those discovery services are; it is not a catalogue of downloadable file contents.
A useful server can improve discovery, but it does not own every file mentioned in a result. Switching servers cannot make an offline peer return or create the missing part of a rare download. Use the server.met guide when the list itself needs attention.
Kad distributes discovery across clients
Kad uses participating clients instead of an eD2K server to organise discovery. A client needs a starting contact to join; the process is called bootstrapping. Once it has suitable contacts, it can discover the network without a central eD2K server.
The practical distinction matters when restoring a fresh installation. A maintained server list and a Kad contact file serve different purposes. Adding one does not automatically replace the other. Follow the Kad checklist if the contact list is empty or joining fails.
Connection, reachability and availability are separate
First ask whether a discovery network is connected. Then check whether other clients can reach the ports your client uses. Finally inspect whether the file has useful sources and whether those sources are ready to upload.
Those questions explain why a green-looking connection display can coexist with a waiting transfer. It is possible to find a file while lacking a useful source for its remaining parts. It is also possible to have a local disk problem after network discovery worked perfectly.
Read each network's own status
Server High ID or Low ID and Kad open or firewalled are related reachability indicators, but they are not interchangeable test results. The TCP and UDP guide explains why one successful test does not prove the whole incoming path is working.
A practical status note might say: server connected with Low ID; Kad connected but firewalled; search returns names; transfer waits. That description is much more useful for troubleshooting than simply saying that eMule is slow.
Compare search methods when diagnosing a problem
Keep one simple query and its filters unchanged while comparing the connected methods. The result lists need not be identical. If only one method fails, focus your checks on that discovery path rather than discarding the entire installation.
Use the search guide for a repeatable test. Once sources are found, read the queue explanation before treating a wait as a failed connection.
A sensible setup goal
Configure each network you intend to use, verify its status and keep a record of the working ports and folders. There is no need to chase a new list or reset all preferences every time one transfer pauses. Start with the particular symptom and follow the matching guide.
Sources and further reading
- Official eMule network guide
- Official help: searching for files
- Official help: the Kad window
- Official help: ID explained
Project help includes older interface examples. Check the labels and options in your installed build before changing a setting.