There may be other possible causes such as the LDAP bind account having insufficient privileges to read the member/memberOf properties on the user and group objects, but one potential issue is the scope defined on the group object in the directory.
To resolve, change the group scope from "Global" to "Universal". If the global catalog is used in the LDAP configuration then the group scope has to be "Universal".