Scala Media Players
TightVNC Incoming Traffic Rule - Network Must Be Private
Scala Media Player Windows® images dated after June 2, 2020 adhere to the Windows firewall network connection rule for TightVNC so that TightVNC connections are permitted only on private networks. If the network that your player uses is public and you want to set up a TightVNC connection, you will need to change the network connection from public to private.
If you are allowing your player to run on a public network, we recommend that you use a reverse VNC connection to remotely access your player. For more information about setting up a reverse VNC connection, see Reverse-VNC on this page.
Changing the TightVNC Incoming Traffic Rule
While the TightVNC incoming traffic rule can be changed to permit connections on all network profiles, we advise that you avoid untrusted, public networks.
Setting a Player's Network to Private
There are four different ways that you can set a player's network as private:
Step-by-step instructions for each of the four options are provided below.
Setting a Player's Network to Private Using the Windows User Interface
To use the Windows GUI to change the network connection, click the network dialog that appears at the bottom, left of the screen next to the task bar.
The Ethernet page appears.
Click the Network name to access the Network profile.
Select the Private radio button under the Network Profile heading.
Setting a Player's Network to Private Using Windows PowerShell
To view the current status of your network connection using the Windows PowerShell, use the following command:
To change the connection status of your network connection to private using Windows PowerShell, use the following command:
Setting a Player's Network to Private Using by Editing the Registry (REGEDIT)
Setting a Player's Network to Private by Editing the Local Security Policy/GPEDIT.MSC or SecPol.MSC
A reverse-VNC connection is when the remote VNC server service will call back to a listening VNC-Viewer that has been configured to be in Remote-Connection-Listening mode.
Use Reverse-VNC to connect to players when:
Use a Content Manager maintenance job to send commands to a remote player which will initiate a Reverse-VNC connection.
For networks where there can be a need for the Network Administrators to have multiple simultaneous sessions, it is possible to configure several listening VNC-Viewers on any given administrative workstation with each VNC-Viewer listening for remote connections on its own unique TCP-Port.
In addition, NAT-TCP-redirection/Port-Forwarding can be utilized so that reverse VNC Content Manager maintenance jobs can be targeted to listening VNC-Viewer on multiple Admin-PC’s.
Example Uses of OpenSSH for Security Tunneling Remote Connections
An SSH-client such as PuTTY, the $M® Microsoft OpenSSH client, or the SSH client in Mac OS or Linux, etc. can be employed to securely access your Scala Media Player over public, untrusted networks.
This will permit a VNC client to remotely connect to the remote Player device by addressing "localhost:59169" on the administrative workstation.
To establish a "Remote Desktop Protocol Connection":
This will permit a Remote Desktop client to establish a secure remote viewing session the Player device by connecting to "localhost:33169" on the Administrative PC.