Skip to main content

No access to network backup storage (Samba SMB)

Thread needs solution

Hello,

 

We're not able to access Samba SMB shares via Acronis from Windows Server 2012R2 and therefore, we cannot run any backup or restore jobs. Since the WannaCry/SambaCry ransomware our backup provider added "nt pipe support = no" to the Samba configuration. Since then, Acronis is not able to access the SMB shares. Acronis claims the user name/password is wrong for the SMB share but the data is correct. The SMB share can be accessed without problems using Windows Explorer or other backup tools (Backup Exec).

We tried it with Acronis Backup 11.7, 12.0 and 12.5

 

Have others also this problem? Is there a way to solve the issue?

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello Thomas,

Thank you for your posting! Have you tried to specify the IP address instead of DNS name? Does this help to solve the issue? 

Alternatively, you may want to update the vulnerable samba module according to the article below and then re-enable "nt pipe support" parameter: 
https://www.tecmint.com/fix-sambacry-vulnerability-cve-2017-7494-in-linux/ 

Hello Ekaterina,

 

Thanks for you feedback. When using the IP address we have the same problem. The backup storage will be provided by the provider OVH, so we cannot change hat on our own and it seems there are no plans to re-enable the paramater at the moment, so we have to find a solution as otherwise we have to switch to another backup solution.

 

Are there any options/parameters that can be set in Acronis for SMB connections (config files, Registry) that we can try?

We are using OVH as well, and this is causing massive problems for us.   We need to backup to \\myShare\backup, but Acronis is requesting access to the root of the share (e.g. \\myShare\ before trying the entire path).  No credentials are needed to \\myShare\backup, but we do not have the \\myShare credentials)

There must be something we can do to change this behavior?  The product is unusable in it's current state.