AD compatibility issue with samba 4

[gcooper]

A debug session on #freenas with an 8.0.3-RC2 user revealed that samba 4 puts the unique 'netbios' identifier in the 'cn' attribute, not the 'nETBIOSName' attribute. Some research via Google colludes with this initial observation. More work will need to be done to properly handle the case described in the blog post [1] and the Oracle forum post [2] (in particular, the LDAP query needs to be modified to use netbiosname='*', or use the super secret sauce method described in the last post in the Oracle forums, if it's indeed valid). So ultimately, the documentation on the Microsoft TechNet? post [4] noted isn't 100% compatible (using the 'nETBIOSName' attribute), and might just work by accident with our middleware today.

Unfortunately I don't have details about the PDC version in use. Whether or not this is a bug in samba 4 triggered by the 3.5.11 -> 3.6.1 upgrade is another good question.

1. ​http://geekswithblogs.net/Tariq/archive/2009/07/30/133813.aspx
2. ​https://forums.oracle.com/forums/thread.jspa?messageID=4694865
3. ​http://serverfault.com/questions/234041/can-an-ldap-query-on-ad-provide-the-netbios-domain-name-for-a-single-account-whe
4. ​http://msdn.microsoft.com/en-us/library/windows/desktop/ms678700%28v=vs.85%29.aspx

[gcooper]

Samba 4 debug log (look for ': domains = ')

[jhixson]

Samba 4 is not supported.