Skip to main content

Unable to connect to SMB://[IPV6]/share datashource from Acronis Backup 12.5

Thread needs solution
Posts: 3
Comments: 1

I try to connect to Samba share using IPV6 IP address but Acronis Backup reports error connecting to the share

smb://[IPV6 Ip address]/share


Failed to resolve the host name due to a network error.

The specified file does not exist.

Error code 0x00590051+0x00040011

Dec 10, 2018, 01:03 PMMore details


Connection to IPV4 shares looks ok. Which format we should use to specify SMB IPv6 addresses?


Thank you

0 Users found this helpful
Acronis Program Manager
Posts: 22
Comments: 3131


Hi Andrey,

Currently there is no pure IPv6 environments support in Acronis Backup 12.5, which means that some scenarios may work (like accessing web console), but some (like accessing network shares) may require IPv4 usage. This feature is planned for future versions with no ETA which we can provide at the moment (internal feature ID for reference: ABR-53979).

Thank you.

Posts: 3
Comments: 1


It's very sad :(

Half of the network which is ipv6 is not accessible from Acronis Backup...

Both IPV6 SMB and NFS can not be accessed from Acronis Backup agents, only IPV4.


Error code: 64
Module: 89
LineInfo: 0xCAA935157D7E70B5
Fields: {"IpAddress":"2001:000:000:1ffe:e0:ff2:0:101","$module":"nfs_supp_lxa64_11010"}
Message: The NFS server is not available.
Error code: 65521
Module: 0
LineInfo: 0xBD28FDBD64EDB911
Fields: {"$module":"nfs_supp_lxa64_11010","code":"11"}
Message: Resource temporarily unavailable


On the 'positive' side the same Linux box with Acronis Agent installed can mount both SMB and NFS IPV6 with no problem.

Sounds like IPV6 address format is causing some issue or confusion in Acronis Agent code and should be relatively easy to fix using different characters or adding logic to interpret both IPV4 and IPV6 formats (IPV6 not a new technology in 2019 anymore)