Test Your Network Connections
    • Dark
      Light
    • PDF

    Test Your Network Connections

    • Dark
      Light
    • PDF

    Article summary

    To deploy ControlUp, it is important that all of our networking requirements are in place. Our networking requirements are described in these articles:

    To make sure you have the requirements in place, you can use our CUTester tool. If there is a network issue, the tester lets you know whether the issue is related to:

    • Network communication failure
    • Proxy/network filtering
    • TLS handshake failure

    Download the tester

    ControlUpTester.zip

    How to use the tester

    Requires .NET Framework 4.8

    If you don't have .NET Framework 4.8 installed, you will receive an error when you try to run the tester.

    • To test ControlUp for VDI & DaaS, run the tester from Monitor machines and machines that run the Real-Time Console desktop application.
    • To test ControlUp for Physical Endpoint (Edge DX and Secure DX), run the tester from machines where the Edge DX and Secure DX Agents will be installed.
    • To test synthetic monitoring with Scoutbees, run the tester from machines where Custom Hives will be installed.

    When you run the CUTester application (CUTester.exe), answer the following questions:

    • What region are you on? Enter the data region you selected when you created your organization. For US/ROW (rest of world), enter us. For EU, enter eu.
    • Are you testing Real-Time DX (Hybrid Cloud)?. If you are testing ControlUp for VDI & DaaS, enter yes. Otherwise, enter no.
    • Are you testing Agent Communication? This tests Agent communication to the Monitor. Enter yes to test the additional URLs required for Agent communication. If you don't use ControlUp for VDI & DaaS, enter no.
    • Are you testing Edge DX? If you are testing ControlUp for Physical Endpoint and running the tester on a machine where the Edge DX Agent will be installed, enter yes. Otherwise, enter no.
      • Please enter your TenantID: This question appears only if you are testing Edge DX. Enter your Edge DX tenant name. You can find your tenant name by going to the Edge DX Agent downloads page. For example, in the image below, the tenant name is controluptechmarketing.
        TenantNameTechMarketing.png
    • Are you testing Scoutbees? If you are testing synthetic monitoring (Scoutbees) from a machine where a Custom Hive will be installed, enter yes. Otherwise, enter no.
    • Are you testing Secure DX? If you are testing Secure DX from a machine where the Secure DX Agent will be installed, enter yes. Otherwise, enter no.
    • Are you testing an API URL? If you want to test whether a certain API URL can be reached, enter yes. For example, if you are using ControlUp for VDI & DaaS to connect to a Citrix delivery controller, you can test whether the Odata API can be reached from your machine.
      • Please enter API URL: enter the URL of the API to test.

    After you answer all of the questions, CUTester will test all the required network connections:

    CuTesterResults.png

    Configure a proxy

    You configure the tester to use a proxy. Currently, only HTTP proxy is supported.

    1. Open CUTester.exe.config

    2. Add the proxyAddress and proxyPort. Optionally, you can add a username and password if needed.
      NetworkTesterV2Proxy.png

    3. Save the config file and run the tester.

    Run the tester under the network service account

    The ControlUp Monitor runs under the network service account. If you are running the tester from a Monitor, you can run it as "Network Service" to exactly simulate Monitor communication.

    To run the tester under the network service account:

    1. Copy the tester into the Temp folder. Note that the Temp folder path will be added to PATH SYTEM environment variables.
    2. Open PowerShell elevated with adaministrative privileges.
    3. Run the script RunAsNetworkService.ps1 in the ControlUpTester file. The tester indicates which user it is running under, and you can use Task Manager to confirm the user running the tester.

    Troubleshooting

    If the tester gets stuck and takes a long time testing a certain URL, press Enter.


    Was this article helpful?