Skip to main content

NinjaOne Backup — Error 316: No Host Found for Network Storage

Audience: T1 / T2 Use when: Backup fails with "Error 316: No host found for Network Storage."

What This Error Means

Lockhart is trying to connect to the NAS using the hostname in the configured UNC path, but cannot resolve or reach that hostname. The NAS either doesn't exist at that address, the hostname doesn't resolve in DNS, or the NAS is offline.

This is a connectivity or DNS failure — not a credentials issue.

How 316 Differs from 315

Error What Happened
315 Host was found, but authentication was rejected
316 Host could not be found at all — DNS or connectivity failure

Step 1 — Basic Connectivity Test

# Can the device reach the NAS hostname?
Test-NetConnection -ComputerName "NAS-HOSTNAME" -Port 445

# Can DNS resolve the NAS hostname?
Resolve-DnsName "NAS-HOSTNAME"

# If both fail: NAS is offline, wrong hostname, or DNS is broken
# If DNS fails but ping by IP works: DNS is the issue

Step 2 — Check If the NAS Is Online

  1. Attempt to access the NAS admin panel in a browser: http://NAS-HOSTNAME:5000 (Synology) or http://NAS-HOSTNAME:8080 (QNAP)
  2. Or ping the NAS IP directly:
# Ping by IP address (get from IT Glue or NinjaOne device list)
ping 192.168.1.X

If the NAS is offline: power it on. If it's not reachable even by IP, check the switch port and power.

Step 3 — Check the UNC Path in NinjaOne

If the NAS hostname was changed (a new NAS was installed, or the hostname was renamed):

  1. NinjaOne → Organization → Backup → Storage Locations
  2. Check the current path — does the hostname in the path still match the NAS's current hostname?
  3. If not: update the path to the new hostname and save
# Confirm the NAS's current hostname from the device
# (Works if NAS is reachable)
Resolve-DnsName "192.168.1.X"  # Replace with actual NAS IP

Step 4 — Check DNS Resolution for the NAS Hostname

If the NAS is online but the hostname doesn't resolve:

# Test DNS from the device
nslookup NAS-HOSTNAME
# Should return an IP address matching the NAS

# If NXDOMAIN: the hostname isn't registered in DNS
# If times out: DNS server isn't responding

If DNS is failing:

  • Verify the device is using the UDM as its DNS server (DTC standard)
  • Verify the NAS has a DHCP reservation or static IP in the UDM so its hostname is stable
  • If using DHCP hostname registration: confirm the NAS is registering itself correctly in the UDM's DNS

Quick fix: Use the NAS IP address in the UNC path instead of hostname (not ideal long-term but unblocks backup immediately):

In NinjaOne storage location: change \\NAS-HOSTNAME\backups\ninjaone to \\192.168.1.X\backups\ninjaone

Step 5 — VLAN/Network Isolation

If the NAS is on a different VLAN than the device:

  • Verify inter-VLAN routing allows SMB (port 445) between the CORP VLAN and the NAS
  • On the UDM: Settings → Firewall → confirm no rules block CORP → NAS traffic on port 445
Back to top