Unable to mount SMB share

[jarrodCoombes]

Pretty much as the title says, I am not able to mount the share, which is a local SMB share. I am absolutely sure I am using the correct password, though it is very unclear what username it is using (I assume the same one specified in Jamf?). I can mount the share manually with the username specified in the Jamf settings and the same password I am trying to usin with Jamf Sync.

24/12/02 09:06:02-ERROR: Failed to load the JAMF Distribution Point (<server>) (JSS) distribution point: mountingFailed

Is there a way to get a more verbose log output to work out what is going in here?

[nfawad227]

I'm experiencing the same issue can't mount the share drive

[BIG-RAT]

Version of Jamf Sync being used?
The account used is the Read/Write account for the file share distribution point (File Sharing tab).
Any other SMB shares mounted when you launch Jamf Sync?

[jarrodCoombes]

Hi @BIG-RAT I am using the latest version, 1.4.0, but it was an issue on previous versions as well. Yes, the account in question is the Read/Write account specified in the Jamf settings (it's also specified as the read only account if that makes a difference), and no, I have no other SMB shared mounted when I launch Jamf Sync.

No idea if this makes any difference, but the password in question has some special characters in it, one of which is &, but the issue persists even if I put the password in quotes.

[BIG-RAT]

I've not encountered any issues having & in the password. Have you tried clearing out the keychain entry for that share (search for JamfSync). Throw in a reboot as well to get a clean start.

[jarrodCoombes]

Keychain has been cleaned, several times. I don't save the password while trying to get this work now. The problem seems to exist on multiple machines, but persists across reboots.

Is there a way to get a verbose log on this? The error thrown by the app is not very helpful.

[BIG-RAT]

log stream is available. See if the following helps:
log stream --debug --predicate 'subsystem == "com.jamf.jamfsync"'

Also, verify the following in Privacy & Security -> Files & Folders

[jarrodCoombes]

The only thing that come out of the log stream is the exact same error I see in the app, which is way to generic to be of any help (Failed to load the JAMF Distribution Point (<SMB_SERVER>) (JSS) distribution point: mountingFailed) Is there a related log I can monitor to see what the actual issue is? Or at the very least see what exactly it is trying to mount with what credentials?

With regards to the security, I do not see JamfSync in that list at all, but there does not appear to be a way to add it. So how do I make sure it has access to network volumes?

EDIT: I created a PPPC profile that allows Jamf Sync Access to Network Volumes and scoped it to the machine in question. It still does not show up in the settings, but I can see that the profile is installed. The issue persists though.

[BIG-RAT]

I'd remove the config profile.
Run the following:
sudo tccutil reset All com.jamf.jamfsync
Next time you launch Jamf Sync and select a network share you should get the prompt to allow access to files on a network volume.

[jarrodCoombes]

So I fixed it. The problem was the setting in Jamf, specifically the "Share name" was wrong, it had a \ in it. I removed it on a whim, and the issue was resolved.

I would highly recommend adding some sort of debug, verbose logging for share mounting. If I had been able to see exactly what Jamf Sync was trying to mount, I'd probably have been able to fix this months ago. Simply throwing a mountFailed is really not helpful at all.

[BIG-RAT]

debug logging - noted.
Glad you got it figured out.

[ajrich77]

I am having the mounting failed error with two different accounts and both passwords are correct. Version is 1.4.0. When I test the credentials they succeed and the password is saved in keychain but the prompt still occurs each time I attempt to synchronize to Jamf server; JamfSync sees the files in the destination but fails to mount: