Display Discovery BasicsThere are three ways that users can discover and connect to Solstice displays.
- Manually enter the IP address that is displayed on the Solstice display splash screen.
- Solstice broadcast discovery.
- Solstice Discovery Service.
The manual method requires the user to find the IP address displayed on the main Solstice window and key it in to the Solstice client. This fallback method is used when automated discovery mechanisms aren’t available. Once a user has connected to a Solstice display using the IP address, the display will be retained in the 'recently used' list so that subsequent connections can be done by selecting the display from a list.
The broadcast discovery mechanism is the default mechanism for Solstice. The Solstice display sends out periodic messages to the broadcast address to announce itself to clients on the network. If the network policy allows broadcast packets, all clients on the same subnet will automatically discover all active Solstice displays and will present them in the “Discovered Displays” list on the discovery screen.
Solstice Discovery Service (SDS) provides a lightweight centralized discovery mechanism that can work in more complex network environments. Because SDS does not rely on broadcast packets, it can be used on networks that restrict broadcast traffic and can also be configured to operate concurrently on multiple subnets. Additional network configuration may be necessary depending on your specific requirements. For more information refer to the Network Deployment Guide and/or SDS Guide.
Connection TroubleshootingThe Solstice clients share content with the Solstice display over 3 TCP ports. The network must be configured to allow clients to initiate connections to the Solstice Server machine on these three ports. If inbound connections are blocked, the client will not be able to connect to the server and share content. Network restrictions are the most common reason that clients are unable to connect to the Solstice Server. If you are having trouble connecting, check the following:
- Security software on the Solstice computer that may be blocking inbound connections. This includes Windows Firewall as well as many third party network security programs (Norton, Symantec, etc).
- Check network hardware configuration. In many corporate or institutional networks, ports are blocked by default and are only opened up on an as-needed basis. The network security settings at the switch or router level may have to be updated to allow connections on the Solstice ports.
- Default “client to client” restrictions on some routers, “wireless hotspots” or other ad-hoc devices may prevent all client-to-client connections. This can typically be configured to enable client-to-client communication through the configuration menu.
Step 1: Make sure the client can connect to the server computer.
Use the “ping” command to verify that the network is set up correctly:
- Open a command window on the client.
- At the prompt type: ping SERVER_IP_ADDRESS
- You should get a message indicating that the server responded
- Is the server configured to respond to ping requests? (Try to ping the server from itself to verify that it is responding to ping)
- Does the server (or network) have a firewall configured? Check your Windows Firewall settings or any other security software.
- Is the client on the same network with the server? For example, if the client is using a WiFi network that doesn’t have connectivity to the server (ethernet?) network.
Step 2: Make sure the client can connect to the server computer.
- Enable the telnet client on the Solstice client machine and also enable the telnet client on the Solstice server machine. You may have to enable Telnet on windows first - instructions here
- Confirm that the Solstice server is running and waiting for connections on the primary airplay port by using telnet on the SERVER machine to connect to itself:
If you don’t get a response / can’t connect, check to verify that you don’t have any firewall running on your Solstice server machine.
Step 3: Try Port 53100 with Client
- Open a command window on the client.
- Use Telnet to attempt to connect to the server on port 53100:
If you aren’t able to connect using Telnet (you should get the same string as above) check that your network isn’t blocking port 53100. The router, the windows Firewall, or other firewall/security software could be blocking traffic.
If you are able to connect and get a response from the server using the ping command, but are still unable to connect with the client, please contact Mersive Support at firstname.lastname@example.org.