The most common cause of a Pod that shows the Splash Screen with a valid IP address but users are unable to connect is that network ports need to be open to allow traffic between devices and the Pod. The port restrictions may exist on network hardware like routers, switches, and firewalls or may be on the client PC due to a software firewalls or security software.
Please reference this list of network ports that need to be open for Solstice or certain features to function properly:
- TCP ports 53100, 53101, and 53102: Used by default for basic communications between the Solstice host and both end user devices and the Solstice Dashboard. Three sequential ports are required, but the base port (53100 by default) may be changed on a per-host basis through the display’s configuration panel or the Dashboard.
- UDP port 55001: Used for display discovery if broadcast discovery mode is enabled.
- UDP port 123: Used to communicate with an NTP server.
- TCP ports 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.
- UDP port 5353: Required for iOS mirroring via the Bonjour protocol. It is not required when using the Solstice Bonjour Proxy.
- TCP ports 6000-7000, 7001, 47000, and 47010: Should allow inbound AirPlay® traffic to the Solstice host.
- UDP ports 6000-7000 and 7011:Should allow inbound AirPlay® traffic to the Solstice host.
- TCP port 7001: Should allow inbound AirPlay® traffic
- TCP ports 80 and 443: Used if the Solstice host is allowed to connect to the internet for license activation and software upgrades.
- TCP ports 80 and 443: Used by the OpenControl API to interface with 3rd party systems.
- TCP port 7236: Miracast WiFi Direct control port used to establish and manage sessions between the source device and the Pod.
- TCP port 7250: Port on which the Pod listens for Miracast packets when Over Existing Network mode is enabled.
- UDP port 5353: 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.
If the required ports have been verified to be open, try pinging the Pod IP address. If the Pod cannot be pinged, this may indicate a routing issue on the network or a network restriction between the subnet/vlan that the Pod is connected to and the subnet/vlan that the client is attempting to connect from.