Net Folders not showing up for users (Connection Test Successful)

Customers have more then one Tree that may be used for LDAP.
Some users exist in both trees.
Rights to the Net Storage volume and directories are assigned correctly.
Testing the connection for the Net Storage folders, shows successful.

The following logs show similar errors:

FAMT log (Novell FAMT)
May  8 03:58:16 filr [XTCOM]: WARNING:ProcessPropFind_AllProp: Get Directory Effective Rights: \\10.1.2.25\data\users\jdoe\folder, failed status = 0xc7fa0003
May  8 03:58:16 filr [XTCOM]: WARNING:ProcessPropFind_AllProp:NCFsdBasicEnumDirectory failed status: 0xc7e70009
May  8 03:58:16 filr [XTCOM]: ERROR:FAMTOperations::ProceeRequest failed unc: \\10.1.2.25\data\users\jdoe\folder identity: cn=admin.o=novell session: URfOYZSoeyeIlGnT9BFeHg==
May  8 03:58:16 filr [XTCOM]: ERROR:NCPOperations::ProceeRequest failed unc: \\10.1.2.25\data\users\jdoe\folder identity: cn=admin.o=novell session: URfOYZSoeyeIlGnT9BFeHg==

SSF log (Novell Filr)
2013-05-08 01:40:42,205 ERROR [http-apr-8443-exec-9] [org.kablink.teaming.module.ldap.impl.LdapModuleImpl] - Error reading attributes from the volume object: /home/jdoe javax.naming.CannotProceedException; remaining name 'home/jdoe'
2013-05-08 01:40:42,297 ERROR [http-apr-8443-exec-9] [org.kablink.teaming.module.ldap.impl.LdapModuleImpl] - Error reading attributes from the volume object: /home/jdoe javax.naming.CannotProceedException; remaining name 'home/jdoe'
2013-05-08 01:40:42,298 ERROR [http-apr-8443-exec-9] [org.kablink.teaming.web.util.NetFolderHelper] - In NetFolderHelper.createHomeDirNetFolder(), invalid server information

Make sure the correct user is being sync'd into Filr so that it can look up and pull down the correct credentials to give the user access to the NetStorage folders.

Because more then one Tree was being used for LDAP sync, Filr is only able to have one user per tree in the system and is not able to sync both users.  When the Net Storage permissions were set up from the admin console, the wrong user was being used, and so Filr was looking up the wrong Tree for the user.