Newbie with a base suffix searching problem

[Rahul Dave <rahul@reno.cis.upenn.edu>]

Hi,
I've been trying to set up OpenLDAP with ldap_nss on
my cluster. I use the migration(from NIS) scripts to populate
the database, and, issuing
ldapsearch -h sentinel -v -b "dc=eniac2000" 'objectclass=*'

will list all the entries

However, 
ldapsearch -h sentinel -v 'objectclass=*'

wont. What gives? I specified the base in defaultbase.ldap and in
ldap.conf. This is on a Redhat 5.0 machine, updated with all RedHat Patches.
(Intel)


Here's ldap.conf:
===
# Your LDAP server. Must be resolvable without using LDAP.
host sentinel

# The distinguished name of the search base.
base "dc=eniac2000"

# The LDAP version to use (defaults to 2)
ldap_version 2

# The distinguished name to bind to the server with.
# Optional: default is to bind anonymously.
binddn "cn=root,dc=eniac2000"

# The credentials to bind with.
# Optional: default is no credential.
bindpw my_password
.....(scope=one, etc , defaults)
===
The host sentinel presently resolves via NIS.

slapd.conf looks thus:
=======

include         /etc/ldap/slapd.at.conf
include         /etc/ldap/slapd.oc.conf
schemacheck     off
#referral       ldap://ldap.itd.umich.edu

#######################################################################
# ldbm database definitions
#######################################################################

database        ldbm
suffix          "dc=eniac2000"
directory       /var/ldap
rootdn          "cn=root,dc=eniac2000"
rootpw          my_password
index           cn,sn,uid                       pres,eq,approx
index           ipserviceport,iphostnumber      pres,eq

access to * attr=userpassword by self write by * compare

============

The consequence is that the name service switch lands up not working
(I think). I tried it by trying to grok groups in the nsswitch.conf
using LDAP, and I only got the gid's :-(

I should mention that this is a 2-ethernet-card host. The externally
accessible interface does not carry the LDAP, its the internal network
which does. The hostname of this machine is given by the external interface,
ie the network on which LDAP is supposedly not running.

I'd be grateful for any help.
Thanks,
Rahul
Eniac 2000 Project
(http://reno.cis.upenn.edu)