>>One of my clients is attempting to deploy a Win2K server with about 15 users. Got everything set up and tried to switch everything over today. Everything seemed to be going fine at first, but the more people logged on, the slower things got, to the point where Windows (workstations are all NT4) appeared to freeze.
>>
>>VFP applications pointing to data on the Win2K box would get "Error reading file" and "Error writing to file" errors intermittently. Click Ok, and you might get another one, or it might "heal" itself. Its as if all of the network connections are being dropped and reconnected spontaneously.
>>
>>Any idea what could be causing this? It seems to get worse as more users get on the system (it becomes unusable at around 7 users, depending on their activity).
>
>Did you ever fix this?

Not yet. We're working with MS.

>You're blazing trails with Win2K Server - we're in early testing here. But a few ideas, assuming your hardware is industrial-strength enough to handle Win2K:
>
>What else is running? There are many apps (server and otherwise) not fully compatible with Win2K. The first thing I'd look at is an AV service, we've had problems that resemble yours with those in previous NT Server/McAfee editions. Currently, I have to keep McAfee disabled on my servers or NT4 will kick users off when it gets busy, for example...

Nothing funky yet, just plain old VFP apps.

It's as if the concurrent user limit for the server has been reached, and it is dropping users as it needs to. But this is not the case.