Network Requirements

Solstice uses all TCP/IP standard network traffic to communicate across all the required and optional components of the Solstice system. The network(s) that Solstice is ultimately deployed on needs to allow peer-to-peer TCP connections. Additionally, for enterprise networks, firewall exceptions may need to be made and network ports may need to be open to allow certain Solstice capabilities to function.

Firewall Exceptions

You may also need to make firewall or proxy bypass exceptions for the following sites:

  • Required for software updates, Solstice Cloud, default RSS feed, default digital signage feed:
    • mersive.com
    • *.mersive.com

    Specific sites required for Solstice Cloud Management (formerly known as Kepler):

    • Kepler.mersive.com
    • Kepler-backend.mersive.com
    • Kepler-auth.mersive.com
    • Kepler-auth-svc.mersive.com
    • Kepler-onboarding.mersive.com
  • Required for pod activation, licensing, and subscription updates:
    • manager.flexnetoperations.com
  • To detect captive portals, Solstice may periodically attempt a connection to:
    • clients3.google.com/generate_204

    Captive portal checks can be turned off as of Solstice version 5.3.

If you utilize a tool that limits program access, such as an anti-virus program, device management services, or a local firewall such as the Windows Firewall Defender, you may need to whitelist or allow the following programs:

  • SolsticeClient.exe
  • SolsticeConference.exe
  • SolsticeVirtualDisplay.exe
  • rsusbipclient.exe

If the programs are not listed, you can add the programs manually using the installation path of the Solstice client. Example installation paths are as follows:

  • QuickConnect Client (downloaded from the Pod):  C:\Users\%username%\AppData\Local\Mersive\SolsticeClient
  • MSI & SCCM Installers:  C:\Program Files\Mersive Technologies, Inc\Solstice\Client

Open Network Ports

Depending on which features your end-users will utilize, certain network ports/routes must be open for Solstice and those features to work correctly.

TCP

  • 7: Used for gateway check (feature deprecated on Pods in Solstice version 5.3.2 and later).
  • 80 and 443: Used if the Solstice host is allowed to connect to the internet for license activation and software upgrades. When pushing a local update file to the Pod, these ports need to be open between the Pod and the Dashboard. These ports are also used by the OpenControl API to interface with 3rd party systems. When network encryption is enabled, the Solstice Dashboard will send SLR updates via port 443.
  • If you are using a Solstice Pod or Solstice Dashboard on 4.1 or higher, communication to Mersive's license server will only occur over https/port 443.

  • 6443: Used for browser-based sharing connections.
  • 7236: Miracast WiFi Direct control port used to establish and manage sessions between the source device and the Pod.
  • 7250: Port on which the Pod listens for Miracast packets when Over Existing Network mode is enabled.
  • 6000-7000, 7100, 47000, and 47010: Should allow inbound AirPlay® traffic to the Solstice host.
  • 53100, 53101, and 53102: Used by default for basic communications between the Solstice host and both end user devices and the Solstice Dashboard. The base port (53100 by default) may be changed on a per-Pod basis through the Pod’s configuration panel or the Solstice Dashboard. Important note: Changing Solstice's base port will also change the sequential streaming port (Solstice base port +1) and notification port (Solstice base port +2) used by Solstice. You must ensure that all three ports are opened on your network.
  • 53103-53119: Used by Solstice Conference in addition to the default base ports 53100-53102. As a note, UDP traffic will need to be enabled for TCP ports 53107-53117 as Solstice will pass UDP packets through these ports. Important note: Changing Solstice's base port will also sequentially change the ports used by Solstice Conference by +100 ports. For example, if you change the configured Solstice base port to 53101, the ports used by Solstice Conference will change to 53204-53220.
    • Ports used for Windows devices: 53103, 53104, 53110-53119.
    • Ports used for MacOS devices: 53105-53108.
  • 53200, 53201, and 53202: Used by the Solstice host and end user devices to communicate the Solstice Discovery Service (SDS) host if SDS discovery mode is enabled.
  • The browser-based sharing capability can utilize any non-privileged TCP port from 1024 to 65535.

UDP

  • 123: Used to communicate with an NTP server.
  • 5353: Required for iOS mirroring via the Bonjour protocol. It is not required when using the Solstice Bonjour Proxy. Also, if Miracast Over Existing Network mode is enabled, this port is used for multicast DNS (mDNS). mDNS is broadcasted to the local subnet of each network interface the Pod is connected to. If the computer that is attempting to make an infrastructure connection is on a different subnet, this broadcast will fail. If this happens, a workaround is to create a DNS entry to the Pod’s hostname.
  • 6000-7000, and 7011: Should allow inbound AirPlay® traffic to the Solstice host.
  • 55001: Used for display discovery if broadcast discovery mode is enabled.
  • Both the Miracast and browser-based sharing capabilities can utilize any non-privileged UDP port from 1024 to 65535.

Network Diagram

Related Topics

Deploying Solstice