Backups fail with an "Error E7D10041: Unable to establish a network connection to \\\. Error EBAB03F1: No network provider accepted the given network path."
Error E7D10041: Unable to establish a network connection to \\\. Error EBAB03F1: No network provider accepted the given network path.
On occasions, backup jobs may fail when using Symantec System Recovery (SSR) or Backup Exec System Recovery (BESR). The error "EBAB03F1: No network provider accepted the given network path." is typically due to DNS issues, network latency, timeouts, or the resource is no longer available.
To troubleshoot the error, perform the following steps:
1) Verify network connectivity by running PING <IP Address> to the Windows Share or remote storage device. Also attempt to ping by name to test name resolution. If ping by name fails then add the IP Address / Host Name in the HOSTS file of the local machine.
2) Run a backup to a locally attached device to rule out the server being backed up as the source of the problem.
3) Create a new Windows Share or folder and run a backup to the new location using \\<ip address>\<share name> instead of a drive mapping.
5) If backups are still failing, then the network is the most likely cause.
6) In addition, check for failing disks if NAS appliances are being used. Check the NAS's internal diagnostic tools (S.M.A.R.T. or similar) to see if any disks are reporting excessive errors.
7) As an additional troubleshooting step, Symantec has an agreement with Apparent Networks to provide a network utility called AppCritical. This utility will provide Symantec Technical Support additional information and possibly identify bottlenecks or other underlying issues in the network infrastructure.
The backup speed is limited by the speed of the physical connection. The rate at which the backup runs depends on the make/model of network cards, the mode/frame type configuration for the adapter, the connectivity equipment (hubs, switches, routers, and so on), and operating system settings. Backups to a local disk can usually backup at a higher rate of speed than backing up across a network.
A common reason for slow network backups can be networking configuration. Features such as "full-duplex" and "auto-detect" may not be fully supported in every environment. Manually set the speed to 100 Mb and the duplex to half/full for the server side. Find out which Ethernet port the server is connected to on the switch, and set the SWITCH PORT setting to 100 MB and half/full duplex. Do this for the backup server switch port, and any switch ports for machines being backed up.
When a hub is in place instead of a switch, full duplex may not be supported, see the Original Equipment Manufacturer for details on device features. Also, both the switch and the network card must have matching settings, for instance, if the switch port is set to 100 half, the NIC for the server should also be set to 100 half.
Another common cause could be the NIC driver. Update the network card drivers on the server and remote machine. Also make sure that the link speed/duplex values are set properly on all machines and that networking errors are not occurring in the Windows Event Viewer logs. Check the event logs for any other warnings, errors, or normal events that may take place when the backups run.
This utility can be obtained at the following site:
Information on how to run the AppCritical tests can be found here: