Novell 错误 81 连接
我们尝试从办公室连接到远程 Novell 服务器。
首先，我们必须打开防火墙端口才能连接到服务器，否则我们会收到错误 91（这基本上表明服务器无法加入）。
其次，我们使用名为 LDAP Browser 的工具来测试连接。
我们收到错误 81“无法联系 LDAP 服务器”。 但我们查看了通信痕迹，发现我们联系了服务器并得到了响应。 我们还使用 Telnet 进行了测试，发现可以连接到服务器。
那么，有人知道这个错误意味着什么以及可能的解决方案是什么？ 因为，我用谷歌搜索了这个错误，但没有得到有效的答案来告诉我要检查什么以及原因是什么。
Novell 服务器由第三方托管，因此我们无法向您提供其 IP，更不用说用户/密码了。
我们正在 636 端口上进行连接。 在LDAP浏览器的跟踪中，我们看到它进入了“初始化SSL...”步骤，但随后无法连接。
We have tried to connect to a remote Novell server from our offices.
First, we had to open the firewall port to connect to the server, otherwise we were getting error 91 (which basically tells that the server cannot be joined).
Second, we used a tool called LDAP Browser to test the connection.
We get the error 81 "can't contact LDAP server". But we looked at the traces of communications and we see that we contact the server and gets a response. We also tested with Telnet and we see that we can connect to the server.
So, is anybody know what this error means and what are the possible solutions? Because, I googled that error and got no valid answer telling what to check and what is the cause.
The Novell server is hosted by a third party, so we cannot provide you its IP, even less the user/password.
We are connecting on the 636 port. In the trace of LDAP browser, we see that its getting to the step of "Initializing SSL..." but then fails to connect.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为两个问题：
1）你想要做什么类型的绑定？ SSL？ 清晰的文字？ 匿名的？
2) 如何在 eDirectory 端配置 LDAP 绑定？
LDAP 浏览器工具，您指的是此链接中的工具吗？
免费 LDAP 浏览器
在 eDirectory 端，他们可以要求所有 LDAP 通信都使用 TLS ，并且他们可以禁止匿名绑定。
您能否要求另一端的人员启用 LDAP 跟踪（在启用 +LDAP 选项的情况下使用 DStrace，有关如何在 Novell eDirectory 上使用 Dstrace 的一些链接请参见：不同类型的 Dstrace 捕获并了解 Identity Manager 的 DS 跟踪。）
这通常会显示一条错误消息来启发您。
我的猜测是要么启用了 Require TLS，并且您可能没有成功进行 SSL 绑定。
如果是这样，请尝试在端口 636 上进行连接，启用 SSL，并为您尝试登录的用户提供完全限定的 DN。
如果您尝试启用 SSL，并且没有收到有关接受树 CA 的受信任根证书的弹出框，则 eDirectory 服务器用户所用的 CA 或 SSL 证书可能已过期或已损坏。 （造成这种情况的常见原因有很多，只需片刻即可修复）。
通常，如果出现问题，Dstrace 中您会看到有关 SSL 证书的错误。 本文中提供了从 Novell Identity Manager 角度来看过期证书的示例： 证书过期以及有关如何修复证书的一些详细信息。
下一种可能是您指定的 DN 不太正确。
从错误 81 的角度来看，这里有几个链接，介绍 AD 如何显示 81 错误情况，以了解可能性（主要与 SSL 相关）。 通过 IDM 驱动程序的 AD SSL
如果您需要进一步帮助，请告诉我。
Two issues I think:
1) What kind of bind are you trying to do? SSL? Clear text? Anonymous?
2) How is it configured on the eDirectory side for LDAP binds?
The tool LDAP Browser, are you referring to the one at this link?
Free LDAP Browser
On the eDirectory side, they can require TLS for all LDAP communication, and they can disallow Anonymous binds.
Can you ask the folks at the other end to enable LDAP tracing (Using DStrace with the +LDAP option enabled, some links for how to use Dstrace on Novell eDirectory look at: Different types of Dstrace Capturing and understand DS Trace for Identity Manager.)
That usually will show an error message that will enlighten you.
My guess is either Require TLS is enabled, and you might not be doing a successful SSL bind.
If so, try to connect on port 636, with SSL enabled, and a fully qualified DN for the user you are trying to login as.
If you are trying with SSL enabled, and you are not getting a pop up box about accepting the tree CA's trusted root certficate, then perhaps the CA or the SSL certificate taht the eDirectory server is user has expired or is broken. (There are any number of causes for this that can be common, and take but a moment to fix).
Usually in Dstrace you will see an error about the SSL certificate if there is a problem. An example from a Novell Identity Manager perspective of an expired certificate is in this article: Certificate Expired As well as some details on how to fix the certificates.
Next possibility is that the DN you are specifying is not quite correct.
From an error 81 perspective, here are a couple of links for how AD would show the 81 error case, to get a feel for possibilities (mostly SSL related). AD SSL via IDM driver
Let me know if you need further help.