In the course of helping customers migrate to Centrify Adbindproxy, Support has identified some instances where the scale of Samba environments impact the effectiveness of the new adbindproxy component. This blog will summarize a recent issue and workaround which may help other customers facing a similar situation.
Centrify supports another way of implementing stock Samba4 with Centrify that does not use adbindd, but uses NSS instead. Access control is then based on NSS users and groups with winbind instead of using adbindd (Active Directory).
In one customer's environment, they were using Samba to share directories to a large number of end users whom were moving and accessing lots of large media files to and from those shares.