There are no special port requirements from the software's perspective, only the standard HTTP and HTTPS ports, 80 and 443, or requests may be routed through a proxy server if your network uses one.
How to Manually Configure Voyant with Network Proxy Settings
In most cases, the Java Runtime Environment will automatically detect and use any special proxy settings or scripts from the computer's default browser. However, this auto-detection is not always fool proof, so in some cases, depending on the network, users may need to configure the software manually to communicate through a proxy server. Manual configuration settings can be found on the Login dialogue, after installing and launching the software. Again, these settings are only required on an as needed basis.
Tip: If you are having problems launching Voyant but aren't sure whether your requests are being routed through a local or network proxy server, a good place to check is in your browser's settings on the computer in question. Read more >>
Voyant operates through Java WebStart. In cases where computers are running local firewalls, settings for the firewall may need to be configured to grant Java full internet access. The Windows firewall, for example, is configured to automatically allow Java internet access whereas such access may need to be granted explicitly in other third-party firewall systems.
If you find that Voyant is unable to connect to the internet or to the Voyant server, please reference the documentation from your third-party firewall provider or contact their support staff on how to allow access. You may also check your network firewalls to determine whether the software being allowed to connect to and pass files to and from:
via HTTPS ports 80 and 443.
Required IP addresses
The IP addresses for our production servers are currently, at time of writing, 188.8.131.52 and 184.108.40.206.
Required content types
The content types used by Java Web Start and Voyant are
Required file types
Files with extension
The .jar and .pack.gz files contain binary data.
Some network firewalls alter or strip information from the headers of messages received through their networks. You will need to ensure that the headers in responses from our servers, which contain important version information, are not altered or stripped by any network proxy servers. The Java Web Start component of the JRE is looking for a specific header (x-java-jnlp-version-id) in the response from our web servers when it requests the application resources. On very rare occasions we have found that some firms operate through firewalls and/or proxy servers which remove these headers from the response.
If you would like to test this outside of the Java environment, the URL format for a versioned resource is as follows.
Below is the expected response as picked up by a network request monitoring tool (We used Fiddler with Firefox).
HTTP/1.1 200 OK
Date: Thu, 07 Jul 2011 12:44:56 GMT
Last-Modified: Wed, 06 Jul 2011 22:08:32 GMT
Set-Cookie: BALANCEID=balancer.app1; path=/; domain=planwithvoyant.co.uk
Keep-Alive: timeout=15, max=100
For Further Reading