How to configure vSpace to scan terminals in other subnets
Our vSpace Console is equipped with a feature that allows it to be programed to include other subnets in the network than the local one.
You can configure it by calling the vSpace Console, then Manage Devices > Networks > + > [add IP range to be discovered].
This feature does not overcome the need to configure properly your security for the allowance of our protocol across subnets. For reference on security configuration, please check this article:
If you are doing a WAN deployment please be aware of this article:
REV. 09/2019
Related Articles
vSpace Console Crashing when launched or scanning devices in the network.
We are monitoring rare occurrences in which the vSpace Console crashes. When launched or when scanning devices. One particular issue related to the firmware of the present devices is what is addressed in this article. The issue has been seen in ...vSpace Pro Installation - Tips, References and Process Detail
Published The following article is a detailed process and tips for installing our vSpace Pro platform (vSpace Pro LTS, vSpace Pro Enterprise Edition). As an additional supplement, this article will deal with all other aspects of Pre-Deployment and ...Tips: How to Enhance Video Performance on vSpace Products.
vSpace, our virtual desktop platform, has an architecture that is designed for a rich performance and delivery of desktops on its lineup of thin clients. One of the features that our platform offers is the delivery of high resolution video. For ...vSpace Console application may crash
When using vSpace console in vSpace version 10.3.4.2, if using the option to scan remote LAN's for devices. If the devices on the remote network are 1.11.x or other versions from vSpace 6 \ 7 \ 8, this may cause the console application to fail. if ...Resetting the vSpace Console Password
"Classic Versions" like vSpace 6 will be permanently discontinued after June 30th, 2020. Please upgrade promptly to our latest platform vSpace Pro. If you are using version 6 because of terminals that are not compatible with vSpace Pro 11 or ...