Hi Rich,

Could be, but when they quit our app, and log in again, it works.
So, if this would be an 'after hour' or 'Logon hours' issue, they probably would not be able to immediately log in our app again.
We'll look into the DHCP settings aswell, but as you know, these are tedious things to try.

Thanks


>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 ?
>
>This could be due to SECURITY OPTIONS settings on the local workstation.
>
>Go to START then RUN, type the following command: "secpol.msc"
>
>Then go to LOCAL POLICIES, then SECURITY OPTIONS, then to MICROSOFT NETWORK SERVER: AMOUNT OF IDLE TIME REQUIRED BEFORE SUSPENDING SESSION and set it to ZERO. The default for this setting is 15 minutes. This is probably not the culprit in your situation but always good to check.
>
>Another one to check is if a user has a LOGON HOURS settings in their account that can also cause a disconnect. There is a setting for this as well in the SECURITY OPTIONS: MICROSOFT NETWORK SERVER: DISCONNECT CLIENTS WHEN LOGON HOURS EXPIRE. This is enabled by default and should be set to DISABLED.
>
>Hopefully that helps solve your problem.