Comprehensive data protection for all workloads
Post Reply
Magion
Influencer
Posts: 12
Liked: 1 time
Joined: Mar 06, 2018 1:10 pm
Contact:

Backup works on Windows 2016 but fails on Windows 2019

Post by Magion »

Ok, I'm probably missing something very simple but can't seem to figure it out.

I have a backup job with a bunch of Windows 2016 servers working fine. But when I add a Windows 2019 server, the backup job is unable to backup the new Windows 2019 server.
Cannot connect to the host's administrative share. Host: [x.x.x.x]. Account: [domain\administrator]. Win32 error:The network path was not found. Code: 53
When I enable file sharing on the Windows 2019 server, the backup works. However a number of Windows 2016 servers don't have file sharing enabled, but are succesfully backup'ed. I compared the firewall settings but see no differences.

Both 2016 and 2019 templates are built in the same way. UAC on, backup using domain administrator.

What could be the reason the backup does work on 2016 but not 2019?
Magion
Influencer
Posts: 12
Liked: 1 time
Joined: Mar 06, 2018 1:10 pm
Contact:

Re: Backup works on Windows 2016 but fails on Windows 2019

Post by Magion »

Using VBR 9.5.4.2866 on Windows 2016. ESXi 6.5 u2
DGrinev
Veteran
Posts: 1943
Liked: 247 times
Joined: Dec 01, 2016 3:49 pm
Full Name: Dmitry Grinev
Location: St.Petersburg
Contact:

Re: Backup works on Windows 2016 but fails on Windows 2019

Post by DGrinev »

Hi Magion,

Can you try to connect to the \\server\admin$ share with Windows Explorer from the backup server machine specifying the credentials?

Thanks!
Magion
Influencer
Posts: 12
Liked: 1 time
Joined: Mar 06, 2018 1:10 pm
Contact:

Re: Backup works on Windows 2016 but fails on Windows 2019

Post by Magion »

I tried accessing the admin share of the Windows 2016 and 2019 servers, and both fail.

Michel
DGrinev
Veteran
Posts: 1943
Liked: 247 times
Joined: Dec 01, 2016 3:49 pm
Full Name: Dmitry Grinev
Location: St.Petersburg
Contact:

Re: Backup works on Windows 2016 but fails on Windows 2019

Post by DGrinev »

Please review this knowledge base article KB1230 for additional information.
If it doesn't help, I'd recommend to contact the support team and let them take a closer look. Thanks!
Post Reply

Who is online

Users browsing this forum: No registered users and 104 guests