NinjaOne Backup — Error 315: NAS Authentication Failed
Audience: T1 / T2 Use when: Backup fails with "Error 315: Credentials failed when authenticating to Network Storage device."
What This Error Means
Lockhart reached the NAS (network connectivity is fine) but the NAS rejected the authentication attempt. The credentials stored in NinjaOne's backup storage location don't match what the NAS currently requires.
Most Common Causes
| Cause | Signal |
|---|---|
dtcbackup password was changed on the NAS but not updated in NinjaOne |
Error started after a NAS password rotation |
dtcbackup account was deleted or disabled on the NAS |
Account doesn't appear in NAS user list |
| NAS was factory reset — cleared all local accounts | All NAS settings reset |
| NAS was replaced with a new unit | New NAS, no dtcbackup account created yet |
| SMB authentication negotiation failure (version mismatch) | Connectivity works but auth fails even with correct credentials |
Step 1 — Test Authentication Manually
# Try to map the share with dtcbackup credentials
# Replace with actual NAS hostname and the dtcbackup password from IT Glue
net use \\NAS-HOSTNAME\backups\ninjaone /user:dtcbackup [password]
# If "Access denied": credentials are wrong or account is locked/deleted
# If "Network path not found": connectivity issue (different problem — see Error 316)
# If it works: credentials are fine — the issue is with how NinjaOne stored them
Step 2 — Verify dtcbackup Account on the NAS
Synology DSM:
- Control Panel → User & Group → Users tab
- Find
dtcbackup— confirm it exists, is not disabled, and is not expired - Check the account's share permissions: it should have Read/Write on
backups
QNAP QTS:
- Control Panel → Privilege → Users
- Find
dtcbackup— confirm active - Check Shared Folder Permissions for
backups— should be Read/Write
Step 3 — Update Credentials in NinjaOne
If the password was changed on the NAS or a new NAS was set up:
- NinjaOne → Administration → Organizations → select the client org
- Org settings → Backup → Storage Locations
- Click the storage location → Edit
- Update the Username and Password fields with the current
dtcbackupcredentials - Save
- Trigger a manual backup run
Step 4 — Recreate the dtcbackup Account (If Deleted)
If the account was removed:
Synology:
- Control Panel → User & Group → Create
- Username:
dtcbackup, password per DTC credential standard - Do NOT add to the administrators group
- Shared Folder Permissions: Read/Write on
backupsonly - Update NinjaOne storage location credentials (Step 3)
QNAP:
- Control Panel → Privilege → Users → Create
- Same naming and permission structure
Step 5 — SMB Version Check (If Credentials Are Correct But Auth Still Fails)
If credentials are verified correct but Error 315 persists, the issue may be SMB authentication negotiation:
# Check SMB negotiation with NAS
Get-SmbConnection | Where-Object {$_.ServerName -like "*NAS*"} | Select ServerName, Dialect, UserName
# If Dialect is 1.0 on a Windows Server 2016+ device: SMBv1 authentication behavior may differ
Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol
Update NAS firmware to support SMBv2/v3 if SMBv1 mismatch is the cause.
If
net usereturns "System error 86 — the specified network password is not correct" (not Access Denied), the password is verified correct, and the same credential works from another machine: this is an NTLM auth-level (LmCompatibilityLevel) problem on the affected server, not an SMB dialect issue and not a NinjaOne credential issue. See NinjaOne Backup — SMB Credentials Rejected (System Error 86): LmCompatibilityLevel / NTLMv2.