vSpace Firewall Antivirus

Port Configuration for NComputing vSpace Products

Use of this document


This document will assist you with your port configuration for your environment's network, antivirus, firewall, and security software.  When not configured, some of the mentioned, can sometimes interfere with the initial configuration or continued operation of NComputing's vSpace software.  

Therefore, this document offers basic information on applications, services, and network communication within vSpace, use it to apply to your environment to ensure continued operation of your vSpace products.


Possible Symptoms

  • vSpace Update Cannot Reach Update Server
  • vSpace Host Not Visible in Connection List
  • Client Hangs (Freezes) During Connection
  • Cannot update firmware of the terminals
  • Console cannot see the terminals
  • vSpace Manager is not refreshing data whit the Management Portal.   
  • Cannot register the vSpace Manager
  • vSpace reports that it cannot reach the Management Portal 

vSpace Installation Recommendations


When installing vSpace for the first time, it is always recommended to disable the firewall and delay the antivirus software installation until our platform is installed, registered and working in the Session Host.  This is further described
here .  However, when this is not possible or when you are installing in working environments, please make sure to disable  any Anti-Virus or Firewall software during the installation of our product.  Because of the nature and purpose of an antivirus software, even as we have tested with some brands, we have seen the potential of interference with the installation of our product.  


After installation has completed you may re-enable Anti-Virus and Firewall software.  

Troubleshooting Steps 

If system instability occurs after installing NComputing vSpace, please try removing vSpace and any antivirus or security software present, and then reinstalling vSpace.  As mentioned before, after our platform is running well and registered, and if the system is stable in this configuration, you may re-apply the antivirus and security software, being mindful to observe any changes in behavior in your system.   


In some instances, our tech support may require for you to remove your antivirus completely during the process of troubleshooting. 

In any instance, all mentioned network configuration, antivirus, firewall, and security software will benefit from the adjustments below. Please set to ignore/allow/trust the following ports and executables:

Exceptions

Port Exceptions from Firewall

  • L-Series, M-Series, MX-Series and vSpace Client
    • TCP: 27605
    • UDP: 1027, 772, 1283
  • vSpace Pro Enterprise (Version 12) and 11.3 LTS (Windows)        
    • vSpace Manager
      • HTTPS port 443 - registration with NComputing Management Portal (https://manage.ncomputing.com/) with HTTPS port 443
      • TLS/SSL port 8666 – Licensing Server Port
    • vSpace Console
      • TCP 39568 – License Server port
      • TCP 9443 – vSpace Console Server port
      • TCP 8667 – Health Monitor Agent port
    • vSpace Core
      • TCP 3689 – Licensing agent port

  • Below table contains more detailed of the program names and ports being used (i.e. ports should be opened):

Program

Protocol/port

Service name

Purpose

LicenseServer.exe

TLS/SSL 8666

NC License Server (NCLS)

License Agent (LsAgent.exe) connects to it

System (LicenseServer.exe)

TCP 39568

NC License Server (NCLS)

vSpaceConsole.exe connects to it to get list of servers

CMServer.exe

TCP 9443

NC vSpace Console Server

vSpaceConsole.exe connects to it to manage devices, networks, groups and profiles

LsAgent.exe

TCP 3689

NC License Agent

RPC calls from local (only local) vSpace Server

mxdhcp.exe

UDP 67

MX100 DHCP Server

DHCP server for MX100D devices

NcMonitorServer.exe

TCP 8667

NC Monitor Server

Health monitoring agents connect to it to provide collected data


  •  vSpace Server 6 (Windows) 
    • Registration: TCP 80, 3630 (connects to: register.ncomputing.com, 52.29.47.231)   Disabled Since 4-30-2018.
    • Update: TCP 20, 21 (70.182.176.102, 81.169.173.128)
The vSpace 6 "Classic" platform will be permanently discontinued after June 30th, 2020. Please consult your sales representative o tech support for your update needs. 

File Access Exceptions - Only if necessary

    • For all vSpace functionality
      • C:\Program Files\NComputing

Summary
The above exceptions and practices can help ensure the best level of interaction between vSpace and your environment.  If issues still persist with a particular 3rd party application, please contact the application's vendor.  If a workaround exists for your antivirus solution of choice and NComputing engineers have verified its effectiveness, a search for the application's name in the NComputing Knowledge Base will typically reveal any available solutions.


Article #KB024
Last Edited: May 18, 2020


    • Related Articles

    • How to install vSpace Pro Enterprise in restricted network environment (e.g. offline deployment)?

      To deploy vSpace Pro in restricted Internet network environment (e.g. offline environment), it is mandatory to have a minimum of 2 host machines. One host machine (Host A) is used to deploy the vSpace Manager component. A second host machine (Host B) ...

    • vSpace Pro Installation - Tips, References and Process Detail

      Published The following article is a detailed process and tips for installing our vSpace Pro platform (vSpace Pro LTS, vSpace Pro Enterprise Edition). As an additional supplement, this article will deal with all other aspects of Pre-Deployment and ...

    • How to: Register vSpace Pro LTS Offline

      This Article is for administrators who are looking to register their vSpace Pro LTS (version 11.3.10) installation. ATTENTION: Do not perform Offline Registration if you have Aged Devices (Manufactured Prior to January 1, 2015) as these devices are ...

    • Offline Registration Process for Legacy vSpace Software Versions

      With the end of life of several of our vSpace Server editions, the online registration services have been decommissioned as follows: Apr 30, 2018 --vSpace 4.x, 7.x and 8.x Apr 30, 2018 --vSpace 6.x for L-series thin clients These dates, as well as ...

    • Network Error Code 10014 / Network Error Code 10054

      Network Error Code 10014 and 10054 occur in XP and 2003 Server when running the vSpace Registration utility, and attempting to perform an online registration, the following errors may occur.  Therefore, the registration process cannot complete ...