MABS · TROUBLESHOOTING

MABS Agent Communication Troubleshooting Guide

Troubleshoot MABS agent communication failures by checking services, firewall, name resolution, credentials and connectivity.

Practical Runbook6 StepsIssues → Solutions → Recommendations
!Issue

Troubleshoot MABS agent communication failures by checking services, firewall, name resolution, credentials and connectivity.

Solution

01 Confirm the protected server

Recommendations

03 Test name resolution Confirm the MABS server and protected server resolve each other correctly.

Verify the correct computer name, IP address and MABS agent version.

01

Confirm the protected server

02

Check required services

Review the MABS protection agent services and Windows event logs on the protected server.

03

Test name resolution

Confirm the MABS server and protected server resolve each other correctly.

04

Check firewall and RPC

Validate the network path and required Windows communication ports according to the deployed MABS architecture.

05

Review agent logs

Correlate MABS agent events with the time of the failed synchronization or consistency check.

06

Validate protection

Run a controlled synchronization and confirm the datasource returns to a healthy protected state.

Explore more TechRunbook guides

Continue with practical infrastructure troubleshooting, PowerShell scripts and operational runbooks.

Browse all articles →