#1 Global Leader in Data Protection & Ransomware Recovery

Rescan of Windows Machine in Protection Group Fails With "The network path was not found."

KB ID: 4495
Product: Veeam Backup & Replication
Veeam Agent for Microsoft Windows
Published: 2023-09-21
Last Modified: 2023-09-21
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

During the rescan of a Protection Group or individual Windows machine, the rescan fails with the error:

Unable to install backup agent: failed to connect to <machine_name> Error: The network path was not found. The network path was not found. (ERROR_BAD_NETPATH).
Example Error
Example Log File Content
C:\ProgramData\Veeam\Backup\Rescan\Rescan_of_<protection_group_name>\Task.<machine_name>.log
Info         [KB4495] Trying to install Installer service on 10.10.10.10:6160.
Error        Native method execution failed: install service ex - The network path was not found.
Error        The network path was not found. (ERROR_BAD_NETPATH)
Error        --tr:Error code: 0x00000035
Error        --tr:Failed to create persistent connection to ADMIN$ shared folder on host [10.10.10.10].
Error        --tr:Failed to install service [VeeamDeploySvc] was not installed on the host [10.10.10.10].
Warning      [KB4495] Failed to install Installer service on 10.10.10.10:6160. Reason: The network path was not found.
Warning      The network path was not found. (ERROR_BAD_NETPATH)

A warning similar to the one shown above will occur if the credentials provided are incorrectly formatted. However, it will state "Failed to connect" and be a warning. Credentials must be formatted with a username specified in the down-level logon name format (e.g., either domain\username or hostname\Administrator) and not with a dot slash (i.e., .\Administrator).

Note: Use of a local account other than Administrator will likely fail; see KB4185.

Failed to connect to <name> Details: The network path was not found. The network path was not found. (ERROR_BAD_NETPATH).
Warning

The topics discussed in this article also apply to the error:

The specified network name is no longer available. Failed to connect to share '\\x.x.x.x\ADMIN$'.

Cause

This error occurs when the Administrative share (admin$) of the Windows machine being rescanned cannot be reached.

The error code (0x00000035 or 53 in decimal) is relayed by Veeam Backup & Replication from the underlying Windows OS error "Error 53: The network path was not found."

Possible causes include, but are not limited to:

  • The machine is powered off.
  • DNS is not resolving the hostname or FQDN to the correct IP.
  • A firewall is blocking the connection to the ADMIN$ share.
  • The Windows machine's Server service may be turned off, disabling File and Printer Sharing.
  • The ADMIN$ share is not present.

Solution

Review the troubleshooting steps below, remembering to test rescanning the individual machine in the protection group if a section results in changes being made.

Ensure the Machine is Powered On

Ensure that the Windows machine failing to be rescanned is powered on.

Ensure DNS Resolution is Correct

Note: This stage can be skipped if the Windows machine was added to the Protection Group via IP address.

From the Veeam Backup Server, use nslookup to check the IP of the Windows machine that is failing to rescan. Make sure to use the hostname or FQDN precisely as it was added to the Protection Group. Then, run ipconfig from within the Windows machine and compare the results. If they do not match, resolve the DNS issue.

Ensure Access to Port 445

From the Veeam Backup Server, check if port 445 (default SMB port) can be reached on the Windows machine failing to rescan.

PowerShell example:

Test-NetConnection -ComputerName hostname -Port 445
If the results output states  "TcpTestSucceeded : False," either a firewall is blocking the connection or the Server service is not running within the guest.
Veeam Agent Management Required Ports
While port 445 is the port directly associated with the ADMIN$ share connectivity issue, other ports must be accessible to ensure the full functionality of Veeam Agent for Microsoft Windows. Ensure all firewalls involved have been configured according to the Required Ports for Management of Veeam Agent for Microsoft Windows deployments.

Ensure That the Server Service Is Running

Connect to the Windows machine that is failing to rescan. Open the Services management console (services.msc) and ensure that the Server service is running.

Ensure that the ADMIN$ Share Is Active

Note: By default, the ADMIN$ share is automatically created when the Server service starts. However, this behavior may be disabled if the AutoShareServer value is set to 0 in the HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters key.

Connect to the Windows machine that is failing to rescan and check in Computer Management under Shared Folders > Shares to see if the ADMIN$ share entry is present.

Or use PowerShell to check:

Get-WmiObject -Class Win32_Share | Where-Object { $_.Name -eq 'admin$' }
  • If the ADMIN$ is present, check the other troubleshooting sections.
  • If the ADMIN$ is missing, restart the Server service. If the ADMIN$ share is not automatically created when the Server service is started, open the Registry Editor and navigate to HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters. If the AutoShareServer value is present and set to 0, remove it and restart the Server service again.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.