I'm trying to figure out what permissions the Agent requires for SMB targets. Situation is this; I have a folder restricted to a specific user only, with security rights inheritance disabled. I share the folder, to that specific user only and the share is 'hidden' ($). I can browse the folder without issue from the source worksation, read/write/delete all fine. Pop it into the Agent and...Access denied, and can't populate the destination.
This started happening when ver 3 was installed, this wasn't and issue with 1.7 and 2. So what changed? What permissions/creds is the Agent sending?!
-
- Enthusiast
- Posts: 39
- Liked: 8 times
- Joined: Jul 11, 2012 3:39 pm
- Full Name: James McGuinness
- Contact:
-
- Veteran
- Posts: 636
- Liked: 100 times
- Joined: Mar 23, 2018 4:43 pm
- Full Name: EJ
- Location: London
- Contact:
Re: Permissions for Agent
Are you sure this isn't something like the account used for Veeam being locked out on the domain controller?
Easy to check I suppose, you could try using credentials you know are valid, the specific user you mentioned.
Easy to check I suppose, you could try using credentials you know are valid, the specific user you mentioned.
-
- Enthusiast
- Posts: 39
- Liked: 8 times
- Joined: Jul 11, 2012 3:39 pm
- Full Name: James McGuinness
- Contact:
Re: Permissions for Agent
Yes I'm sure. As I said if I browse the exact path from the run line and test read/write/del it's all fine. I re-produce the problem with a different PC and user account as well.
-
- Product Manager
- Posts: 14726
- Liked: 1707 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Permissions for Agent
Hello James,
Nothing was changed in agent authentication logic. To double check: can you confirm that this specific account (the one that is set in the agent job settings) can login to the mentioned file share from the affected machine? Can you start recovery via agent from any restore point on your file share? Thank you in advance!
Nothing was changed in agent authentication logic. To double check: can you confirm that this specific account (the one that is set in the agent job settings) can login to the mentioned file share from the affected machine? Can you start recovery via agent from any restore point on your file share? Thank you in advance!
Who is online
Users browsing this forum: No registered users and 7 guests