5 replies
by bill
I have experienced the problem you described on a number of occasions. The best I've been able to determine is that, at times of high network activity, the response delay from the server is sufficient to trigger 'path not accessible' or 'access denied' type error messages. In most cases, if I waited a couple minutes, and retried access to the location in question everything was fine.
There are some network 'timeout' settings that can be 'tweaked' to avoid these messages, but, in my experience, often the user gives up and reboots thinking that their PC was 'hung' while waiting for the server to respond.
Also, you might want to try adding some memory to your servers if they're running with less than 1Gb. We found that maxing out theRAM at 1Gb virtually eliminated the 'unexplained' problems we'd been experiencing. Seems 2000 especially likes large amounts of available RAM, even more so than NT did.
-Bill
by staci
by umbral-echo
Microsoft has posted knowledge base articles that seem to address the problem you are describing. They have hotfixes linked in the article.
The articles are Q278558 and Q278456.
You did not specify client types but if they are Windows 98 they are definitely vulnerable to these problems.
by staci
by staci
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending