If you use a local firewall, you must set your firewall to allow iFolder to choose a local dynamic port or configure a local static port for the iFolder client to communicate locally (the same computer) with Mono XSP Server. iFolder uses Mono XSP Web services to communicate via HTTP with the iFolder enterprise servers where you have iFolder accounts. The iFolder administrator configures iFolder services that determine whether communications use HTTP in your environment.
Your firewall does not block traffic between Mono XSP and the iFolder enterprise server because Mono XSP uses the standard HTTP ports for traffic. However, if you block the traffic between the client and Mono XSP, the client has no way to communicate with the server. You cannot log in to your iFolder account and synchronize iFolder data.
Initially, the iFolder configuration does not specify a particular port to use for client-to-Mono XSP communications. When iFolder first runs, it opens an available local port to listen for requests from Mono XSP and to send data to the server via Mono XSP. It writes the port number to a configuration file and uses this port thereafter unless the port is not available whenever iFolder starts. If the port is in use by another application, iFolder selects a different available port, reconfigures the port in the configuration file, and uses the new port thereafter. For example, if iFolder is down and another application takes the port, iFolder must select and configure a different port to use when you restart iFolder.
If you use a local firewall on your computer, the firewall should detect the local traffic between the iFolder and Mono XSP server whenever iFolder contacts the server to synchronize its list of users and iFolder data. Select Allow to permit the iFolder traffic for this session. If you allow the traffic permanently, your firewall should not remind you again, and you can avoid receiving the pop-up alerts whenever iFolder starts.
If you block the iFolder-to-Mono XSP traffic, your firewall prevents you from connecting with the iFolder server and you cannot synchronize your files. iFolder does not detect that traffic is blocked by the firewall; it reports only that it cannot connect to your account on the iFolder server.
You can optionally add the Web Service Port parameter in the port section of the xspport.cfg file to allow Mono XSP Server to use a static port for this local traffic. This port can then be opened in the firewall to allow communications for Mono XSP.
You can find xspport.cfg in the following locations:
|
Operating System |
Location of the Simias.config File |
|---|---|
|
Linux |
/home/username/.local/share/simias/xspport.cfg |
|
Windows |
C:\Documents and Settings\username\Local Settings\Application Data\simias\xspport.cfg |
|
Macintosh |
/Users/username/.local/share/simias/xspport.cfg |
To configure your system to use a specific port:
Configure your firewall to allow traffic for the port you want to use for iFolder traffic.
See your firewall’s documentation for information on how to open a port in the firewall.
Stop the iFolder client by right-clicking the iFolder icon, then selecting Exit.
Modify the xspport.cfg file by adding the Web Service Port Range parameter to the Service Manager section.
<XspPortConfiguration>
<Port>
<monoxsp_port>
</Port>
</XspPortConfiguration>
Replace monoxsp_port with a port number:
Specify a value of a single four-digit port number (such as 1234) to use a single static port. For example:
<1234>
Start the iFolder client.
For more information, see Section 7.2, Starting the iFolder Client.