Fileshare Path Status: Troubleshooting 'Not Connected' Error with Backup Server's Proxy

Troubleshooting File Share Connectivity Issues

KB ID: 241011

Issue:

Fileshare path status is displayed as "Not connected" when attempting to use the backup server's default proxy. 

Possible Cause and Solutions

1. Invalid UNC Path or Incorrect Password

Cause: The UNC path or password may be incorrect.
Solution:
  1. Verify the UNC path is correct.
  2. Ensure the password entered matches the required credentials.

2. File Share Already Mapped

Cause: The file share may already be mapped to the same proxy.
Solution:
  1. Check for duplicate mappings to the same share.
  2. Remove any redundant mappings.

3. Multiple Connections to Server

Cause: Multiple connections to the server or shared resource by the same user.
Solution:
Restart Workstation Service:
  1. Open Command Prompt as Administrator:
    1. Select the Start button, type CMD, right-click "Command Prompt," and select "Run as Administrator".
  2. Run the following commands:
net stop workstation /y and press Enter.
net start workstation and press Enter.
Delete Unwanted Drives:
  1. In Command Prompt, type net use and press Enter to list drives.
  2. Identify and remove questionable drives using:
net use /delete \\servername\foldername

4. No Internet Connectivity on Target Proxy Agent (Azure Share)

Cause: Internet connectivity may be required to access Azure resources.
Solution: Confirm that the target proxy agent has active internet access.

5. Insufficient Permissions on Share

Cause: User may lack the necessary permissions to access the share.
Solution:
Access Share Permissions:
  1. Log in to the server hosting the shared folder.
  2. Right-click on the folder, select "Properties," then navigate to the "Sharing" tab.
Check and Adjust Permissions:
  1. Click "Share" or "Advanced Sharing" and review the list of users with access.
  2. If needed, click "Add" or "Edit" to adjust permissions (e.g., Read, Read/Write, Full Control).
  3. Apply changes and click "OK."

6. BDR Delegation Service Not Running

Cause: The BDR delegation service may not be active on the selected proxy.
Solution: Confirm that the BDR delegation service is running.
NotesNote: After adding the file share to the server, it may take 10 to 30 seconds to synchronize. During this time, the message "file share not connected" may appear. Once mapped to the proxy, it will be in an idle state. Any errors will be displayed in the menu notification.
If the issue persists after following these steps, please contact BDRSuite Support for further assistance.

    • Related Articles

    • Troubleshooting Network Path Connection Issues to Target Host

      KB ID: 117037 Issue: Encountering difficulties when trying to establish a network path connection to the target host with BDRSuite Cause: This problem occurs when the BDRSuite Backup Server or BDRSuite Backup Client cannot access the admin$ share ...

    • Troubleshooting Database/Instance Connection Issues

      KB ID: 231001 Summary: Error code 231001 indicates a connection issue between the Database/Instance and the backup server. This critical error message reads, "Unable to establish the connection between the Database/Instance and the backup server." ...

    • Quick Start Guide for NAS/File Share Backup

      About NAS/File Share Backup & Recovery BDRSuite provides a comprehensive solution for protecting NAS/File shares. BDRSuite ensures secure storage of NAS backup data in the BDRSuite repository across local, remote, and cloud destinations with ...

    • NAS / File Share Backup

      BDRSuite's NAS / File Share Backup solution offers reliable protection for your file shares across NAS devices, ensuring secure backup of your critical files and folders. Whether it's NFS or CIFS/SMB shares, BDRSuite ensures that your data is safely ...

    • Troubleshooting Restore Failures Due to VM Configuration File Unzipping Issues in VMware Environment

      KB ID: 105027 Issue Description Users may encounter restore failures during Full VM Recovery or Instant Boot Recovery in a VMware environment. One possible reason for these failures is issues with unzipping the VM configuration file stored in the ...