Section 11.8.4, Not Able to Change Authentication Mode in iManager
Section 11.8.7, Windows or Mac Unable to Resolve the NetBIOS Name of the CIFS Server
Section 11.8.8, Temporary Files Created On the OES Server By MS Office 2010 Are Not Deleted
Section 11.8.9, Users Created Using UID Qualifier Cannot Access CIFS Shares
Cause: When a file from a redirected folder is deleted by pressing Del or from the File menu, the file is moved to the folder specific recycle bin rather than completely deleting it. This is a Windows client behavior.
Action: The Windows client behavior can be changed by using the registry setting NukeOnDelete at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\BitBucket\KnownFolder.
Set NukeOnDelete (REG_DWORD) 0 (move to recycle bin) or 1 (delete) to 1. The files will not be moved to recycle bin but will be completely deleted and available in the NFARM salvage purge list.
The Windows client sends multiple login or logout requests based on the number of CIFS connections to the OES server and this gets logged in the audit.log or messages files. This is a Windows behavior observed after successful folder redirection operation.
Cause: The cached Kerberos credentials does not have supervisor rights to add or remove OES objects from the computer directory.
Action: Execute kinit to obtain the Kerberos credentials of an AD supervisory user. For example, kinit Administrator@EXAMPLE.COM.
Where “Administrator” is domain admin or an user with sufficient rights and “EXAMPLE.COM” is the AD domain.
NOTE:Ensure that the AD domain name is in capitals.
If SMB2 or SMB3 is the current dialect, iManager plug-in prevents changing the authentication mode from 'Local' to 'Domain (Passthru)'. It throws the error message, "The parameters to CIFS_SetServerConfiguration are not valid for this server type".
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.
Action:
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 5.10, Enabling Offline Files Support and Section 13.3.5, Oplocks.
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 Client for Open Enterprise Server.
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.
192.168.1.1 servername_W
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:
10.10.1.1 USERSVR_W
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.
If necessary, repeat Step 1 to Step 3 on each client computer, or create a hosts file and distribute it to the client machines.
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 Tools > Map Network Drive.
In the Folder field, type one of the following:
\\192.168.1.1\volumename
\\servername_W\volumename
Replace 192.168.1.1 with the actual IP address or servername with the hostname of your server.
(Optional) Select Reconnect at Logon.
Click Finish.
Cause: The Enable for Editing option 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.
Description: Ticket Granting Ticket (TGT) expiration errors are seen if the NIT setting ad-tgt-refresh-timeout is more than the "Maximum lifetime for a user ticket" in the Kerberos policy of the domain.
Action: To avoid TGT expiration errors, ensure that the ad-tgt-refresh-timeout value is less than Active Directory TGT expiration time.
Description: If the Active Directory user is denied access possibly the user is not assigned a valid UID.
Cause: Run the nitconfig get command and check if ad-uid-generate-mode parameter is set to 0. Setting this parameter to 0 means NIT operates in Fetch mode for Active Directory users and tries to fetch UIDs for those users from Active Directory. If the users do not have UIDs assigned in Active Directory you might encounter this error.
Action: When you choose to fetch UID for Active Directory users, NIT fetches the uidNumber attribute set in Active Directory for all the Active Directory users. If UID is not set for a particular user, that user cannot access NSS file systems. If you are configuring NIT in fetch mode for Active Directory users, ensure that the Active Directory users who require access to NSS filesystems have UID numbers set in the Active Directory. Add the uidNumber attribute explicitly to the Global Catalog server as it is not part of default attributes. For more information about replicating UID numbers to the Global Catalog server, refer to the Microsoft Support website.
Description: eDirectory is down and NIT is not able to fetch tree name.
Action:
Start eDirectory by running the rcndsd start command.
Start NIT by running the rcnovell-nit start command