Access issues with Lacie

It sounds like a permissions issue - I expect what's happening is that when you use explorer to browse the NAS your workstation authenticates using your (domain) username and password. When Paragon tries to connect it does so using the credentials of the service account it's running under.  It works when you create a folder and kick off the backup because it ends up running with your credentials, rather than the service credentials.

Try creating an account in the domain which you'll use to run the backup software, and then change the service on each workstation to run using that account.  Give that account the appropriate access to the share on the NAS, and it ought to work.

Jon

I have tried to do what you said but it just isn't cooperating. When I specify the the username and pass for the scheduled backup, it gives a permissions error. The only way it passes is if you enter the credentials of the current user of the person logged in.

I have also tried to make a network drive with the user name that is set on Lacie device and Windows, then used it to the path of the backup folder and it still fails.

I logged into Lacie with FTP and noticed that the permissions on the folder read as follows.

Owner:   Read Y Group Y Execute Y
Group:    Read Y Group N  Execute Y
All Users:Read Y Group N  Execute Y

Thought the setup on Lacie I applied the public access to read/write permission.

Why does this not work then?
I cannot change the permissions either.

That's interesting, given the symptoms you were describing I'd thought it was an authentication problem at the workstation end.  It may (or may not for that matter) be a permissions problem at the NAS end.  It's often the case that the permissions shown via ftp don't match reality - and some implementations just lie.

Which specific LaCie box are you using?  (different LaCie boxes run different software, so to be able to make specific suggestions I need to know which it is).

Having asked that, the direction I'm thinking in is to create a (domain) backup user (I think you've already done this), create a folder on the NAS that is owned by this user (probably by logging in to a workstation as the backup user and creating it there), and then try logging in via ftp as that user to check you can write.  If that works, then I can't see a reason why paragon wouldn't be able to backup via ftp in the same way.

jon

I am using a Lacie-5big network 2 box. I am thinking of just building a workstation to use as a storage device then running a backup for that machine to the Lacie as an offsite backup. Unless I can get the permission issue dealt with.

I will give you points for the solution though this is not the way I am going to use the backup. I am setting up a PC on the domain for storage then backup to the LACIE for a secondary backup.