Nx Meta User Manual
The Remote Access Tool (RAT) presents a unified display of remote connections that are available.
Key Concepts:
•Remote Access is disabled when Site Security is set to high.
•Only site administrators and power users can access the RAT settings.
•User accounts configured for Digest Authentication are not allowed to make remote access connections.
•All remote access connections are logged in the Audit Trail of User Actions.
•Always use localhost with the port displayed in the Remote Access Tool.
•The remote connection port will change each time the desktop client is opened.
•A remote access service must be installed on the same machine as the server to be shared.
•Applications that use a port for access, like RDP and SSH, require that the Desktop Client remains open to perform required connection-management tasks in the background
•Applications that do not use a port for access, like TeamViewer and AnyDesk, do not require the Desktop Client to be open while maintaining a remote connection.
•Configure remote connection applications to auto-start and authenticate upon system boot to provide a persistent, remote access connection.
Supported Remote Access Services:
The following remote access services have been tested and many others will likely work without issue:
These services do NOT require port forwarding and an open Desktop Client:
•Any Desk.
These services REQUIRE port forwarding and an open Desktop Client:
•SSH Protocol (openSSH).
•VNC – RealVNC, TightVNC, or UltraVNC.
•RDP – Windows Remote Desktop (Requires Public IP).
Remote Access Requisites:
•The connecting user must be a member of the Site Administrators permissions group, or a member of the Power User group when remote access is granted to power users.
•The Remote Access Tool must be enabled (default) for the Desktop Client to provide port forwarding.
•The server that will receive the remote connection request must be active and online.
•A remote access configuration file must be available to the media server.
•The remote access client must have a network path to the media server.
Router, Gateway, and other network settings are not covered in the Nx Meta user manual.
How to Use the Remote Access Tool:
Follow these steps to create a remote access configuration file on the server to be accessed or shared.
1.Create a file called port_forwarding.json that follows this syntax:
[
{
"name": "RDP",
"port": 3389,
"login": "admin",
"password": "123"
},
{
"name": "SSH",
"port": 22,
"login": "root",
"password": "456"
}
]
2.Copy the port_forwarding.json file to the following locations.
a.Windows: C:\Windows\System32\config\systemprofile\AppData\Local\Network Optix\Network Optix Media Server
b.Linux: computer/opt/Network Optix/mediaserver/var
3.Restart the media server
NOTES:
•The login and password are for the machine providing the remote connection and not the login and password of server being shared.
•Valid credentials must be provided to complete the remote access connection.
•Credentials can be entered when establishing a remote connection or optionally placed in the configuration file so end-users can copy the login and password from the Server Settings -> General dialog.
•The availability of the remote access feature and the path for the port_forwarding.json file will vary on edge devices. Refer to vendor documentation or support services for additional guidance.
Establishing a Remote Access Connection:
1.Open the Main Menu -> Site Administration -> Security dialog.
2.Ensure the Remote Access Tool switch is set to enabled.
3.Close the Site Administration -> Security dialog.
4.Select a server in the resource panel using the context menu (right click).
5.Open the server settings dialog from the menu and select the general tab.
6.The Desktop Client will display tiles with the remote connection parameters.
7.Use the port, login (username) and password to establish remote connection.
a.Example (1) for RDP: Connect via RDP localhost:42207; this will connect to the system via RDP to port 3389 over port 42207.
b.Example (2) for SSH: Connect via ssh -p 35115 user@localhost; this will connect to the system via SSH to port 22 with proxies over port 35115.
8.Close the Remote Connection when all remote tasks are complete.
