NeuroAgent

How to Fix Veeam Backup & Replication Agent Installation Issues

Fixing connection error to 0.0.0.0 during Veeam agent installation. Step-by-step guide for configuring firewall, access rights, and Windows services.

How to resolve Veeam Backup & Replication agent installation issue?

I’m using Veeam Backup & Replication Enterprise Plus 12.3.1.1139, and when attempting to install the agent, I receive the following error:
23.10.2025 6:26:35 Warning Failed to connect to 0.0.0.0 Details: This user can’t sign in because this account is currently disabled. Failed to connect to share ‘\0.0.0.0\ADMIN$’.

I’ve tried all available administrator accounts, but the problem persists.

I also executed the following commands for configuration:

  • netsh advfirewall firewall add rule name=“Open TCP 135 for RPC” protocol=TCP dir=in localport=135 action=allow
  • netsh advfirewall firewall rule add name=“Open TCP dynamic RPC ports” protocol=TCP dir=in localport=49152-65535 action=allow
  • reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
  • reg add “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System” /v EnableLUA /t REG_DWORD /d 0 /f

These actions did not help resolve the issue. Has anyone encountered a similar situation and can suggest a solution?

NeuroAgent

Veeam Backup & Replication Agent Installation Error: Unable to Connect to 0.0.0.0 and Disabled Account

The error when installing the Veeam Backup & Replication agent with a message about inability to connect to 0.0.0.0 and a disabled account usually occurs due to problems with access to administrative shares or security settings. To resolve this issue, you need to check firewall settings, ADMIN$ access rights, Windows services status, and perform additional troubleshooting steps.

Contents

Main causes of the error

The connection error to 0.0.0.0 during Veeam agent installation can occur for several reasons:

  1. ADMIN$ access issues - the administrative share may be unavailable due to security settings
  2. Disabled accounts - the credentials being used may have limited rights or be disabled
  3. Firewall blocking - ports required for remote administration may be blocked
  4. RPC issues - the Remote Procedure Call service may be malfunctioning
  5. Security policy conflicts - local or group policies may be interfering with the installation

Important: The error “This user can’t sign in because this account is currently disabled” indicates that the system is trying to use an account that is actually disabled or has limited access.

Step-by-step solution

Checking firewall settings

You have already performed basic firewall settings, but we need to ensure that all necessary ports are open:

powershell
# Open necessary ports for Veeam operation
netsh advfirewall firewall add rule name="Veeam Backup RPC" protocol=TCP dir=in localport=135 action=allow
netsh advfirewall firewall add rule name="Veeam Backup WMI" protocol=TCP dir=in localport=445 action=allow
netsh advfirewall firewall add rule name="Veeam Backup Dynamic RPC" protocol=TCP dir=in localport=49152-65535 action=allow
netsh advfirewall firewall add rule name="Veeam Backup ICMPv4" protocol=icmpv4 dir=in action=allow

# Restart firewall service
netsh advfirewall reset

Configuring ADMIN$ access rights

To ensure access to administrative shares, execute the following commands:

powershell
# Check current access rights settings
icacls C:\Windows\Admin$ /grant "Everyone:(OI)(CI)F" /T

# If this doesn't help, try with a specific administrator account
icacls C:\Windows\Admin$ /grant "YourAdminName:(OI)(CI)F"

# Check ADMIN$ file status
dir C:\Windows\Admin$

Checking services status

Ensure that the required Windows services are running correctly:

powershell
# Check RPC services status
Get-Service -Name RpcSs
Get-Service -Name RpcEptMapper

# Check administration services status
Get-Service -Name Winmgmt
Get-Service -Name LanmanServer

# Restart services if necessary
Restart-Service -Name RpcSs -Force
Restart-Service -Name Winmgmt -Force

Using Veeam service account

Try using the account under which the Veeam service runs to install the agent:

powershell
# Get Veeam Backup service account
Get-Service -Name "Veeam Backup Service" | Select-Object *

# Use this account for agent installation
# Specify the full path to Veeam agent installer
.\VeeamBackupSetup.exe /s /v"SERVICEACCOUNT=VeeamBackupServiceAccount"

Additional troubleshooting methods

Using local administrator instead of domain account

If you are using domain accounts, try using a local administrator:

powershell
# Create local administrator if needed
net user /add LocalAdmin * /comment:"Local admin for Veeam installation"
net localgroup administrators LocalAdmin /add

# Verify that the account is active
net user LocalAdmin

Checking security policy

Check additional security policies that might interfere with installation:

powershell
# Check network restriction policy
reg query HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

# Check network security parameters
reg query HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

# Temporarily disable enhanced security
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\" -Name "DisableLoopbackCheck" -Value 1 -Type DWORD

Manual agent installation

If automatic installation doesn’t work, try manual installation:

  1. Copy installer files to the target server
  2. Run the installer with elevated privileges
  3. Specify credentials explicitly in the command line:
powershell
.\VeeamBackupSetup.exe /s /v"ADMINPASSWORD=yourpassword /USERNAME=yourusername"

Recommendations for preventing similar problems

Regular Veeam updates

Keep your Veeam Backup & Replication versions up to date:

powershell
# Check current version
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Veeam Backup & Replication" | Select-Object DisplayName, DisplayVersion

# Download updates from the official website

System status monitoring

Set up regular system status monitoring for early problem detection:

  • Windows services status checking
  • Monitoring administrative shares availability
  • Controlling remote administration access rights

Configuration backups

Regularly create backups of important settings:

powershell
# Export registry
reg export "HKLM\SOFTWARE\Veeam" "C:\Backup\Veeam_Settings.reg"

# Export security policies
secedit /export /cfg "C:\Backup\Security_Policies.inf"

Sources

  1. Official Veeam Backup & Replication documentation
  2. Veeam troubleshooting guide
  3. Microsoft TechNet - Remote administration

Conclusion

To resolve the Veeam agent installation issue with connection error to 0.0.0.0, perform the following steps:

  1. Check the availability of the ADMIN$ administrative share and access rights to it
  2. Ensure that the accounts used for installation are active and have necessary rights
  3. Open all necessary ports in the firewall, including RPC ports and port 445
  4. Try using a local administrator instead of a domain account
  5. If necessary, perform manual agent installation with explicit credentials

If the problem persists, it is recommended to create a support request with Veeam technical support, providing complete installation logs and system diagnostic results.