Client File Fails To Synchronize To The Server Even After Conflict Resolution; All Ifolders In An Account Fail To Synchronize; Problem Synchronizing Some Files On A Fat32 File System On Linux; Section B.5, "Client File Fails To Synchronize To The Server Even After Conflict Resolution - Novell IFOLDER 3.6 - CROSS-PLATFORM Manual

B.5 Client File Fails to Synchronize to the Server
Even after Conflict Resolution
Conflict resolution does not attempt a re-synchronization on the iFolder. If you select a local copy
instead of a server copy, the file is synchronized only in the next synchronization cycle unless you
perform a forced manual sync. If you select a server copy, re-synchronization is not required.
B.6 All iFolders in an Account Fail to
Synchronize
If all iFolders in an account fail to synchronize, consider the following possible causes:
You are not logged in to the iFolder account.
Click the iFolder Services icon, select Account Settings, select the account, then select Online
to connect to the server. Log in if necessary.
The account is disabled on the client side; that is, the Automatically connect parameter is
disabled.
Click the iFolder Services icon, select Account Settings, select the account, select Properties,
then select Automatically connect.
The server is down or your account is disabled on the server side. Contact your iFolder
administrator for assistance.
Your firewall is blocking iFolder traffic. For information to resolve this problem, see
Section 6.6, "Configuring Local Firewall Settings for iFolder Traffic," on page
Your network connection is down. Check your local network settings.
B.7 Problem Synchronizing Some Files on a
FAT32 File System on Linux
If you create iFolders on a FAT32 file system on Linux, avoid naming files in all uppercase
characters. The VFAT or FAT32 file handling on Linux automatically changes the filenames that are
all uppercase characters and meet the MS-DOS 8.3 file format from all uppercase characters to all
lowercase characters. This creates synchronization problems for those files if the iFolder is set with
the Read Only access right.
To avoid this problem for iFolders on FAT32 file systems on Linux, do one or more of the following:
Use only lowercase characters when naming files in the iFolder. Make sure all members of the
iFolder follow this naming convention.
Make sure the iFolder access right is not Read Only; use the Read/Write or Full Control right
for iFolders on the FAT32 file system.
If an iFolder is shared with the Read Only right, set up the iFolder on a traditional Linux file
system instead of on the FAT32 file system.
![(Bug 84722, Russ Young, Last updated: July 29, 2005)]
64.
Troubleshooting 107