Project

General

Profile

Bug #70950

Active Directory Fails to show Mounts After an Update from 11.2 Beta to 11.2 Stable

Added by Shane Holloman 7 months ago. Updated 5 months ago.

Status:
Closed
Priority:
No priority
Assignee:
Release Council
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Not Applicable
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Our office has been using 11.2 Beta successfully for AD home folders for Windows users. Very nice

After updating to 11.2 Stable today - re-authenticating the Domain account name and Pass under http://tank/ui/directoryservice/activedirectory and ensuring the enable is still checked -

We can see a "homes" location: /mnt/primary/homes with "Use as home share" enabled. However, the Windows user can not connect to their personal share while logged in on a domain-bound PC with their domain name and user.

History

#1 Updated by Shane Holloman 7 months ago

  • Seen in changed from 11.3 to TrueNAS 11.2-U3

#2 Updated by Dru Lavigne 7 months ago

  • Private changed from No to Yes
  • Seen in changed from TrueNAS 11.2-U3 to 11.2-RELEASE
  • Reason for Blocked set to Need additional information from Author

Shane: please have a client try to connect. Then on the FreeNAS system, create a debug (System -> Advanced -> Save debug) and attach the resulting file to this ticket.

#3 Updated by Dru Lavigne 7 months ago

  • Status changed from Unscreened to Closed
  • Target version changed from Backlog to N/A
  • Private changed from Yes to No

#4 Updated by Conny Molin 6 months ago

I have the exact same error on my system. The only difference is that I went from 11.2 stable to 11.2 u2 stable today and access to homes got affected.
Other shares on the freenas system are working normally (and yes, they are shares with AD permissions as well).

Would you need me to write up a separate bug report or can you take it from this one as they are basically identical?

#5 Updated by Dru Lavigne 6 months ago

Go ahead and create another one that contains your debug as it is most likely related to the bump in the Samba version for U2.

#6 Updated by Conny Molin 6 months ago

  • File debug-freenas01-20190219195104.tgz added

I suspect so too. Want me to tar and attach the /var/log/samba4 folder as well?

EDIT: Sorry, misread your comment. I'll arrange a new bug report.

#7 Updated by Dru Lavigne 6 months ago

  • File deleted (debug-freenas01-20190219195104.tgz)

#8 Updated by Mike Gomon 5 months ago

I usually go by the mentality of "if it isn't broke, don't fix it" - But I wanted to grab the most current updates. Then this... fun times. Any ETA on when this issue will be addressed? It looks long past due for a fix.

#9 Updated by Mike Gomon 5 months ago

face palm @ microsoft! I literally logged out and back in on each machine that was actively connected to an SMB share and everything looks fine.

#10 Updated by Dru Lavigne 5 months ago

  • Reason for Closing set to Not Applicable
  • Reason for Blocked deleted (Need additional information from Author)

Also available in: Atom PDF