
Managing iFolder Accounts and Preferences
65
n
ov
do
cx (e
n)
11
Ju
ly 20
08
Your firewall does not block traffic between Mono XSP and the Novell 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, re-configures 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.
Using a Local Dynamic Port
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.
Using a Local Static Port
You can optionally add the Web Service Port Range parameter in the Service Manager section of the
Simias.config
file to allow Mono XSP Server to use a static port or a range of ports for this
local traffic. This port or range of ports can then be opened in the firewall to allow communications
for Mono XSP.
You can find
Simias.config
in the following locations:
Add the Web Service Port Range Setting to the Service Manager section of the
Simias.config
file. For example:
<configuration>
<section name="ServiceManager">
<setting name="WebServicePortRange" value="
monoxsp_port
" />
</section>
</configuration>
Operating System
Location of the Simias.config File
Linux
/home/
username
/.local/share/simias/Simias.config
Windows
C:\Documents and Settings\
username
\Local Settings\Application
Data\simias\Simias.config
Содержание IFOLDER 3.6 - CROSS-PLATFORM
Страница 18: ...18 OES 2 Novell iFolder 3 6 Cross Platform User Guide novdocx en 11 July 2008...
Страница 26: ...26 OES 2 Novell iFolder 3 6 Cross Platform User Guide novdocx en 11 July 2008...
Страница 32: ...32 OES 2 Novell iFolder 3 6 Cross Platform User Guide novdocx en 11 July 2008...
Страница 40: ...40 OES 2 Novell iFolder 3 6 Cross Platform User Guide novdocx en 11 July 2008...
Страница 48: ...48 OES 2 Novell iFolder 3 6 Cross Platform User Guide novdocx en 11 July 2008...
Страница 94: ...94 OES 2 Novell iFolder 3 6 Cross Platform User Guide novdocx en 11 July 2008...
Страница 102: ...102 OES 2 Novell iFolder 3 6 Cross Platform User Guide novdocx en 11 July 2008...
Страница 110: ...110 OES 2 Novell iFolder 3 6 Cross Platform User Guide novdocx en 11 July 2008...