Part of Setup.INI, in your installation folder.
This property is not part of the Application Configuration dialog.
[RPCManager-ExcludeIP] has no effect unless [RPCManager-AllowIP] has been defined and is not empty.
As described in RAS Clients (see "RAS Clients"), from VTS 5.1502 onwards, a workstation running VTScada can accommodate RAS clients on any subnet, including one already used by a LAN connection. You can achieve this by adding an [RPCManager-ExcludeIP] section to Setup.ini, and instructing the RPC Manager via this section to not create or accept connections with specific IPs or subnet ranges.
By specifying the IP that the RAS host presents as its own IP to the RAS client, the RAS client will not create a connection to the RAS host IP, but will only connect to the other IPs by which the host workstation is known.
For example, if a workstation running VTScada had an IP of 192.168.0.40, and that workstation was configured to support a RAS client, such that the RAS client would see the host workstation as 192.168.0.150, and the RAS client would be assigned an IP address from a pool of addresses from the range of 192.168.0.151 to 192.168.0.155, then the following section should appear in the RAS client's Setup.ini file, so that the RAS client will only make a connection to 192.168.0.40 (which will b done over the RAS link), and not to 192.168.0.150:
[RPCmanager-ExcludeIP]
IP = 192.168.0.150
Note that this is not necessary if the RAS IP address pool is on a different subnet from any other IP of the RAS host, so long as no routing exists between the two subnets.
From VTScada version 5.18 onwards, it is not necessary to exclude any IP addresses on the server, however, if the IP cannot be accessed by a connecting client VTScada system, it is advisable to exclude it from the RPC Manager's view using the method exemplified above.
To refuse all inbound RPC connections and prevent all outbound connections, set only the local machine's IP address in the AllowIP section:
[RPCManager-AllowIP]
IP = 127.0.0.1
