Novell eDirectory 8.8 Troubleshooting Guide - NetIQ
Novell eDirectory 8.8 Troubleshooting Guide - NetIQ
Novell eDirectory 8.8 Troubleshooting Guide - NetIQ
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
23.7.3 On Windows<br />
1 Go to the novell\nds directory and rename or move the following SecretStore modules:<br />
lsss.dll<br />
sss.dlm<br />
ssncp.dlm<br />
ssldp.dlm<br />
2 Restart the server.<br />
novdocx (en) 22 June 2009<br />
23.8 Viewing SLP Man Pages<br />
To view the man pages for SLP, you need to set the paths for the man pages. For example, on AIX,<br />
you must set the manpath to /usr/share/man instead of /opt/novell/man.<br />
23.9 dsbk Configuration File Location<br />
The dsbk.conf file is located in /etc instead of the location relative to the specific instance of<br />
<strong>eDirectory</strong>.<br />
23.10 SLP Interoperability Issues on OES Linux<br />
OpenSLP implements SLPv2, but <strong>Novell</strong> SLP (NDSslp) on UNIX* and Windows* platforms<br />
implements SLPv1.<br />
SLPv1 UAs do not receive replies from SLPv2 SAs, and SLPv2 UAs do not receive replies from<br />
SLPv1 SAs. That is, the clients with OpenSLP cannot see trees with NDSslp. Similarly, the clients<br />
with NDSslp cannot see trees with OpenSLP. For SLPv1 and SLPv2 to interact, you need to<br />
configure a DA that is running SLPv2.OES Linux ships with OpenSLP. However, <strong>eDirectory</strong><br />
installed other UNIX platforms, such as Solaris and Red Hat Linux, might use NDSslp, which is<br />
shipped with <strong>eDirectory</strong>. Because of interoperability issues with the two versions of SLP, a tree<br />
advertised via OpenSLP multicast might not be visible to NDSslp and vice versa. To overcome this<br />
problem, you need to configure a DA that runs OpenSLP.<br />
23.11 ldif2dib Fails to Open the Error Log File<br />
When the DIB Directory Exists In the Custom<br />
Path<br />
ldif2dib fails to open the default log file, ldif2dib.log when the dib directory is relocated to a<br />
custom location.<br />
To work around this issue, explicitly provide the log file location by using the -b switch.<br />
23.12 ndsconfig Does Not Verify an Invalid<br />
Configuration File Path<br />
To create the necessary configuration file, ndsconfig requires the full path and the configuration<br />
filename. When the same path name is passed for both the configuration file and the instance<br />
directory, ndsconfig cannot create the configuration file and aborts the operation.<br />
Miscellaneous 113
Change language