Carbonite Support > The Carbonite Remote Managemen...

The Carbonite Remote Management Service is Using Hundreds/Thousands of TCP Ports

  • This article is for Windows only

In CSSB 5.3, we discovered an issue where the Carbonite Remote Management Service could get stuck in a loop of attempting to connect, failing to connect, and attempting to connect again. The old connections would be held open while constantly retrying, new connections would be spawned by new backup activity, and each one would utilize a TCP port. Over time, this TCP Port usage build up could cause performance and connectivity issues on the system. The root failure to connect was typically caused by firewalls, content filters, or other similar security measures.

CSSB 6.0 fixed the version 5.3 issue, switching to an entirely different communication method that could open and close even if interrupted by security measures. Unfortunately, this same fix introduced a completely new way for excessive TCP Port usage to occur.

Rather than spawning countless outbound connections as in CSSB 5.3, CSSB 6.0 may create countless internal loopback connections. This has a different root cause and utilizes a different type of connection, but has the same result in the end: connectivity and performance issues on the system where CSSB is installed.

These issues have been resolved in the latest versions of the CSSB client.

The sections below are collapsed. Please click a section title to open / close the appropriate section.

Symptoms

You are experiencing this issue if:

  • You are running CSSB 6.0.
  • You see CSBUIService.exe or CSBUIService-64.exe making more than 15 loopback connections in Resource Monitor. The loopbacks usually do not appear in Task Manager.
    • Resource Monitor can be opened by typing Resource Monitor into the start menu.
    • Visit the Network tab and expand the TCP Connections section to find loopback connections.
    • A screenshot showing excessive loopback connections is shown below.
Resolution

Customers running CSSB 6.0 systems that encounter the loopback-based TCP Ports issue should upgrade to the latest available version of CSSB using these instructions.

Feedback