cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

DCOM communication error with Linux servers

We are currently running Backup Exec 15 with both Windows and Linux agents.

We are seeing a large number of errors being logged to the Windows Event Log:

DCOM was unable to communicate with the computer LINUX_HOST_NAME using any of the configured protocols; requested by PID      f48 (C:\Program Files\Symantec\Backup Exec\BackupExecManagementService.exe).

Whilst backups are working correctly, Backup Exec is logging the error several times an hour for each server.

We can see that the backup server is attempting to communicate with the agent on port 135 (which is blocked) but connects successfully on port 10000.

Is there a way to stop Backup Exec attempting to communicate with non-Windows agents using the NETBIOS port?

2 Replies
Highlighted

Hello, I am uncertain about

Hello,

I am uncertain about this statement/question: Is there a way to stop Backup Exec attempting to communicate with non-Windows agents using the NETBIOS port? 

However, since the backup jobs are working fine, you can try to fix this DCOM error by adding details of your Non-Windows servers to \windows\system32\drivers\etc\hosts file of your Backup Exec Server. 

I hope it helps! 

This may be due to the Data

This may be due to the Data Discovery which runs every day. Try deslecting the option "Discover data to back up" under BE settings as per https://support.symantec.com/en_US/article.TECH210383.html