--- title: "ACCESS Tab" slug: "access-tab" status: "update" updated: 2026-05-21T16:51:08Z published: 2026-05-21T16:52:46Z canonical: "docs.zpesystems.com/access-tab" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.zpesystems.com/llms.txt > Use this file to discover all available pages before exploring further. # ACCESS Tab The Access tab enables users to access the Nodegrid device and its corresponding managed devices using the Console, Web and other access connection types. This page provides a list of Nodegrid devices enrolled in ZPE Cloud and Managed Devices enabled, on-demand and discovered on the correspondent Nodegrid device. The page provides the following features: - How to Enable Remote Access on Nodegrid Device - Access Search between Nodegrid devices and Managed devices. - Viewing Nodegrid Devices in ZPE Cloud. - Viewing Managed Devices in ZPE Cloud. - Access Connections to Nodegrid device Web and Console and Managed device Web, Console, KVM and MKS (when configured). - Access Connection with Full Browser Experience of Managed Devices via ZPE Cloud (when configured). **NOTE** Remote Access is required to be enabled to open Access Connections. For more information on how to Enable Remote Access, see the next section or see [Security::Services Section](https://docs.zpesystems.com/docs/general-services-sub-tab1); ## Enable Remote Access on Nodegrid Device The Access page is used to open new Remote Access sessions quickly and it requires Remote Access enabled at the Nodegrid device configuration. For more information on how to Enable Remote Access, see [Security::Services Section](https://docs.zpesystems.com/docs/general-services-sub-tab1); Nodegrid remote access is enabled by default on all SR family devices. For devices not in the SR family, remote access is enabled by default when the user enables ZPE Cloud. To enable ZPE Cloud, do as follows: 1. Login to the device’s Web connection. 2. Go to *Security :: Services*. 3. In the *ZPE Cloud* menu, select **Enable Remote Access** checkbox, then click **Save**. ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-1677595667573.png) ## Access Search The ZPE Cloud provides the ability to search between Nodegrid devices and Managed Devices, allowing easy and fast initiation of remote access sessions. The search bar is located above the table and the search will return any result found containing the substring for any of the following fields: - Nodegrid device: Hostname, Serial Number, Model and Site Name - Managed Device: Name, Type, IP Address and Local Serial Port ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-7LVPIT9C.png) In order to provide programmatic view between different searches, the found results between Nodegrid devices and Managed Devices will have the following behavior: - If the substring matches **both NG and Managed Device**: The NG is displayed and by default, it is expanded with all of its **Managed devices**. - If the substring matches the **NG but not the Managed Device**: The NG is displayed and by default, it is expanded with all of its **Managed devices**. - If the substring matches the **Managed Device but not the NG**: The NG is displayed and by default, it is expanded with only the matched **Managed devices**. - If the substring does **not match either the NG or Managed Device**: **Nothing is displayed.** Next sections will highlight the visualization and information available for Nodegrid devices and Managed devices at ZPE Cloud. **NOTE** The search will return any result found containing the substring for any of the searcheable fields. When searching for NG and/or Managed Device using the search bar, the EXPAND ALL button behavior is performed by default. When clearing the search bar, the COLLAPSE ALL button behavior is performed by default. ## Viewing Nodegrid Devices in ZPE Cloud - Hostname of the device, which you can click to view device details. For more information, see the [Devices Section.](https://docs.zpesystems.com/zpe-cloud/docs/devices-section) - Serial number and model of the device. - Whether the device status is online, offline, failover, never connected, or pending connection. - The geographical site location of the device. - The group to which the device is assigned for access permissions. - The network connection name used on the connection to ZPE Cloud. - Under Connect, the **Console** and **Web** options enable users to launch the device via the console (CLI) application or Web UI. For more information, see the [Access Connections section](https://docs.zpesystems.com/zpe-cloud/docs/access-tab#access-connections). For easier and faster visualization of Nodegrid and Managed Devices, see the [Access Search section](https://docs.zpesystems.com/zpe-cloud/docs/access-tab#access-search). > [!NOTE] > NOTE: > > RELOAD button refreshes the table contents. > > EXPAND ALL and COLLAPSE ALL button expands or collapses the list of managed devices for all the Nodegrid devices listed. ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/Dashboard-Access - List - Screenshot 2025-05-30 182046.png) ## Viewing Managed Devices in ZPE Cloud The managed devices are listed on ZPE Cloud. To see the list and details of the managed devices, click on the arrow column at left side of the Nodegrid hostname. It is an arrow to Expand and Collapse the managed device list. The feature allows users to view name, type, connection status, ip address, local serial port and access connection from managed devices, allowing easier access and management of the managed device within a Nodegrid. The managed device statuses are received from Nodegrid each minute and displayed in corresponding colors for easy identification. The access connection supports different types of access connections. For more information, see the [Access Search](https://docs.zpesystems.com/zpe-cloud/docs/access-tab#access-search) section. > [!NOTE] > **Note**: The managed device list is displayed for Enrolled and Online and in Failover Nodegrid devices. It is **not displayed** for Offline, Never connected or Pending connection status that are not connected to ZPE Cloud. > [!NOTE] > Note: > > The managed devices’ **status** is displayed for the Nodegrid versions from **v6.0.25** onwards. If your Nodegrid device is running a version earlier than that, the column is **not displayed**. > [!NOTE] > Note: under the next ZPE Cloud v2.47.0 > > The managed devices’ **description** is displayed for the Nodegrid versions from **v6.0.31** onwards. If your Nodegrid device is running a version earlier than that, the column is **not displayed**. ![Under Dashboard::Access page with the Nodegrid managed devices expanded](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/Dashboard-Access - Expanded - Screenshot 2025-08-11 123858.png) Dashboard::Access page with the Nodegrid managed devices expanded The available statuses are: - **Connected** - Managed device is successfully connected to the Nodegrid device and it is available for sessions. - **In-Use** - Managed device is successfully connected to the Nodegrid device and in use and therefore not available for sessions. - **Disconnected** - Managed device could not successfully connect to the Nodegrid device and it is not available for sessions. - **Unknown** - The connection status is unknown. This is the default state for devices with the connection mode On-Demand or for new devices for which the discovery process is not completed. You can hover your mouse over the managed device name and the complete name of the device is shown as a tool tip. Clicking on the name, opens a pop-up with the device details and its status. ![Dashboard::Access page with an expanded NG and Drilldowned a managed device to see its information](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/Dashboard-Access - ManagedDevice - Drilldown - Screenshot 2025-08-11 124013.png) Dashboard::Access page with an expanded NG and Drilldowned a managed device to see its information ## Access Connections Some Device pages will include supported access connections: WEB (WebUI), Console (CLI window), KVM, and MKS. Device connection types are: - Nodegrid (Web and Console) - USB Ports (Console) - Serial Ports (Console) - Managed Device (Web, Console, KVM, MKS) **NOTE** Grayed button indicates Access Connection function is disabled. For more information on how to Enable Remote Access, see [Security::Services Section](https://docs.zpesystems.com/docs/general-services-sub-tab1); ### Access a Device Direct device access is available with active buttons. Grayed buttons have no device access. #### Log into a Device 1. To launch a device’s remote connection, in the *Connect* column, click **Connect** button. 2. On the small pop-up dialog, the options are: **CONSOLE** (CLI window) or **WEB** (device UI). After clicking on one of the above mentioned connection options, a device session is initiated and the device can pass one of the following statuses. | Device Status | Message | | --- | --- | | *Waiting device connection:* If the session does not connect immediately and takes a few seconds to establish a connection to the Device Access page in ZPE Cloud, you will see this temporary status page. It displays the identification details of the device you are accessing. Depending on the connection status, this page will either transition to the "Device Could Not Connect" page if the connection fails or the "Device Connection Established" page if the connection is successful. > [!NOTE] > Note > > Maximum time to connect is 120 seconds. | ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/device-waiting.png) | | *Device could not connect:* If the session exceeds the maximum connection time without fully establishing a connection, it will be closed. You will then see this message, which displays the device's identification along with common reasons why it may have failed to connect to ZPE Cloud Remote Access. | ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/device-waiting1.png) | | *Device session expired:* If the session expires due to a timeout or is manually closed, this page appears, indicating that the session has ended. You can then close the tab. | ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/session-expired.png) | | *Device connection established:* If the session is successful and has fully connected, the device login page is displayed. Upon logging in, the Device access page is shown. | ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/login(1).png) | 3. (as needed) On the *Login* page, enter device credentials and click **Login**. 4. If **CONSOLE**, the CLI window displays in a browser window. 5. If **WEB**, the Nodegrid device user interface displays in a browser window. #### Remote Access Possible Errors Below are a couple of cases to identify possible errors occurring when trying to remote access a device. | Error Case | Message | | --- | --- | | **RAS-03-01** Invalid Request: Request is corrupted or missing key fields. Possible solution: Restart the Remote Access session. | ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-7YW9JZ0V.png) | | **RAS-03-02** Unauthorized Request: The session within the device has been terminated or expired. Possible solution: Start a new Remote Access session. | ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-DCL6RRVL.png) | | **RAS-05-01** General failure when handling HTTP/Websocket request: The request could not be performed due to an issue with the host. Could be a Nodegrid or a Managed Device connection issue that is related to the Web Plugin. Possible solution: Restart the Web Forwarder service. | ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-KNZHT3J4.png) | | **RAS-05-02** Browser Forwarder failed during request: The Browser Forwarder is not running or couldn’t process the request. Please contact support for further help. | ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-J2VOV1V3.png) | | **RAS-05-03** Browser Forwarder could not validate session: The Browser Forwarder session has been terminated or has expired. Please contact support for further help. | ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-I7ZY7E74.png) | | **RAS-05-04** Nodegrid's Web Service unreachable: The Nodegrid’s Web Service is not running or it is not configured correctly for Remote Access usage. Please contact support for further help. | ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-2PXU83BG.png) | | **RAS-0X-0X** General device failure: An exact root cause was not identified. Please contact support for further help. | ![](https://cdn.document360.io/763c5fb1-b9af-4ccd-9ad6-cf28ae4cd5a3/Images/Documentation/image-M8UA40GQ.png) | | **SFE-07-01** Remote Access request not accepted by the device. | Possible solution: - Try again in a few minutes. - Start a new Remote Access connection. | | **SFE-07-02** Remote Access request failed to be processed by the device. | Possible solution: - Try again in a few minutes. - Start a new Remote Access connection. | | **SFE-08-01** Remote Access request rejected as invalid. | Possible solution: - Start a new Remote Access connection. | | **SFE-09-01** Device failed to generate the Remote Access token. | Possible solution: - Try again in a few minutes. - Start a new Remote Access connection. | | **SFE-14-01** Reconnection failed the maximum amount of times. | Possible solution: - Try again in a few minutes. - Start a new Remote Access connection. - Check if the device date and time are correct. - Follow ZPE Cloud troubleshooting guides [https://docs.zpesystems.com/guides/docs/how-to-troubleshoot-zpe-cloud-environment](https://docs.zpesystems.com/guides/docs/how-to-troubleshoot-zpe-cloud-environment). | | **SFE-14-02** Connection failed due to Remote Access certificate validation issue. | Possible solution: - Try again in a few minutes. - Start a new Remote Access connection. - Check if the device date and time are correct. - Follow ZPE Cloud troubleshooting guides [https://docs.zpesystems.com/guides/docs/how-to-troubleshoot-zpe-cloud-environment](https://docs.zpesystems.com/guides/docs/how-to-troubleshoot-zpe-cloud-environment). | | **SFE-14-04** Unable to connect to Remote Access. | Possible Solution: - Try again in a few minutes. - Start a new remote access connection. - Check if the device date and time are correct. - Check if the device network is stable and meets ZPE Cloud requirements [https://docs.zpesystems.com/guides/docs/intro](https://docs.zpesystems.com/guides/docs/intro). - Verify DNS, routes, and failover configuration. - Ensure Remote Access services are allowed by firewalls as per [https://docs.zpesystems.com/guides/docs/intro](https://docs.zpesystems.com/guides/docs/intro). - If your network uses traffic inspection tools, verify that the ZPE Cloud connection is explicitly trusted. | | **SFE-15-01** Forwarder service not running. | Possible Solution: - Check device service status. - Follow ZPE Cloud troubleshooting guides [https://docs.zpesystems.com/guides/docs/how-to-troubleshoot-zpe-cloud-environment](https://docs.zpesystems.com/guides/docs/how-to-troubleshoot-zpe-cloud-environment). - Restart the Remote Access connection. | ## Access Connection with Full Browser Experience of Managed Devices via ZPE Cloud Remote access connection to WEB through ZPE Cloud when configured opens a virtual window of the managed device using the default browser. While functional, the virtual window has restricted screen size and limitated capacity to use special combination of characters and shortcuts (i.e.: Ctrl+C, Ctrl+V and Fn shortcuts). Therefore, ZPE cloud now offers an alternative native solution named ‘Browser Forwarder’ that once configured on the [Managed Device access configuration section](https://docs.zpesystems.com/docs/access-sub-tab), delivers a full browser experience with a seamless interface directly within your web browser to the Managed Device access connection. The steps to remote access the WEB connection for Managed Devices with or without the Full Browser Experience is the same, just the configuration of the Managed device needs to be configure to enjoy the experience. See how to start a remote access to the WEB and other types of access connections at [Access Connections section](https://docs.zpesystems.com/zpe-cloud/docs/access-tab#access-connections). **NOTE** The ZPE Cloud previously supported a similar experience provided by the Browser **Extension** option, a browser plugin supported on browsers plugin stores, but the plugin is not supported anymore as part of deprecation from these stores. Nodegrid device versions that supports the option do not work anymore, furthermore, ZPE developed the new Browser Forwarder to enhance and deliver improvements to the previous experience. **NOTE** The **Browser Forwarder** is supported on the Nodegrid versions from **v6.0.28** onwards. If your Nodegrid device is running a version earlier than 6.0.28, the Browser Forwarder is not supported.