网络看似已关闭，但实际并未关闭
客户正在通过 LAN 使用我们的应用程序。
VB6 前端通过 DAO 访问 Jet 数据库。
数据库连接在此期间保持打开状态。 他们会收到一些错误，就像网络没有关闭一样。
如果我能解释一下： 有时，当存在不可靠的网络连接时，查询将失败，并给出类似“无法找到表 A”的错误。一旦网络再次恢复，该实例将再次恢复正常工作。
然而，在这种情况下，会发生的情况是，一个实例将以上述方式停机，但如果启动一个新实例，它将正常运行（直到经过一段随机时间后，它也会挂起），同时前一个实例将继续返回暗示的错误消息网络瘫痪并且永远无法恢复正常工作。
有谁知道这可能是什么？
*更新2011年2月8日问题已解决*
导致此问题的原因是存储数据库的计算机具有静态IP，而其余计算机具有动态IP。静态IP 地址落在选择动态IP 地址的范围内。 最终生成了与静态地址相同的动态地址，并导致了上述问题。 感谢大家的评论
A client is using our app over a LAN.
A VB6 front end accesses a Jet database via DAO.
The database connection is is kept open for the duration.
They are getting errors like as though the network is down when it isn't.
If I can explain:
Sometimes when there's a dodgy network connection a query will fail giving an error along the lines of "unable to find table A". As soon as the network is up again this instance will resume working properly again.
In this case however what happens is that an instance will go down in the manner described above but if a new instance is started it will behave properly (until after a random period it too hangs) meanwhile the previous instance will keep returning error messages suggestive of a network being down and never resume working properly.
Does anyone have an idea what this could be?
*UPDATE 08 Feb2011 The problem has been resolved *
The cause of this problem was the the computer storing the database had a static IP while the rest had dynamic IPs. The static IP address fell within the range from which the dynaic ones were selected.
Eventually a dynamic address was generated identical with the static one and caused the issues described above.
Thanks to everyone for their comments
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论