“磁盘或网络错误” [英] "Disk or network error"
问题描述
我对这个错误信息并不陌生，但我有一个客户是否经历过它，但是，幸运的是，没有任何实际数据
腐败，它正在驱使他们制造。他们无法掌握
，原因基本上是一个网络问题也在制造
我把头发拉出来。
一些历史：
网络由五台可追溯到1995年的计算机组成，每台计算机一次购买一台，每台计算机都有不同的操作系统等。在最近购买IBM笔记本电脑之前，网络是稳定的，只有两台机器，一台Win2K台式机（这是点对点文件）/
>
服务器）和一个Win98桌面（主工作站）。
在此之前，Win98桌面一直是文件服务器，并且
另一个工作站是Win95盒子。这个设置运行得很好。
在那段时间里购买了一台Win98笔记本电脑，但它几乎没有使用过
，所以我不能说是否或者没有任何问题
连接到网络。
当我们拿到Win2K盒子时，我像往常一样设置它，使用TCP / IP
网络，Win98工作站无法连接到
，但速度非常慢到Win2K盒子。我最终
在两个盒子上都安装了NETBEUI，然后事情很快就完成了（不要...... b $ b让任何人告诉你NETBEUI是一个糟糕的网络协议！）。
最近，购买了一台新的IBM T42用作老板的主要工作站，并且Win2K盒已经退役用作
原理工作站。所以，新的配置是：
WinXP笔记本电脑 - > Win2K P2P服务器
上一个是：
Win98桌面 - > Win2K P2P服务器（TCP / IP + NETBEUI）
前一个是：
Win95桌面 - > Win98 P2P服务器（无NETBEUI）
此外，在目前的情况下，还有：
WinXP笔记本电脑 - > Win2K P2P服务器
Win98笔记本电脑也已复活。
当我设置新的WinXP笔记本电脑时，我从
一切。但在那之后，两台笔记本电脑（WinXP和Win98）都出现了网络连接间歇性问题 -
事情开始很好但几分钟后（5-20） ），磁盘或
网络错误弹出。如果用户然后尝试通过其他方法（我的网络位置等）访问网络
资源，他们可能
或者可能无法通过（大约2 / 3s）当时，它成功，但
剩余时间，它也失败了。）
但是在这些情况下都没有数据文件已损坏
（所有工作站的前端，数据文件仅在P2P
服务器上）。
此外，何时*正在*工作在WinXP上，网络是*慢*，
类似于Win98工作站失败的方式
连接到Win2K P2P服务器。由于旧的情况似乎已经通过安装NETBEUI来解决，我们尝试使用
当前批量的机器，但它没有解决问题（注意
由于旧的网络问题，我们没有得到磁盘或
网络错误，只是性能不佳）。
我们已经更换了所有接线。我们换了枢纽。我们目前正在下载所有新的网络驱动程序，并期待关闭所有对MDB进行AV扫描的
。
可能导致磁盘或网络错误的任何其他想法
没有腐败，没有任何其他申请的投诉？
-
David W. Fenton http://www.bway.net/~dfenton
dfenton在bway dot net http://www.bway.net/~dfassoc
我没有提到一件至关重要的事情：这是一个完全的Access 97
设置，所以我不是认为OpLocks可能与它有任何关系，
因为这只是开始只是Access 2K的问题，
对吧？
-
David W. Fenton http ：//www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
2005年4月1日星期五20:33:38 GMT， David W. Fenton
< dX ******** @ bway.net.invalid>写道：
我认为，而不是软件，你需要考虑失败
硬件。也许是一个NIC，一个集线器（端口）或一个电缆。
-Tom。
我失败了一件至关重要的事情提到：这是一个完全的Access 97
设置，所以我不认为OpLocks可以与它有任何关系，
因为这只是开始只是Access 2K的问题，
对吗？
Tom van Stiphout< no ************* @ cox.net>写在
新闻：dr ******************************** @ 4ax.com：
2005年4月1日星期五20:33:38 GMT，David W. Fenton
< dX ******** @ bway。 net.invalid>写道：
我没有提到一件至关重要的事情：这是一个完全的Access
97设置，所以我不喜欢我认为OpLocks可能与它有任何关系，因为只有使用
Access 2K才开始出现这个问题，对吧？
我认为你需要考虑硬件失败，而不是软件。也许是一个NIC，一个集线器（端口）或一个电缆。
嗯，唯一改变的硬件是增加一个新的
笔记本电脑，它表现出与笔记本电脑相同的症状，即4年b
岁，所以这往往会让我觉得问题是
不是硬件。
我也没有任何关于NIC随着时间的推移变坏的经验 -
他们要么坏了要么他们不是。
如果问题机器是台式机，我们马上就换掉了
网卡，但它们是不可交换的（我认为两者都在板载
笔记本电脑主板上。
IBM对讨论网卡故障排除不感兴趣。
戴尔笔记本电脑长期不在保修期内。
我也非常偏见硬件故障导致这些错误，因为我有这些错误从来没有这个
类专业的单一实例没有*基于软件的瑕疵。当然，这可能是它的硬件时间。
所有的电缆都已经被新的替换了（我告诉
他们要切换所有电缆，但是它们不是太亮了，并且除了每个网络中涉及的电缆外，所有电缆都切换了
交易，从集线器到P2P服务器）。
我对于确定一个失败的网卡感到绝望，因为
情况（我可以不容易到达客户端，他们的网卡不能兑换掉b $ b。我相信有一个集线器（它可能是一个
自动感应开关，在这个
大小的网络上没有任何用途，但老板的丈夫除了具有4个端口的Linksys
有线/ DSL路由器之外，其中之一是b $ b知道 - 足够危险的类型。不过，我不知道什么是插入
。 Linksys盒子是新的，集线器/开关，我不知道。
我怀疑它不是*硬件的另一个原因是完全没有
腐败。这不是任何一种特别设计的应用程序，它具有
仔细的连接管理 - 它基于我曾经创建的第一个主要的
访问应用程序客户。这意味着设计是b
HIDEOUS。 :)它使用绑定到整个表的表单（虽然它是，至少
，记录源中的一个SQL字符串）。如果失去网络连接，我认为它会非常容易腐败，但
似乎没有。
这让我怀疑是非硬件问题。
-
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net < a rel =nofollowhref =http://www.bway.net/~dfassoctarget =_ blank> http://www.bway.net/~dfassoc
I''m no stranger to this error message, but I have a client who is
experiencing it, but, fortunately, without any actual data
corruption, and it''s driving them made. Their inability to grasp
that the cause is fundamentally a networking problem is also making
me pull my hair out.
Some history:
The network is composed of five computers dating back to 1995, each
purchased one at a time, and each having a different OS, etc. Until
the recent purchase of an IBM laptop, the network was stable with
only two machines, a Win2K desktop (which was the peer-to-peer file
server) and a Win98 desktop (the primary workstation).
Previous to that, the Win98 desktop had been the file server, and
the other workstation was a Win95 box. That setup worked just fine.
During that time a Win98 laptop was purchased, but it was hardly
ever used, so I can''t say whether or not it had any problems
connecting to the network.
When we got the Win2K box, I set it up as I always do, using TCP/IP
networking, and the Win98 workstation had trouble connecting at
anything but really slow speeds to the Win2K box. I eventually
installed NETBEUI on both boxes and then things worked fast (don''t
let anyone tell you that NETBEUI is a bad networking protocol!).
Recently, a new IBM T42 was purchased to be used as primary
workstation for the boss, and the Win2K box was retired for use as
principle workstation. So, the new configuration was:
WinXP laptop --> Win2K P2P server
Previous was:
Win98 desktop --> Win2K P2P server (TCP/IP + NETBEUI)
Previous to that was:
Win95 desktop --> Win98 P2P server (no NETBEUI)
Also, in the current situation, with:
WinXP laptop --> Win2K P2P server
the Win98 laptop has also been revived.
When I set up the new WinXP laptop, I removed NETBEUI from
everything. But after that, both laptops (WinXP and Win98) have been
experiencing intermittent problems with network connectivity --
things start out great but after a few minutes (5-20), "disk or
network error" pops up. If the user then tries to access network
resources by some other method (My Network Places, etc.), they may
or may not get through (about 2/3s of the time, it succeeds, but the
remainder of times, it, too fails).
But in none of these cases has the data file ever been corrupted
(front ends on all the workstations, data file only on the P2P
server).
Also, when things *are* working on WinXP, the network is *slow*,
similar to the way things were failing with the Win98 workstation
connecting to the Win2K P2P server. Since the old situation seemed
to have been worked around by installing NETBEUI, we tried that with
the current batch of machines, but it didn''t solve the problem (note
that with the old network problems, we weren''t getting "disk or
network error," just poor performance).
We''ve replaced all the wiring. We''ve swapped hubs. We''re currently
downloading all new network drivers, and looking into turning off
all AV scanning of MDBs.
Any other ideas what might be causing "disk or network error" with
no corruption, and no complaints from any other applications?
--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
One crucial thing I failed to mention: this is an entirely Access 97
setup, so I don''t think OpLocks could have anything to do with it,
as that''s something that started being an issue only with Access 2K,
right?
--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
On Fri, 01 Apr 2005 20:33:38 GMT, "David W. Fenton"
<dX********@bway.net.invalid> wrote:
I think that rather than software, you need to think about failing
hardware. Perhaps a NIC, a hub (port), or a cable.
-Tom.
One crucial thing I failed to mention: this is an entirely Access 97
setup, so I don''t think OpLocks could have anything to do with it,
as that''s something that started being an issue only with Access 2K,
right?
Tom van Stiphout <no*************@cox.net> wrote in
news:dr********************************@4ax.com:
On Fri, 01 Apr 2005 20:33:38 GMT, "David W. Fenton"
<dX********@bway.net.invalid> wrote:
One crucial thing I failed to mention: this is an entirely Access
97 setup, so I don''t think OpLocks could have anything to do with
it, as that''s something that started being an issue only with
Access 2K, right?
I think that rather than software, you need to think about failing
hardware. Perhaps a NIC, a hub (port), or a cable.
Well, the only hardware that has changed is the addition of a new
laptop, and it''s exhibiting the same symptoms as a laptop that is 4
years old, so that would tend to make me think that the problem was
not hardware.
I also don''t have any experience with NICs going bad over time --
they are either bad or they aren''t.
If the problem machines were desktops, we''d have swapped out the
NICs right off, but they aren''t swappable (I think both are onboard
the laptop motherboards).
IBM is not interested in discussing NIC troubleshooting.
The Dell laptop is long out of warranty.
I''m also quite prejudiced against hardware failure as a cause of
these kinds of errors, as I have never had a single instance of this
kind of problem that was *not* software-based. Of course, this could
be the time it''s hardware.
All but one of the cables has already been replaced with new (I told
them to switch all cables, but they aren''t too bright, and switched
all of them except the one that was involved in every network
transaction, the one from the hub to the P2P server).
I despair over trying to identify a failing NIC given the
circumstances (I can''t get to the client easily, and they NICs can''t
be swapped out). I do believe there is a hub (it may be an
auto-sensing switch, which serves no purpose on a network of this
size, but the husband of the boss is one of those
knows-just-enough-to-be-dangerous types) in addition to a Linksys
cable/DSL router with 4 ports. I don''t know what''s plugged into
what, though. The Linksys box is new, the hub/switch, I don''t know.
Another reason I suspect it''s *not* hardware is the complete lack of
corruption. This isn''t any kind of specially-designed app with
careful connection management -- it''s based on the first major
Access app I ever created for a client. That means the design is
HIDEOUS. :) And it uses forms bound to entire tables (though it is,
at least, a SQL string in the recordsource). I would think it would
be very prone to corruption if it lost the network connection, but
it doesn''t seem to be.
That makes me suspect a non-hardware issue.
--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
这篇关于“磁盘或网络错误”的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
