Skip to main content

NAS registration refused

Thread needs solution

I am trying a backup on my nas. ATI recognises the nas but the registration with actual and correct username/password is not being accepted.

I have no idea what the reason could be.

I'm using Win 10 anniversary with latest updates.

 

0 Users found this helpful

I believe I have indentified the issue is that an incorrect path to the NAS deivce is the issue.  Take note of the NAS deivce name as viewed in a Windows File Explorer screen. Write it down if you have to as yo will need it.

Now, open True Image and create your backup task.  When you select destnation by clicking on the NAS folder icon in the GUI look to the top of that screen at the path box displayed.  Verify that the path contains the same name for your NAS as appears in Windows File Explorer.  If not change the path to that name and add the desired folder name to the path as well

Example: NAS:\\NASname\sharefoldername

With that done look to the right of the path box and you will see a > carat symbol inside a small box.  Click on that symbol.  If the path is correct it should populate in the directory tree view below.  If it is not correct the path will not appear.  In this case replace the NASname with the IP address of your NAS and that should result in the path populating the tree view.  Once you have the path established select it, enter credentials if prompted and test.  It should athenticate and you can proceed with your backup.

You can review this Thread link for posts from others having this problem if you desire.

https://forum.acronis.com/forum/126528

Origando, do you have any mapped drives in Windows with a drive letter going to the NAS as well?  If so, please check this thread:

https://forum.acronis.com/forum/126528?page=2#comment-395544

 

I solved the issue!

As proposed by Bobbo_3C0X1 I opened the NAS by using the address box on top of the ATI window and entered not the name of the NAS but: (\\192.168.xxx.xx). Now the registration screen opened and username/password were accepted.

Thanks to all for your support.

Glad to hear it!  Seems like a bug for now that should hopefully be addressed in the next update (no idea when that will be).  At least we have a few work-a-round options for now.