Syed Jahanzaib – Personal Blog to Share Knowledge !

October 26, 2021

Veeam B&R: Win32 Error / Code: 67 Cannot connect to the host’s administrative share

Continued post from


  • Veeam B&R 9.5 (Ver installed on Windows Server 2012R2


After running the daily job, we were observing following failure notice for particular windows 7/10 OS.

Processing WIN10-LOG Error: Failed to connect to guest agent. Errors: ‘Cannot connect to the host’s administrative share. Host: [WIN10-LOG]. Account: [admin]. Win32 error:The network name cannot be found. Code: 67 Cannot connect to the host’s administrative share. Host: []. Account: [admin]. Win32 error:The specified network name is no longer available.

After some R&D , I had to create a new DWORD value in registry at effected windows , & afterwards the issue got resolved.

Edit the registry on effected Windows & perform following

  1. Click Start, click Run, type regedit, and then press ENTER.
  2. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  3. If the LocalAccountTokenFilterPolicy registry entry doesn’t exist, follow these steps:
    1. On the Edit menu, point to New, and then select DWORD Value.
    2. Type LocalAccountTokenFilterPolicy, and then press ENTER.
  4. Right-click LocalAccountTokenFilterPolicy and then select Modify.
  5. In the Value data box, type 1, and then select OK.
  6. Exit Registry Editor.

On a safe side , perform following as well,

  • Disable windows based firewall
  • Disable windows UAC

Reboot the affected windows machine & now RUN the backup job on Veeam B&R server.

Exporting VEEAM job LOGS for troubleshooting purposes

It’s a good idea to export JOB logs in order to troubleshoot the error in depth.

Follow below veeam article

Syed Jahanzaib

%d bloggers like this: