What is Web Remote Control?

Web Remote uses a web browser to remote control a test set within the same LAN and/or WLAN/Wi-Fi network environment, No App installation required.

Simply connect the test set's Management Port to the LAN, or to a Wi-Fi access point, so it gets an IP address. Then open a standard web browser on a Win/Mac/Linux PC or iOS/Android tablet or smart phone, enter the test set's IP address on the address/search bar, and a Web Remote Access page (locally hosted by the test set) will be displayed.

If supported by the network and the test set, users may also enter the .local Network Host Name URL that identifies the test set in ZeroConfig/Bonjour/mDNS environments (e.g., RXT012433.local). This information and settings can be found in >Utilities >Settings >More >Remote Access. (The menu structure may vary from product to product.)

VeEX Web Remote Access page, internally hosted by the test set

Select Remote Control, from the menu on the left and enter the Password and click on OK. The mirrored test set screen will be displayed on the Web Browser and users can start interacting with its graphical user interface (GUI). the test set is operated exactly as users do when using the built-in LCD touch screen.

VeEX Web-based Remote Control GUI page, hosted by the test set

The default (Super User) password is pass1, however we highly encourage users to change the password. This password allows full control of the test set. There is a secondary VNC Regular User Password, pass2, that allows users to view the content of the test set screen, however, it doesn't allow control of the test set.

The Web Remote Access page offer extra functionality, when compared to VNC clients, including Test results download, screen capture, software upgrades, etc.

Note: If the computing device running the Web Browser is not on the same LAN where the test set is, users may need to use VPN access to gain connectivity to the target private IP address. In those cases, we also recommend the use of VeEX's EZ-Remote cloud service (if supported by the test set), which doesn't require a VPN connection.

We strongly discourage leaving test sets connected directly to public IP addresses, due to network cybersecurity exposure.