'Open ports for use of RetailVista'

This document describes the ports to be opened on a firewall when using RetailVista.

If outgoing ports are not blocked in the Internet router (outgoing traffic is usually not blocked by default), this document does not apply. However, there are companies that choose to restrict outgoing Internet traffic. In that case, it is important to keep a number of ports and IP destinations open so that RetailVista can be used.

Filtering outgoing traffic is often referred to as 'URL keyword filtering'. URL filtering is generally supported on more expensive modems. The Alcatel Thomson 510 (which is often supplied with simple DSL connections) does not support URL filtering, but the Alcatel 608 does. NedFox recommends and supplies the Netgear FVS124G VPN server/firewall. This firewall is placed behind the DSL modem. For this reason, it is necessary to configure the DSL modem in 'Bridging mode'.

RetailVista uses the following TCP ports and IP addresses:

*1 - This port number is adjustable and may vary per RetailVista instance. Please inquire about the assigned TCP port for Local Services. These can also be found within eSocrates in eVault.

The URLs mentioned above lead to IP addresses. It is advisable to filter on DNS name rather than IP address (if URL filtering is used). It is possible that NedFox will modify the IP addresses in the future, this cannot be ruled out.

Depending on the hosting environment, special agreements may be made with special URLs or even a situation where a franchise organization wants to host RetailVista itself. Please inquire with the project leader of NedFox if there are any deviations in the respective project. Furthermore, RetailVista POS can still establish connections to other hosts, for example for gift card processing. This depends on which additional licenses are purchased and used.

Note: When blocking outgoing websites, please also consider Windows Updates and any other applications.

NedFox will communicate changes in IP addresses and/or URLs and/or ports as much as possible through an announcement on the website. NedFox is not liable for any consequences in the infrastructure of other parties.