Loading...
Loading...
Users receive "Access Denied" errors when connecting to CIFS shares. Backup jobs fail due to CIFS access issues. CIFS shares appear inaccessible from Windows clients.
CIFS permission issues can occur due to: Authentication failures (Kerberos or NTLM) Incorrect share-level permissions or client access restrictions Missing or misconfigured NTFS file permissions Replication targets enforcing read-only access
Troubleshooting CIFS permissions follows the same principles as Windows Server. Access behavior depends on the interaction between share permissions and file system permissions. If NTFS permissions are incorrect, adjust them using Windows Explorer. A Windows Domain Admin or an authorized user may be required to make these changes. Follow these steps to troubleshoot CIFS permission issues: Verify CIFS Authentication Test connectivity without specifying a share: Start → Run → \\<ddr-hostname|or|IP If the hostname works, Kerberos authentication is successful If the IP address works, NTLM authentication is successful If both work, add the share name to attempt access If both fail, resolve authentication before proceeding Check CIFS Share Permissions On the DD-CLI, display share details: # cifs share show <share-name> For example: ## cifs share show sql Shares information for: sql --------------- share sql --------------- permissions: 1 ACE(s) have been set by MMC clients: * enabled: yes groups: techsupp\sales users: techsupp\abc maxconn: 0 writeable: yes path: /data/col1/data/sql ## Confirm: Users/Groups have access Clients list includes the correct hostnames/IPs Path exists and is writable Adjust permissions using Windows MMC: Computer Management → Shared Folders → Shares → Properties → Share Permissions Only Domain Admins can modify share security settings. Validate NTFS File Permissions On Windows client: Right-click file/folder → Properties → Security tab Ensure required users/groups have appropriate access. Check Replication Status If the path is a replication target, it is read-only: # replication show config To make writable, break replication: # replication break rctx://<context-number> Perform this on both source and destination systems.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.