Skip to main content

Network management

The Classic UI can connect to O&O Defrag on another computer where the installed edition and configuration provide remote management. Operations then run on that computer's local drives through its agent.

Requirements​

  • A compatible O&O Defrag installation and running agent on the target computer.
  • An account authorized to administer the target; the normal arrangement requires membership in its local Administrators group.
  • Network access to the target agent using TCP port 50300.

Enable remote administration from same network relaxes the same-subnet access restriction. Review your administration policy before enabling it; do not assume the option automatically creates every required firewall rule. It is not necessary to grant every network user control just to configure an administrator connection.

Connect​

  1. In the ribbon, open Extras → Connect to computer….
  2. Select or enter the target computer in the connection dialog.
  3. Complete the connection and any required authentication.
  4. Verify the connected computer and its drive list before starting an action or editing settings.
  5. Check reports on that target to confirm results.

Remote commands affect the target computer. Batch-command paths and service names in a remote task also refer to the target, not the computer displaying the interface.

Firewall and connection problems​

If the connection fails, check the computer name, network availability, account permissions, agent service, and firewall rule. Permit the required agent traffic for the intended computers and network profile. Keep the firewall enabled; avoid exposing the management port more broadly than required.

Error 10061 can indicate a refused connection, including a stopped agent or blocked communication. The Classic components also use TCP/IP locally, so a local connection problem does not prove that Internet access is needed. Review the O&O Defrag service and related Windows event entries before changing network rules.

Mapped network shares are not substitutes for remotely managed local volumes. These ribbon instructions and port settings belong to the Classic UI and must not be assumed to configure current OODCMD.