Doing a "save configuration" from the e-smith console interface will regenerate the LDAP database, which should hopefully fix this.
A warning though - doing this also clears out the DHCP leases, so if the e-smith server is providing DHCP services on your local network you'll need to release all your DHCP leases before saving the configuration, then renew them afterward. (This is being improved in e-smith 4.0.)
Best regards,
- Joe