/LDAPv3/192.168.0.2 couldn't be opened because of an unexpected error-14002

Question

/LDAPv3/192.168.0.2 couldn't be opened because of an unexpected error-14002

We have 2 xserves both running 10.4.8. One xserve does dns, dhcp, mail and authentication. The other xserve just hosts the user data files. This setup has been working for about a month and today the data xserve gets an error in workgroup manager when trying to connect to the xserve that authenticates. I get the following error when I select the path in workgroup manager to /LDAPv3/192.168.0.2 (the ip address of the authentication xserve).

Unable to open the requested node. The node /LDAPv3/192.168.0.2 couldn't be opened because of an unexpected error of type -14002 occurred.

I have run disk repair and repaired permissions on all hard drives of both servers. I have copied the contents of the console below with the error messages. If someone could please help, I would greatly appreciate it.

dsOpenDirNode failed with error of type -14002
2007-01-17 14:00:48.387 Workgroup Manager[692] Got unexpected error of type eDSOpenNodeFailed (-14002) on line 3809 of /SourceCache/ServerManagerApp/ServerManagerApp-230.2.51/PMMUGMainView.mm
dsOpenDirNode failed with error of type -14002
2007-01-17 14:01:05.854 Workgroup Manager[692] Got unexpected error of type eDSOpenNodeFailed (-14002) on line 3809 of /SourceCache/ServerManagerApp/ServerManagerApp-230.2.51/PMMUGMainView.mm
dsOpenDirNode failed with error of type -14008
dsOpenDirNode failed with error of type -14002
2007-01-17 14:02:12.668 Workgroup Manager[692] Got unexpected error of type eDSOpenNodeFailed (-14002) on line 3809 of /SourceCache/ServerManagerApp/ServerManagerApp-230.2.51/PMMUGMainView.mm
2007-01-17 14:05:27.038 Workgroup Manager[692] dsTickler failed: dsVerifyDirRefNum( 29360129 ) returned eDSCannotAccessSession (-14006)
Jan 17 14:07:43 dataxserve servermgrd: servermgr_dns: no name available via DNS for 192.168.0.3
Jan 17 14:07:43 dataxserve servermgrd: servermgr_dns: no hostname set and unable to detect via DNS, services may not function properly - use changeip to repair
2007-01-17 14:09:27.048 Workgroup Manager[692] dsTickler failed: dsVerifyDirRefNum( 29360129 ) returned eDSRefTableEntryNilError (-14084)
Jan 17 14:13:06 dataxserve ntpd[206]: sendto(17.254.0.27): Bad file descriptor
2007-01-17 14:13:27.059 Workgroup Manager[692] dsTickler failed: dsVerifyDirRefNum( 29360129 ) returned eDSRefTableEntryNilError (-14084)
2007-01-17 14:17:27.069 Workgroup Manager[692] dsTickler failed: dsVerifyDirRefNum( 29360129 ) returned eDSRefTableEntryNilError (-14084)
2007-01-17 14:21:27.079 Workgroup Manager[692] dsTickler failed: dsVerifyDirRefNum( 29360129 ) returned eDSRefTableEntryNilError (-14084)
Jan 17 14:22:43 dataxserve DirectoryService[60]: DSLDAPv3PlugIn: Required Policies not Supported: No ClearText. LDAP Connection for Node 192.168.0.2 denied.
Jan 17 14:22:43 dataxserve DirectoryService[60]: DSLDAPv3PlugIn: Policy Violation. Disabled future attempts to bind to [192.168.0.2] for 1 hour.
Jan 17 14:22:44 dataxserve DirectoryService[60]: DSLDAPv3PlugIn: Required Policies not Supported: No ClearText. LDAP Connection for Node xserve denied.
Jan 17 14:22:44 dataxserve DirectoryService[60]: DSLDAPv3PlugIn: Policy Violation. Disabled future attempts to bind to [192.168.0.2] for 1 hour.
2007-01-17 14:25:27.090 Workgroup Manager[692] dsTickler failed: dsVerifyDirRefNum( 29360129 ) returned eDSRefTableEntryNilError (-14084)

Xserve g5 dual 2ghz 2GB RAM 150GB HD, Mac OS X (10.4.8)

Posted on Jan 17, 2007 12:33 PM

Reply

Answer 1

Jan 17, 2007 2:33 PM in response to West Harrison

I had the exact same problem 2 days ago with a new Intel Xserve running as OD master, and a 2nd G5 Xserve connected to the LDAP for AFP authentication. I can't say that this is a solution, but I did a few things, and somehow it began working again. Just to clarify, normally I can view users in WGM while connecting to either server. From the AFP server, the WGM working directory has been "/LDAPv3/( my odmaster xserve hostname)" When the problem started, I would get the error -14002 when trying to view that LDAP directory from the AFP server. However, I could view it just fine locally from the OD Master server. Here is what I did to fix it. First I demoted the afp server to "standalone" and using Directory Access on the AFP server I also removed the LDAP server listed (OD Master should be listed here). Then I restarted the AFP server. Now I re-added the LDAP server in Directory Access on the AFP server. In this step, you do not have to "bind" the 2nd server to the OD master, just add the correct hostname for your OD Master, and select Open Directory from the pull down list. Then I re-promoted the AFP server to be a member of a Directory System, and rebooted one more time. Then it was working again.

Reply