Hello,
We have a small network of about 25 users running windows 98 SE with a server running windows NT 4 (sp 6). The server stores many office 97 (sp2b) files that the clients must be able to reach.
Periodically, word and excel documents will take a very long time to load. Often when this happens word will show an error indicating there was possible corruption with the file. Using Performance Monitor, the server vital signs (Memory PAges/sec, available bytes, %Disk time, %Processor time, etc) appear normal.
When this happens I have tried to open the same file reported by word as corrupted using OpenOffice 1.0. The file opens quickly and does not appear to have any corruption.
Eventually the problem goes away all on its own, all files then work correctly with Office97.
Is this a network traffic problem, or a disk corruption problem? Or is this just an issue with Office97? Is there a program I can use to monitor traffic on my network?
I can't seem to pin down the problem, especially since it is an erratic occurance (Roughly every month, we experience this for a couple of days).
Thanks,
Matt Kubilus
Sofix Corporation
We have a small network of about 25 users running windows 98 SE with a server running windows NT 4 (sp 6). The server stores many office 97 (sp2b) files that the clients must be able to reach.
Periodically, word and excel documents will take a very long time to load. Often when this happens word will show an error indicating there was possible corruption with the file. Using Performance Monitor, the server vital signs (Memory PAges/sec, available bytes, %Disk time, %Processor time, etc) appear normal.
When this happens I have tried to open the same file reported by word as corrupted using OpenOffice 1.0. The file opens quickly and does not appear to have any corruption.
Eventually the problem goes away all on its own, all files then work correctly with Office97.
Is this a network traffic problem, or a disk corruption problem? Or is this just an issue with Office97? Is there a program I can use to monitor traffic on my network?
I can't seem to pin down the problem, especially since it is an erratic occurance (Roughly every month, we experience this for a couple of days).
Thanks,
Matt Kubilus
Sofix Corporation