alsmk2
Hot Shot
Hot Shot

Unable to mount file share in App Volumes 3

Jump to solution

I am having difficulties setting up a file share within AV3. Here's the log output:

[2016-04-05 10:17:49 UTC] P3573R2063 INFO Started POST "/xms/file_shares" for 127.0.0.1 at 2016-04-05 10:17:49 +0000

[2016-04-05 10:17:49 UTC] P3573R2063 INFO Processing by Xms::FileSharesController#create as JSON

[2016-04-05 10:17:49 UTC] P3573R2063 INFO Parameters: {"data"=>{"id"=>"1459851469533", "name"=>"App Stacks", "virtual"=>"true", "physical"=>"false", "policies"=>"false", "auto_import"=>"true", "type"=>"FileShare", "status"=>"pending", "status_message"=>"", "path"=>"\\\\server.domain.com\\AppStacks", "local_path"=>"", "hypervisor_ids"=>{"0"=>"2"}, "last_sync"=>"2016-04-05T10:17:49.533Z"}}

[2016-04-05 10:17:49 UTC] P3573R2063 INFO Creating directory: "/mnt/wem/__server_domain_com_AppStacks"

[2016-04-05 10:17:49 UTC] P3573R2063 ERROR Unable to mount file share because of permission: error 32, File share must be in the given domains.

[2016-04-05 10:17:49 UTC] P3573R2063 ERROR Unable to create file share "//server.domain.com/AppStacks"

[2016-04-05 10:17:49 UTC] P3573R2063 INFO Completed 400 Bad Request in 41.8ms (Views: 0.2ms | ActiveRecord: 1.0ms)

Just for clarification, the file share does exist in the same domain and has full access on the share and NTFS for everyone. I am also aware of the other answered discussion that suggests this is down to the bind account format; however, that is also entered correctly.

Would anybody have any ideas what this could be caused by?

Tags (2)
1 Solution

Accepted Solutions
Lakshman
Champion
Champion

Can you please check whether the Domain Bind username has any non-ASCII characters or not?

View solution in original post

4 Replies
Lakshman
Champion
Champion

Can you please check whether the Domain Bind username has any non-ASCII characters or not?

View solution in original post

alsmk2
Hot Shot
Hot Shot

That was in the right direction - it was caused by the domain user bind password containing special characters.

Resetting it to a basic alphanumeric password allowed me to add the share.

0 Kudos
chavesHFC
Contributor
Contributor

I am getting the same error trying to mount a fileshare.  I have verified that the bind account format is just the username, the username does not contain non-ascii characters and the password does not contain any special characters.  From the appliance, I verified I could mount the cifs share using the bind account credentials.  How can I see what credentials are being passed from the AV site?

0 Kudos
massmans
Contributor
Contributor

I solved this issue by switching the AD domain join from domain\username to just username. 

0 Kudos