>Tony, thanks for your reply
>
>It seems that this is a fairly 'common' problem that there must be some common reason for it. I wonder if there are any Knowledge base articles about this.
>The particular site that it is happening happens to be a Thin ethernet, but as I said in the first question, THERE IS ANOTHER FPW APPLICATION RUNNING on a number of pc's on the network and they are not having any trouble.
>
>The only difference (I think) is that these users happen to be on Win 95 . The problem users are on Win 98 on fairly new pc's)
>
>regards,
>
>Gerard
>

You might want to check out what the NICs used in the '98 PCs are. Swapped out a few of these and most of the problems went away. It's probably more of a driver related problem. When we switched NIC's, we also switched brands from 3Com to Intel, I think it was.



>
>
>
>>David
>>
>>Thanks for willing to testify. But sometimes.., I still can not get rid of this "Error reading file", even I already use a good NIC, Ethernet Switch, and good quality UTP Cable (measured with a proper instrument). I think I will try to replace the NT Server with Netware Server just for the VFP Application and Data.
>>
>>See you
>>Tony
>>
>>
>>>Tony and Gerard,
>>>
>>>>...I usually get rid of this problem by providing a better network approaches, such as using Ethernet Switch HUB instead of using Ethernet HUB, using better NIC, using Fiber Optics Cable and alot of prays.
>>>
>>>I can testify that a similar approach solved major network "unavailability" problems for me on an NT network recently.
>>>