Offline file synchronization fails to complete on a computer that is running Windows 7. Additionally logging the error message, "The specified network name is no longer available" in the Sync Center.
To fix this issue, apply the hotfix available on the Microsoft Support web site.
Cause: This error occurs on a computer that is running Windows 7, when Oplocks is disabled on the CIFS server or folders are taken offline on the client machine.
Enable Oplocks on the CIFS Server (Oplocks are enabled by default).
Delete the offline copy of the folder on the Windows client system.
For more information, see Section 6.8, Enabling Offline Files Support and Section 13.3.6, Oplocks in the OES 11 SP2: Novell CIFS for Linux Administration Guide.
CIFS client on Windows 2000 Service Pack 4, Windows XP Service Pack 2, Windows Vista, Windows 7 or later releases, Mac 10.7 or later releases might have problems following DFS junctions over CIFS because of a defect in Windows and Mac client versions. (This problem exhibits itself in a pure Windows environment.) When using DFS with CIFS, this issue will be seen if the CIFS server and Windows / Mac clients are on different IP subnets. In this case, the client must have a way to resolve the CIFS server name in order for DFS to work properly. This is a Microsoft / Mac CIFS client requirement, not a CIFS Linux server requirement.
NOTE:This problem does not affect Windows clients that use the Novell Client.
There are multiple ways the client can resolve the CIFS server name:
Configure both the client and server for the same WINS server.
Configure both the client and server to use the same DNS server.
Modify the hosts file for all client computers with appropriate entries for any volumes on OES servers that use DFS junctions.
To modify the hosts file on a client:
In a text editor, open the hosts file.
Windows 2000: c:\WINNT\system32\drivers\etc\hosts
Windows XP/Vista/7 or later: c:\windows\system32\drivers\etc\hosts
If you do not have a hosts file, create the file.
Mac 10.7 or later: /etc/hosts
A line at the end of the file that identifies the IP address and NetBIOS name of the data server, such as.
Replace 192.168.1.1 with the actual IP address and replace servername with the name of your server.
IMPORTANT:It is not possible to modify the CIFS server name of the virtual server with iManager. However, it is possible to modify the CIFS server name for a physical server.
We recommend that you do not modify the CIFS server name of the physical server that is the DFS target.
For example, suppose you have the following server:
Server IP address: 10.10.1.1. If the DFS target is a cluster resource, use the <Cluster IP address> or <Cluster Resource IP address> in place of the server IP.
Server name: USERSVR
NetBIOS server name: USERSVR_W
If the target of the junction is a cluster resource, use the <Cluster IP address> or <Cluster Resource IP address> and instead of the server name, use the cluster resource name.
The line you add to the hosts file is:
The string length of the NetBIOS name should not exceed 15 characters. The host name or the last 13 characters from the host name (whichever is shorter) is considered and appended with _W at the end to frame the standard NetBIOS name.
Save and close the hosts file.
On each client, map a network drive to the user’s data volume.
Continuing the example above, the user could map to \\10.10.1.1\VOL1 or to \\USERSVR_W\VOL1.
In the Windows Explorer file manager, click.
In thefield, type one of the following:
Replace 192.168.1.1 with the actual IP address or servername with the hostname of your server.
Cause: Theoption is enabled in MS Office 2010.
Action: To ensure the temporary files are not stored in the server, disable the Enable for Editing option in MS Office 2010.
Cause: The users are by default created with the cn qualifier. If you create a user with the uid qualifier, the user cannot access the CIFS shares.
Action: Ensure you create a user with the default cn qualifier.