Quick answer

The “problem on Everything” gets resolved by resetting the server PC (or restarting the Everything application) that’s hosting the ETP server, which clears the stuck port/connection state and allows clients to reconnect normally.

What “Everything” this is referring to

The forum thread you’re asking about is about Everything , the free Windows file‑search utility by voidtools, specifically its ETP/FTP server feature. Users were reporting a connectivity issue where a client PC could no longer connect to the Everything ETP server on another PC after some time or after a restart.

How the problem is resolved (step‑by‑step)

From the discussion on the voidtools forum, the core fix is:

  1. Reset / restart the server PC
    • The key line in the thread is: “Once the server PC is reset the problem is resolved.”
 * This clears whatever internal state in Everything (or the OS network stack) is preventing new connections on the ETP port.
  1. If you don’t want to reboot the whole machine, restart Everything itself
    • Users confirm that closing all instances of everything.exe and then reopening Everything also resolves the issue.
 * They verified this by:
   * Using **Process Explorer** and **TCPView** to confirm no `everything.exe` processes remained and that the ETP port was closed.
   * Then binding another application (e.g., an FTP server) to that same port successfully, proving the port was truly freed.

  1. Optional: use debug/verbose mode to diagnose
    The thread also outlines a diagnostic path if the problem keeps recurring:

    • On the server PC running Everything:

      • In the search box, type: /debug and press Enter
      • Then type: /verbose and press Enter

    • This opens a debug console that logs connection events.

    • When a client PC tries and fails to connect, check the server debug console for lines like:
      listen event <x> <y>

    • This helps confirm whether Everything is seeing the connection attempts and whether it’s failing at the listen/accept stage.

Why this works (in plain terms)

The underlying issue appears to be a stuck network listener inside Everything’s ETP server:

  • Over time or after certain events (like client restarts), the ETP server can end up in a state where it:
    • Thinks it’s still listening on the port, but
    • Doesn’t actually accept new connections properly.
  • Restarting the PC or the Everything process:
    • Fully tears down that listener,
    • Releases the TCP port,
    • And lets Everything start a fresh, working ETP server instance when it launches again.

Practical takeaway

If you’re running Everything’s ETP server and clients suddenly can’t connect:

  • First try: close Everything completely and reopen it on the server PC.
  • If that doesn’t help or the issue keeps coming back: reboot the server PC.
  • For persistent problems, enable /debug and /verbose in Everything and inspect the logs when a client fails to connect, then share those logs on the voidtools forum for deeper troubleshooting.

TL;DR: In the forum thread, the “Everything” problem is resolved by resetting the server PC (or fully restarting the Everything app), which clears the stuck ETP server state and restores connectivity.

Information gathered from public forums or data available on the internet and portrayed here.