Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

jpipitone

macrumors newbie
Original poster
Feb 8, 2004
23
0
We've recently upgraded to Yosemite, and now several of our enterprise SMB and AFP shares we cannot connect to using the FQDNs or just the host names. Our enterprise consists of Windows AD servers, and our Macs have been configured to bind to the domain. All Mac users are logging in with their domain accounts. The share connectivity issues ONLY occur when using a domain account.

We have taken the following steps to troubleshoot:

What works
  • Connect to SMB or AFP share via IP address
  • Manually connecting to share with the cli using mount_smbfs with the following command:
    • mount_smbfs //'domain;administrator'@servername/shared /Volumes/mntpnt
  • kdestroy -a before connecting to SMB or AFP share
    • This destroys the Kerberos ticket and allows us to connect with the FQDN or hostname
What doesn't work
  • Connecting via FQDN or server name from the Finder
  • Manually connecting to share with the cli using mount_afp with the following command:
    • sudo mount_afp -i afp://hostname /Volumes/mntpnt
Error: mount_afp: AFPMountURL returned error 22, errno is 3

We've tried creating an nsmb.conf inside /etc, forcing smb1 and smb2, however this does not resolve the issue:

[default]
smb_neg=smb1_only
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.