What is the hash list that is referenced in the afptcp.log? Here is what it looks like:

Feb 10 10:15:56 d208 afptcpd[7382]: [debug] Ldap user name: cn=James***,ou=TECH,ou=CENTRAL,o=***
Feb 10 10:15:57 d208 afptcpd[7382]: [debug] UID: 600
Feb 10 10:16:00 d208 afptcpd[7382]: [error] Map GUID to DN returns -765
Feb 10 10:16:00 d208 afptcpd[7382]: UTF8 Name
Feb 10 10:16:00 d208 afptcpd[7382]: [error] Unable to open parent (ZID #127 <7f>) 20407 <4fb7> child is <mach_kernel>
Feb 10 10:16:00 d208 afptcpd[7382]: [error] FPGetFileDirParms: GetInfo call is failed with err 20407
Feb 10 10:16:00 d208 afptcpd[7382]: UTF8 Name
Feb 10 10:16:00 d208 afptcpd[7382]: [error] Unable to open parent (ZID #127 <7f>) 20407 <4fb7> child is <DCIM>

(...Lots more of this)

Feb 10 10:16:00 d208 afptcpd[7382]: [debug] entry 130 already exists in the hash table Feb 10 10:16:00 d208 afptcpd[7382]: [error] Failed to resolve user name .Help_Desk_Specialist.ou=ADMIN_SVCS.ou=CENTRAL.o=* ** NWDSResolveName error: -601 - fffffda7
Feb 10 10:16:00 d208 afptcpd[7382]: [error] Failed to resolve user name .Help_Desk_Specialist.ou=BUSINESS.ou=CENTRAL.o=*** NWDSResolveName error: -601 - fffffda7

(...Lots more of this)

Feb 10 10:16:01 d208 afptcpd[7382]: [error] Unable to convert trustee GUID -1 <ffffffff>

That is NOT an attempted login. Dozens of these kinds of -601 errors follow for users not trying to login. Apparently they are somehow stuck in this "hash table"? The logs for a single login attempt will return over 13000 lines of these -601 errors coming from this hash table.

Any ideas what is going on here?