Error Message

An error was encountered while attempting to browse the contents of \\\D$. A communication failure has occurred.

Sgmon log :

BEREMOTE: [2224] ndmpConnectEx : Control Connection information: A connection was established between end-points 192.168.1.18:4772 and 10.47.1.99:10000.
BEREMOTE: [2224] NDMP version 3 connection CONNECTED
BEREMOTE: [2224] ERROR: sending message 0xf33b: not supported.
BEREMOTE: [2224] ERROR: ndmpSendRequest failed:
BEREMOTE: [2224] ERROR: ndmpConnectClientAuth

Scenario 1

Remote agent version mismatch

BEWS Media server is a lower version than the Remote agent on Linux - Unix (i.e:  BEWS media server on Version 22.0 and remote agent on version 22.2 )

Ensure an appropriate version of Remote agent is Installed  on the Linux/Unix server.

Scenario 2

NDMP Port 10000 is in use by other application on the remote Linux- Unix box

Details :
With the introduction of Remote Agent for Linux & UNIX Servers (RALUS) , Backup Exec now uses well known NDMP port 10000 for UNIX\Linux backup and restore operations. There are times when this port is busy or in use by another process. In such cases, it's important to find out if port 10000 is really in use.

1. Ensure that Port 10,000 is not in use on the Remote Server.

Note:
If it is not possible to change the third party application port , the port for Network Data Management Protocol (NDMP) used by Backup Exec Remote Agent for Linux and UNIX servers on a UNIX/Linux machine can be changed.

Caution: When changing the port for NDMP, the changes must take place on every server in the environment that needs to be protected by Backup Exec. ( Only For version 10 x )  

Scenario 3:

"Firewall" is enabled on the remote UNIX\Linux server in Backup Exec for Windows Servers

For Successful Backup, the following ports need to be opened at Firewall:
Port 10000 (NDMP Control Port) & Range of Dynamic ports. (Example: Dynamic Data Port range : 1025-65535).

Note: This is the full available range but administrators can decide and have a specific range opened at the Firewall. Veritas recommends having port 10000 open and available on the Backup Exec media server as well as on the remote systems. In addition, you must also open the dynamic port ranges as mentioned above, specified for communications between the media server and remote agents. Therefore, it is important to understand that its the combination of two ports (Control + Data) that makes the data, successful data backups. Communication between the media server and the Remote Agent will usually require up to 2 ports on the remote agent side per backup operation. If you plan on supporting multiple backups and restores occurring simultaneously, you must configure your firewall to allow a range of ports.

For additional information, please refer to the article link : https://www.veritas.com/support/en_US/article.000031930

Scenario 4:

Backup Exec service account is changed but Backup Exec has not been configured to logon with the new account information.

To verify the account name that is listed, go to Start |Run services.msc and check the account name associated with the Backup Exec services. (Figure 1)

Figure 1

If the account name listed is different than the one listed in the Backup Exec Services Manager, perform the steps in the Solution Section.

Note: The Backup Exec Remote Agent for Windows Servers service should always be running as "Local System Account".

1. In Backup Exec, go to the Backup Exec Services Manager.
2. Click on the Services credentials tab.
3. Enter the new Backup Exec Service Account information in the Service Account Information window and then click OK.
4. On the message to restart Backup Exec Services, click OK.
5. Restart Backup Exec services using the Stop all services and Start all services options in the Backup Exec Services Manager.

Error Message