Don't just click that tempting fat Services button at the top of the screen and click the On/Off button for CIFS. But whether you got the "Success" message or not, you haven't succeeded-Samba, which handles Active Directory joining, won't be started unless you've enabled CIFS. The notice just goes away, and you may or may not get a little "Success" message in green fading in and out of the top of your screen. Once you click "OK" here, you might assume you're joined to the domain. By that point, I was just plain paranoid. I don't think the username Administrator really needed to be capitalized as shown here, but honestly I'm not sure. Another nasty thing about this dialog is that-in testing, at least-joining the directory absolutely would not work unless the Domain name, NetBIOS name, and Workgroup name were in ALL CAPS as shown above. The "NetBIOS name" is actually the name you want your FreeNAS box to use on the domain-the little tooltip on its right will tell you, if you hover over it-but it would really have been nice to have had that information visible to begin with. It's the short-form non-FQDN domain name, and it needs to be entered correctly (and in all caps), or you're going to be out of luck. First of all, the "Workgroup Name" actually IS important here. I hope you like tooltips, because some pretty essential information is buried in those little "i" buttons next to each of the text boxes. you have to find the "Services" element on the left bar, expand it, and then find "Directory Services" under that.Įnlarge / This is the first step on your journey of pain. The first step is to find "Active Directory" under "Services." Unfortunately, that alluring big "Services" icon on the top bar is not going to take you to the right place. despite the fact that I have nearly 20 years of BSD and Samba experience, 13+ years of Active Directory experience, and this was my fifth or sixth time in the last year and a half doing a FreeNAS AD join. Remember how joining in NAS4Free took five minutes? Well, this FreeNAS setup took closer to an hour and a half. It felt like a band of evil gnomes was hiding essential controls from me, secreting them in weird places, offering me identically named control elements that weren't actually what I wanted. Like many other things, the Active Directory support works, but getting it working is such an exercise-even when following documentation-in frustration. To put it kindly, this is the beginning of my frustration with FreeNAS. If you haven't already, of course, don't forget to go to Services|CIFS/SMB and check "Enable." If you don't, your Windows machines won't see your NAS on the network even though it's joined to the domain. Trying anonymous access." message even on a successfully bound domain, which could potentially throw troubleshooters down a rabbit hole when they can't figure out what they've done wrong (like using test.tld instead of in the Domain Controller text box). The other minor nitpick is that the MS Domain Info page gave me the harmless "Environment LOGNAME is not defined. (I tripped up on that one on my first attempt.) First, the "Domain controller name" text box on the Access|Active Directory dialog says "AD or PDC name," which initially sounds reasonable-on my test domain, "test.tld" and "" both resolve to the same IP address-but in fact, the join will only work if you specify the actual DC machine's FQDN. I could only find two minor nitpicky things to complain about here. Enlarge / No jimmies were rustled during this process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |