[Samba] 3.0.14 to 3.0.23c Invalid SID

[Larry McElderry]

Trying to upgrade from 3.0.14a to 3.0.23c.  So far, things seem to be working, but the following entries appear in the smbd error
log.  The test machine is a domain client (server is still 3.0.14).  The sids listed are exactly as they appear in the ldap tables.
What makes them invalid?  Anyone know.

[2006/10/19 11:34:10, 1] passdb/pdb_interface.c:pdb_default_uid_to_rid(1227)
  Could not peek rid out of sid S-1-5-21-1471758060-416947062-312552118-500
[2006/10/19 11:34:14, 0] passdb/passdb.c:lookup_global_sam_name(598)
  User nobody with invalid SID S-1-5-21-1471758060-416947062-312552118-2998 in p
assdb
[2006/10/19 11:46:01, 0] lib/util_sock.c:get_peer_addr(1229)
  getpeername failed. Error was Transport endpoint is not connected
[2006/10/19 11:46:01, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 172.21.2.2. Error Connection re
set by peer
[2006/10/19 11:46:01, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2006/10/19 11:46:02, 0] passdb/passdb.c:lookup_global_sam_name(598)
  User larry with invalid SID S-1-5-21-1471758060-416947062-312552118-1003 in pa
ssdb
[2006/10/19 11:46:04, 0] passdb/passdb.c:lookup_global_sam_name(598)
  User nobody with invalid SID S-1-5-21-1471758060-416947062-312552118-2998 in p
assdb
[2006/10/19 11:46:04, 0] passdb/passdb.c:lookup_global_sam_name(598)
  User larry with invalid SID S-1-5-21-1471758060-416947062-312552118-1003 in pa
ssdb