Environment
Novell Filr 1.1 Netfolders
Microsoft Windows Server 2012R2
Microsoft Dynamic Fils System (DFS)
Situation
In a Microsoft Windows AD environment, where the File System environment is build up using Domain-Based DFS Namespaces with the target towards a Microsoft Windows Server, Filr is unable to traverse the DFS Namespace towards the target server.
The famtd.log shows the following errors in regards with the Domain Name Server:
famtd[2366]: ERROR:FAMTOperations::ProceesRequest:[sid - wAirVPoXikbGjdrS7CSjFw==] failed unc: //DOMAIN/NS identity: Proxy FILR session: wAirVPoXikbGjdrS7CSjFw==
famtd[2366]: ERROR:thread_handler: request processing failed - FAMT_SERVER_DOWN
famtd[2366]: ERROR:sendStatus: sending status ret: FAMT_SERVER_DOWN
famtd[2366]: ERROR:thread_handler: Exiting thread handler. Error FAMT_SERVER_DOWN
famtd[2366]: ERROR:sendStatus: sending status ret: FAMT_SERVER_DOWN
famtd[2366]: ERROR:thread_handler: request processing failed - FAMT_LOGIN_FAILED
famtd[2366]: ERROR:CIFSOperations::ListAll:[sid - PK+cKn+IN2jN6lOjrRrCeA==] SMBC_Stat failed Connection timed out
A Network trace shows that even though the Net Folder Server is configured with an proxy user that is in the DOMAIN\User or User@DOMAIN format, login attempts are made with WORKGROUP\User.These login attempts are rejected by the DFS target.
famtd[2366]: ERROR:FAMTOperations::ProceesRequest:[sid - wAirVPoXikbGjdrS7CSjFw==] failed unc: //DOMAIN/NS identity: Proxy FILR session: wAirVPoXikbGjdrS7CSjFw==
famtd[2366]: ERROR:thread_handler: request processing failed - FAMT_SERVER_DOWN
famtd[2366]: ERROR:sendStatus: sending status ret: FAMT_SERVER_DOWN
famtd[2366]: ERROR:thread_handler: Exiting thread handler. Error FAMT_SERVER_DOWN
famtd[2366]: ERROR:sendStatus: sending status ret: FAMT_SERVER_DOWN
famtd[2366]: ERROR:thread_handler: request processing failed - FAMT_LOGIN_FAILED
famtd[2366]: ERROR:CIFSOperations::ListAll:[sid - PK+cKn+IN2jN6lOjrRrCeA==] SMBC_Stat failed Connection timed out
A Network trace shows that even though the Net Folder Server is configured with an proxy user that is in the DOMAIN\User or User@DOMAIN format, login attempts are made with WORKGROUP\User.These login attempts are rejected by the DFS target.
Resolution
Before implementing the suggested fix below, first verify the following:
- The Novell Filr Appliance(s) can resolve all hosts involved with both the long and short DNS name.
- The Novell File Appliance(s) can resolve the domain with the long and short DNS name.
- Whether smbclient from the Filr Appliance is able to traverse the DFS Namespace towards the target, using the proxy user and / or Administrator.
- If the Novel Filr Appliance is installed in a DMZ, make sure that all required network ports are open, as in the document ion.
- The target server is up and running, and reachable by the Filr appliance.
If the previously conditions are all met, and the error is observed in the famt.log then proceed with the adjustment of the Filr appliance samba client configuration.
- Enable SSH on the Filr appliance, or use the server prompt via the hypervisor console.
- :# cd /etc/samba/
- :# cp smb.conf smb.org
- :# vi smb.conf
- Search for the workgroup = WORKGROUP string under [ global ]
- Press i to enable editing
- Replace WORKGROUP with the short name of the domain.
- Close vi, with saving the changes by using the Esc key, typing :wq and then the enter key.
- The Novell Filr Appliance(s) can resolve all hosts involved with both the long and short DNS name.
- The Novell File Appliance(s) can resolve the domain with the long and short DNS name.
- Whether smbclient from the Filr Appliance is able to traverse the DFS Namespace towards the target, using the proxy user and / or Administrator.
- If the Novel Filr Appliance is installed in a DMZ, make sure that all required network ports are open, as in the document ion.
- The target server is up and running, and reachable by the Filr appliance.
If the previously conditions are all met, and the error is observed in the famt.log then proceed with the adjustment of the Filr appliance samba client configuration.
- Enable SSH on the Filr appliance, or use the server prompt via the hypervisor console.
- :# cd /etc/samba/
- :# cp smb.conf smb.org
- :# vi smb.conf
- Search for the workgroup = WORKGROUP string under [ global ]
- Press i to enable editing
- Replace WORKGROUP with the short name of the domain.
- Close vi, with saving the changes by using the Esc key, typing :wq and then the enter key.
Additional Information
Other versions of Microsoft Windows Server or NAS devices are potentially affected too, but Novell Technical Services have not encountered them yet.
When upgrading Filr by replacing the system disk as documented (for instance when upgrading from Filr 1.1.0 towards 1.2.0) it may be required to redo the smb.conf configuration as the original does not survive the upgrade.
When upgrading Filr by replacing the system disk as documented (for instance when upgrading from Filr 1.1.0 towards 1.2.0) it may be required to redo the smb.conf configuration as the original does not survive the upgrade.