#Helix server hosting professional#

The firewall must be set to accept unsolicited connections to Helix Server via port 10850.Given the default configuration, the firewall must be configured as follows. These port numbers are randomly assigned, but are all initiated by Helix Server. (This port number is stored in a resource in the Helix applications that can be changed using a resource editor.) When a request is made (on port 10850) the Helix Server will reply via one or more streams of data, each requiring its own port. By default, Helix Server listens for incoming requests on TCP port number 10850. Communication between Helix Server and Client is as follows. In order for a Helix Client to access a collection hosted by a Helix Server that is protected by a firewall, the network manager must configure the firewall to allow the required traffic. When data is allowed to pass through the firewall, a port is opened between the two networks and the data passes through. The absence of those criteria causes the firewall to block the communication.

When a request is made for data to pass through the firewall, the data is 'filtered' and if the necessary criteria are met, traffic is allowed. the Internet) and the other connects to a private network. A firewall acts as the gateway between the two networks one side of the firewall connects to a public network (e.g. The information below does not apply to Helix 5.3 or later.Ī Helix Client (5.0-5.2) can't reliably connect to a Helix Server that is behind a firewall.Ī firewall, which segments a network into two physical sub networks, restricts unauthorized access to internal networks. This configuration note applies to Helix 5.0–5.2.1 only. TS484: Configuring Helix 5.0–5.2.1 for Access through a Firewall Overview Services techdb Helix 8 Technotes Helix 7 Technotes Tips Issues Scripts Chat Repair Feature Requests Bug Reports FTP FAQs

#Helix server hosting professional#

Technical Educational Professional 3rd Party Contact Us