Hi Jim,

Way ahead of you ;-)
That was one of the first things we checked.
We disabled all sleep modes, on the nerwork-card aswell as on the entire pc.
Also, it's not due to inactivity, it just occurs after xx hours of connection (or at a certain hour, that's difficult to determine)

>Something else to check out...
>
>Most newer network adapters have a "sleep" mode, ostensibly for power-saving reasons. All that I have seen like this have this feature turned ON.
>I know that this can lead to the error message you report here.
>
>In a VFP environment leaving this set ON is poison.
>
>The setting can be changed through the Control Panel --> System --> Device Manager, then check/change the power saving feature of the network adapters.
>
>good luck
>
>
>>Hi Neil,
>>
>>Well, some of them are using network, others are using citrix or Terminal Server.
>>The viruscheckers have been 'checked', no scheduled scans.
>>The event-logs state nothing specific.
>>One of our customers mentioned that she has the impression it occurs after exactly being logged in our app for 10 hours straight on.
>>Other customers report about the same hour when this happens (early evening), but maybe this also is due to being active for xx time in our app.
>>
>>
>>
>>>Hi,
>>>Do the workstations have a scheduled virus scan which causes the problem. What do the server & the workstation event logs show.
>>>Check for scheduled tasks in the event scheduler, maybe someone is downloading something after hours, see what processes are running on each of the workstations.
>>>Also if these workstations are on a separate network segment what is the bandwidth utilization which is causing a network timeout.
>>>
>>>>Hi,
>>>>
>>>>Some of our customers are experiencing something quite strange.
>>>>They are using our app (local exe's) which uses databases on a central server 2003.
>>>>
>>>>Starting from a certain hour in the early evening (some 18u, others a bit later) they start getting Error reading file-errors.
>>>>
>>>>We already checked if there's any backup-program starting or something else, but no, not a thing.
>>>>
>>>>Does anyone have an idea what could be causing this? Maybe some obscure setting in Server 2003 ?
>>>>
>>>>Thanks for any hints.
>>>>
>>>>Guillaume