Determining network settings – Interlogix TruPortal User Manual
Page 20
Preparing for Configuration
8
TruPortal Software User Guide
Determining Network Settings
Before using the Installation Wizard to perform an initial configuration of the System Controller,
consult with the site network administrator to determine the answers to the following questions:
•
Should the IP address of the System Controller be static or dynamic? Operators will access
the User Interface by typing the System Controller’s IP address into a web browser address field.
If the IP address of the System Controller uses the Dynamic Host Configuration Protocol
(DHCP), then operators must use a virtual URL or other alias to access the System Controller. If
the actual IP address assignment is changed by the network, the operators will not be able to find
it.
•
Should the Service Port be changed? The default Service Port for an HTTPS connection is
443; the default value for an HTTP connection is 80. Typically, this port only needs to be
changed if it conflicts with an existing port used on the network. If the port is changed, users will
need to append the port number to the IP address of the System Controller to log into the System
(e.g., https://IPaddress:port).
Note:
Ports 0 through 1024 (i.e., well-known ports) are reserved for privileged services. It is
recommended that these ports not be used as the service port.
•
If a static IP address will be used, what are the subnet mask, default gateway, and Domain
Name Server (DNS) values for the network? This information will be needed when
configuring network properties for the System Controller.
•
Should a Hypertext Transfer Protocol Secure (HTTPS) connection be used? HTTPS is
highly recommended to prevent unauthorized access to the System. This secure protocol encrypts
the packets between the client browser and the System Controller, preventing someone from
gathering user information by spying on network traffic. There may be circumstances that require
non-secure HTTP. For example, if the System Controller is accessed through a Web proxy server
that does not support HTTPS, then the only option is to disable HTTPS.
After installation, the System can also be configured to use a Secure Shell (SSH) connection that
authenticates remote client workstations and allows remote users (including technical support
representatives) to log into the System. Refer to