If you are attempting to connect to a WiFi network that has heavy firewall restrictions or if your WiFi network requires you to accept terms and conditions before you are able to access the internet then there are specific configurations that will have to be made on your network to allow the ScreenScape device access to your internet via the WiFi network. The ScreenScape service requirements for restricted networks (2nd Generation Connect Device and Smart Box) are listed below.


Introduction

This information is provided to allow Network Security resources to understand and configure Network policies to allow access to ScreenScape Services over restricted networks. This information is subject to change without notice. It is recommended to configure whitelists by url names over IP address to limit the risk of changes impacting functionality.

Whitelisting

We recommend that a whitelist rule be configured for *.screenscape.com for both http/https protocol to allow access to the full suite of ScreenScape services.

ScreenManager Service Requirements (Online Application)

The ScreenManager application should be open to *.screenscape.com for both http/https.

Specific URLs
  • http://www.screenscape.com
  • https://www.screenscape.com
  • http://manage.screenscape.com
  • https://manage.screenscape.com
  • http://hostedvideo.screenscape.com
  • https://hostedvideo.screenscape.com
  • http://com.screenscape.in.s3.amazonaws.com/
  • https://com.screenscape.in.s3.amazonaws.com/
  • http://cdn.screenscape.com
  • https://cdn.screenscape.com
  • http://support.screenscape.com
  • https://support.screenscape.com

SmartPlayer Service Requirements (Device Software)

The ScreenScape Connect (2nd Generation) and the ScreenScape Smart Box should be
open to *.screenscape.com for both http/https.

Specific URLs
  • http://manage.screenscape.com
  • https://manage.screenscape.com
  • http://hostedvideo.screenscape.com
  • https://hostedvideo.screenscape.com
  • http://cdn.screenscape.com
  • https://cdn.screenscape.com
  • http://deploy.screenscape.com
  • https://deploy.screenscape.com
  • http://messagingstorage.screenscape.com
  • https://messagingstorage.screenscape.com
  • http://google.com
  • https://google.com

Network Time Protocol (NTP) will be from time.windows.com

Windows Update Endpoints

 Windows Updates Service Requirements

Windows Defender Endpoints

Windows Defender Service Requirements

Customer Success Remote Support Access

Spashtop Service Requirements

Third Party Content

The ScreenScape service includes support for third party content services, such as YouTube and RSS. These services are available through ScreenScape on devices with unrestricted Internet access. Customers operating restricted networks, who wish to access third party content will need to add the necessary network rules, as determined by them for the content they wish to access, for third party content to function normally.

SmartPlayer Performance and Health

For real-time performance and health status of our devices, we rely on NewRelic Infrastructure. In order to report data to New Relic, Infrastructure needs outbound access to these domains, networks and ports: https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/networks#infrastructure

IP and Ports

If IP Port based rules are required, use the following:

ScreenManager Service

IPv4 Range Port
65.17.211.192/26 TCP/80
65.17.211.192/26 TCP/443
Please add IP Address for AWS CloudFront and S3 TCP/80

SmartPlayer Devices – All Platforms

IPv4 Range Port
65.17.211.192/26 TCP/80
65.17.211.192/26 TCP/443
Please add IP Address for AWS CloudFront and S3 TCP/80
* UDP/123

Network Time Protocol (NTP) will be from time.windows.com