Test your network connection to CrashPlan servers

Objective

Follow these steps to test network connectivity to the CrashPlan cloud on the required ports. This can help you rule out blocked connections caused by firewalls, antivirus products, or other network configurations.

Prerequisites

• Windows, Mac, or Linux operating system
• Command-line tools for your operating system:
  • Windows: PowerShell
  • Mac and Linux: Terminal

Procedure

The CrashPlan app requires ports 443 and 4287 to be open. The examples in this guide use the most common CrashPlan cloud instance, US2 (clients.us2.crashplan.com).

If your organization is in a different cloud instance such as US1 (clients.us1.crashplan.com) or EU5 (clients.eu5.cpg.crashplan.com), replace the address in the commands below.

Option 1: Test connectivity on Windows (PowerShell)

Windows includes the PowerShell scripting tool by default, which can test network routing without requiring third-party tools.

1. Click the Start menu, type PowerShell, and open the application.
2. Run the Test-NetConnection command using your specific server address and port.

   • Format:

     Test-NetConnection -ComputerName [address] -Port [port]

   • Example:

     Test-NetConnection -ComputerName clients.us2.crashplan.com -Port 4287

3. Press Enter.
   • If successful: A TcpTestSucceeded : True message displays.
   • If failed: A WARNING: TCP connect to [...] failed message displays. Proceed to the troubleshooting section below.

Option 2: Test connectivity on Mac or Linux (Netcat)

Mac and Linux systems include the Netcat (nc) networking utility by default.

1. Open the Terminal application.
2. Run the nc command using your specific server address and port.

   • Format:

     nc -vz [address] [port]

   • Example:

     nc -vz clients.us2.crashplan.com 4287

3. Press Enter.
   • If successful: A succeeded! or CONNECTED message displays.
   • If failed: An Operation timed out or Connection refused message displays. Proceed to the troubleshooting section below.

Additional information

Troubleshooting a failed connection

If your connection test fails, the issue is caused by your local computer or network configuration, not the CrashPlan service. To resolve this:

• Check your network configuration and port forwarding settings. For more details, see:
  • IP addresses, domains, and ports used by CrashPlan
• Verify that CrashPlan is added to the exclusion list for security, antivirus, VPNs, and similar software. For more details, see:
  • Known software conflicts with the CrashPlan app
  • Best practices for using CrashPlan with Endpoint Detection and Response (EDR) software