Fix: Error 53 ERROR_BAD_NETPATH with Veeam Agent for Windows 2.1

This post was originally published on this site


I have previously written a blog post about Veeam Agent for Windows management with Veeam Backup and Replication 9.5 U3. In that post, I mentioned the agent upgrade process was not entirely plane sailing. Initial upgrade results in an Error 53 ERROR_BAD_NETPATH error which is a generic Windows error when the source computer cannot contact the destination computer. So what does that look like?

The problem

When trying to upgrade the agent through an agent protection group, I received the following error.

The Fix

Ok, so whats up with that? First thing I checked was, could I browse the machine via UNC path win7democ$. This did not work. As the test machine was not domain joined, I had to disable User Access Control to allow remote access to default hidden system shares using local credentials on the Win7Demo machine. I am sure there is a better way to achieve this, but this is what I did.

So great, I could now browse to the target machine by UNC path, but the error still persisted in Veeam. A little further digging on the interwebs suggested running the following command from a command prompt to replicate the error.

net use

Want to learn more? Read the source post!