Choose the network you actually connected to
Open the search method menu. Server, sometimes labelled Local, asks the eD2K server you are using. Global (Server) queries the servers in your list. Kad uses Kademlia instead. A working server connection does not establish that a Kad search can work, or the reverse.
Read the connection status before starting a comparison. If Kad has not joined the network, follow the Kad connection checklist. For server searches, check your server list. Avoid changing both while trying to identify which search method failed.
Remove filters that silently exclude a file
For the first test, select all file types and clear minimum size, maximum size, extension and availability restrictions. An old filter can remain relevant even when you enter a different name. Check the units beside size values, too: a number interpreted as megabytes is different from a byte count.
Try one distinctive word from the name of material you are entitled to obtain. Add a second word only after the broad search behaves as expected. A useful comparison changes one field at a time; it does not require repeatedly issuing the same search.
Use short, meaningful keywords
Several ordinary words generally require all of those words to appear. Extra release labels, punctuation or a filename copied from another website can narrow the query too far. Try a simpler spelling before concluding that a file is absent.
Advanced Boolean expressions have rules that differ between server and Kad searches. When diagnosing a problem, use plain words rather than a complicated expression. Once a basic search works, the project's search documentation explains how to refine it.
Compare methods without expecting identical results
Record the query and filters, then try the other connected network. Give each search time to return results. Different discovery paths can return different sets of files, and result limits mean a broad query is not an exhaustive inventory.
If one method works consistently and another remains empty, investigate the failing path. If both work for some queries, concentrate on names, filters and availability rather than reinstalling the program.
Separate no results from misleading results
A page full of unrelated names is a different problem. The official troubleshooting notes warn about spam returned by untrustworthy servers. Keep a maintained list and review suspicious results carefully. A large source count is not proof that a file is authentic.
For persistently poor Kad results, review UDP reachability and whether the router or upstream connection is overloaded. Use the ports guide for specific rules; keep general firewall protection enabled.
When the search succeeds but downloading waits
Finding a name and locating a peer that can supply every part are separate steps. An entry can be discoverable while useful sources are offline or busy. Continue with the slow-download checklist if the file appears in Transfers but does not progress.
Sources and further reading
Project help includes older interface examples. Check the labels and options in your installed build before changing a setting.