Just an update to this issue in the event that it might help someone in the future. I have been able to resolve both of my problem situations.

In the Win2K/Win2K Server case, the customer originally told me that they had write-caching disabled on the client. In fact, they did *not* and after this was done, the problem went away.

In the NT/NT Server case, the resolution was to install the software to another server. The system started behaving normally following the change. This leads me to believe that the problem was caused by a network component like a cable, hub, or switch between the client and the first server although that wasn't necessarily proven to be the case. MSKB article #145952 indicates this could be the cause. I suppose it could have been a setting on the server itself, but the errors were never being logged in the Event Log there.

Thanks,
Scott