Could not mount distribution point

Can anyone tell me if this issue is persistent and repeatable, or if it's random? I am seeing this happen but it's at random. Every couple days I'll get a JSS error that somebody tried to install a piece of software from self service and it failed because "could not mount distribution point", while most people aren't having any issues.

If I were having the issue as described above, would it be affecting everybody consistently? We're on 9.91.

I'm curious if what we're using now - IP address for the DP's, would cause this to happen as well since we currently populate the "Workgroup or Domain" field in 9.82.
We will upgrade to 9.9x in the near future, so I want to be sure that we don't panic if this shows up.

We changed to IP a while back as we had the issue that @znilsson posted above.

I just spent the last 3 days on and off trying to figure this out. With the share being able to be mounted I was convinced I was going crazy or needed to witchdoctor and a chicken to resolve this.

Yeah, i'm punchy as I have been working on this a while.

Thanks justincredible, this cured problem i had with linux 9.96 connecting to windows DFS/SMB share.

This worked perfectly for me. Was on 9.82. Upgraded to 9.96 today and Casper Admin/clients were unable to mount the SMB CasperShare. In 9.82 I had the domain entered in the Workgroup field. By emptying that field, everything is now working as normal.

Posted: 6/30/16 at 12:41 PM by justincredible From my JAMF Buddy: "There was an issue starting with version 9.9 where having a workgroup entered for the file share settings could cause issues if the file share server belongs to that same workgroup. Can we try going to the File Share Distribution Point settings in the JSS and clear out what's entered for the Workgroup field." This worked for me. Posted: 7/18/16 at 4:47 PM by donmontalvo Ran into the same problem, glad I found this thread, workaround fixed it. https://jamfnation.jamfsoftware.com/discussion.html?id=20550 Server Name of server.domain.com and Workgroup of domain.com prevents SMB (Samba) shares from mounting. Clearing out Workgroup field fixes the issue. PS, It would be great to have a Known Issues wiki, else this workaround might come back to bite is if and when the issue is resolved...I'd hate to run into more issues by having the Workgroup field cleared out. Thanks, Don

Thanks Justin,

We just upgraded from 9.81 to 9.96 yesterday and had the same issue of not being able to SMB mount the DP using Casper Admin, Self Service ...

The domain name was in there as a FQDN. I tried NO domain and the short Domain Name and both solved the problem. This was when used on OS X 10.12 and 10.11 machines. Have contacted JAMF support with that info

Regards,

David

It seems that this issue is still persistent in Jamf 10.0.0

I followed the instructions from @bmccune's buddy, and immediately fixed this issue with my 10.6 JSS. Thanks for posting!

Hi Just to share my case :
Same trouble after upgrading JSS from JAMF 10.0.0/ Sierra to 10.9/Mojave
I couldn't launch Casper Admin because casper share folder.
So creating share folder on a distinct server (NAS) with the 2 jamf users (r and rw ) solved my problem
It seems to be a strict condition : jss must not host share folder (even if it worked in the previous versions ; 10.0. was ok)
Using smb protocol
Hope my feedback could help some of us
Cheers
Joel