Skip to content
English
Sign in
Contact us
  • There are no suggestions because the search field is empty.

Advanced NAS Troubleshooting

This guide covers complex NAS backup scenarios for system administrators and advanced users. If you haven't tried the basic setup steps yet, start with our NAS Backup Setup Guide first.

Advanced NAS Troubleshooting for IT Professionals

This guide covers complex NAS backup scenarios for system administrators and advanced users. If you haven't tried the basic setup steps yet, start with our NAS Backup Setup Guide first.

When to Use This Guide

Use this advanced troubleshooting guide if you've already tried the basic setup steps and are encountering:

  • Persistent credential failures despite correct settings
  • Domain controller or enterprise authentication issues
  • Windows 11 24H2 SMB signing conflicts
  • "Channel" errors in backup logs after device setup
  • Complex network infrastructure requirements

Windows 11 24H2 Specific Issues

SMB Signing Requirement Error

Error: "You can't access this shared folder because your computer is configured to require SMB signing"

Cause: Windows 11 24H2 changed SMB security defaults to be more restrictive.

Solution:

  1. Open Group Policy Editor (gpedit.msc)
  2. Navigate to: Computer Configuration > Administrative Templates > Network > Lanman Server > Parameters
  3. Find "SMB client signing requirement"
  4. Set to "Disabled" or "Not Configured"
  5. Restart the computer

Alternative Registry Fix:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters]
"RequireSecuritySignature"=dword:00000000

NTLM Authentication Changes

Issue: Backup fails with "The specified network password is not correct, Error e001001e"

Cause: Windows 11 24H2 restricted NTLM authentication methods.

Fix:

  1. Open Group Policy Editor
  2. Go to: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options
  3. Find "Network security: LAN Manager authentication level"
  4. Change from default to "Send NTLMv2 response only. Refuse LM & NTLM"
  5. Apply and restart

Domain and Enterprise Scenarios

Domain Controller Backup Clients

Special Requirements:

  • Domain controller machines require domain-level user accounts
  • Cannot use local machine accounts for NAS authentication
  • May require "Run as Specified User" configuration

Setup Process:

  1. Create domain user account with appropriate NAS permissions
  2. Add domain user to local "Administrators" group on backup client
  3. Configure backup job with "Run as Specified User" setting
  4. Use domain credentials in both device setup AND job settings

Domain-Joined NAS Devices

For NAS devices joined to Active Directory:

Device Setup:

  • Domain: Enter your AD domain name
  • Username: Domain username (without domain prefix)
  • Password: Domain password

Verification: Test connectivity with: net use \\nas\share /user:DOMAIN\username

SMB Protocol Version Issues

Checking Current SMB Versions

PowerShell Command:

Get-SmbClientConfiguration | Select EnableSMB1Protocol,EnableSMB2Protocol
Get-SmbServerConfiguration | Select EnableSMB1Protocol,EnableSMB2Protocol

Requirements:

  • NovaBACKUP requires SMB 1.1, 1.2, or higher
  • SMB 1.0 only will cause connection failures
  • SMB 3.0+ recommended for Windows 11

Enable Required Protocols:

# Enable SMB 1.1 and 1.2 (run as Administrator)
Set-SmbClientConfiguration -EnableSMB1Protocol $true -EnableSMB2Protocol $true
Set-SmbServerConfiguration -EnableSMB1Protocol $true -EnableSMB2Protocol $true

TLS and Certificate Issues

TLS Version Requirements

Symptoms: Device setup fails with generic "connection failed" errors

Check TLS Versions: Download and run IIS Crypto GUI

Requirements:

  • TLS 1.1 and 1.2 must be enabled
  • TLS 1.0 may be required for older NAS devices

Registry Fix for TLS:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client]
"Enabled"=dword:00000001
"DisabledByDefault"=dword:00000000

"Channel" Errors After Setup

Symptom

Device adds successfully but backups fail with log errors containing "channel" warnings.

Root Cause

Windows Server authentication requirements between backup service and network share.

Solution: Configure "Run as Specified User"

Step 1: Create Local User

  1. Run lusrmgr.msc (Local Users and Groups)
  2. Create new user matching NAS credentials exactly
  3. Add user to local "Administrators" group

Step 2: Configure Backup Job

  1. Open backup job settings
  2. Go to "Run As" tab
  3. Select "Run as Specified User"
  4. Enter same credentials used in NAS device setup
  5. Test credentials using "Check Credentials" button

Step 3: Verify Device Credentials

  1. Go to Device tab
  2. Open NAS device properties
  3. Use "Check Credentials" in Network Credentials tab
  4. Ensure test passes before running backup

OS-Specific Requirements

  • Windows Server 2019/2016: Usually requires "Run As" configuration
  • Windows Server 2022: May not require "Run As" setting
  • Windows 10/11: Depends on network configuration

Complex Network Troubleshooting

Multiple Domain Scenarios

Problem: NAS device on different domain than backup client

Solution:

  1. Use IP address instead of DNS name in device path
  2. Create local user account matching NAS credentials
  3. Configure explicit trust relationship between domains
  4. Test with: net use \\IP.ADDRESS\share /user:NASDOMAIN\username

Firewall and Port Issues

Required Ports:

  • SMB: 445 (TCP)
  • NetBIOS: 139 (TCP)
  • NetBIOS Name Service: 137 (UDP)

Test Connectivity:

telnet NAS_IP 445
telnet NAS_IP 139

DNS Resolution Problems

Test DNS Resolution:

nslookup NAS_NAME
ping NAS_NAME

Workaround: Use IP address in device path instead of DNS name

Windows Credential Manager Conflicts

Symptom

Setup fails even with correct credentials, especially after previous failed attempts.

Solution

  1. Open Control Panel > Credential Manager
  2. Expand "Windows Credentials"
  3. Remove any entries for your NAS IP/name
  4. Clear saved credentials: 
    net use * /delete /yes
  5. Restart and retry device setup

Advanced Command Line Diagnostics

Comprehensive Connection Testing

Test 1: Basic Connectivity

ping NAS_IP
telnet NAS_IP 445

Test 2: SMB Connection

net use \\NAS_IP\share /user:username password
dir \\NAS_IP\share
net use \\NAS_IP\share /delete

Test 3: Authentication Methods

# Test with different auth methods
net use \\NAS_IP\share /user:DOMAIN\username password
net use \\NAS_IP\share /user:username@domain.com password
net use \\NAS_IP\share /user:.\username password

Process and Handle Diagnostics

Check for locked handles:

# Download Microsoft Handle.exe
handle.exe \\NAS_IP

Kill specific processes:

taskkill /f /im explorer.exe
# Then restart: explorer.exe

Specialized NAS Configurations

Buffalo NAS Specific Issues

Common Problems:

  • Default SMB settings may be restrictive
  • Web interface required for user management
  • May require firmware updates for Windows 11 compatibility

Buffalo-Specific Steps:

  1. Access web interface (usually http://NAS_IP)
  2. Enable SMB 2.0/3.0 in sharing settings
  3. Create dedicated backup user with admin rights
  4. Disable guest access if enabled

Synology NAS Considerations

DSM 7.0+ Changes:

  • SMB minimum protocol version increased
  • Advanced folder permissions required
  • May need explicit SMB service restart

QNAP NAS Requirements

QTS Specific:

  • Enable "Microsoft Networking" service
  • Configure "Windows ACL" permissions
  • May require "Network Recycle Bin" to be disabled

Registry-Level Troubleshooting

Force SMB Protocol Version

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters]
"SMB1"=dword:00000001
"SMB2"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"AllowInsecureGuestAuth"=dword:00000001

Disable SMB Signing (Use with Caution)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters]
"RequireSecuritySignature"=dword:00000000
"EnableSecuritySignature"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"RequireSecuritySignature"=dword:00000000
"EnableSecuritySignature"=dword:00000000

⚠️ Security Warning: Disabling SMB signing reduces network security. Only use in controlled environments.

Escalation and Support

Before Contacting Support

  1. Gather Diagnostic Information:

    • Output of net use command
    • Windows Event Viewer system logs
    • NovaBACKUP client logs
    • Network configuration details

  2. Test Basic Connectivity:

    • Can you browse to NAS in Windows Explorer?
    • Does net use command work manually?
    • Are there any antivirus/firewall blocks?

  3. Try Alternative Approaches:

    • Use IP address instead of DNS name
    • Test with local admin account
    • Try different SMB protocol versions

Information for Support Tickets

Include in your support request:

  • Windows version and build number
  • NAS brand, model, and firmware version
  • Network topology (domain, workgroup, etc.)
  • Exact error messages
  • Steps already attempted from this guide

Quick Reference Checklist

Domain Controller Clients

  • [ ] Domain user account created
  • [ ] User added to local Administrators group
  • [ ] "Run as Specified User" configured in backup job
  • [ ] Same credentials used in device AND job settings

Windows 11 24H2 Issues

  • [ ] SMB signing requirement disabled
  • [ ] NTLM authentication level adjusted
  • [ ] TLS 1.1/1.2 enabled
  • [ ] Windows Credential Manager cleared

Complex Network Scenarios

  • [ ] Firewall ports 139, 445 open
  • [ ] DNS resolution tested
  • [ ] SMB protocol versions verified
  • [ ] Alternative authentication methods tried

This advanced guide covers enterprise and complex scenarios. For standard home/small business NAS setup, use our simplified NAS Backup Setup Guide.