A. This problem may be due to the machines having a non-zero PagedPoolSize in the registry. This can be set by performing the following:

  1. Log onto the server as an Administrator
  2. Start the registry editor (regedit.exe)
  3. Move to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
  4. Double click on PagedPoolSize and set to 0
  5. Click OK
  6. Close the registry editor
  7. Reboot the machine

If PagedPoolSize is 0 then it allows NT to dynamically allocate memory, the installation of software such as ARCServe is known to cause this problem.

This can also be caused when accessing a Windows NT Server share from a Windows NT client if IRPstackSize is too small. To correct try the following:

  1. Log onto the server as Administrator
  2. Start the registry editor (regedit.exe)
  3. Move to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
  4. Double click on IRPstackSize
  5. Increase the value. Valid ranges are between 1 and 12. Click OK
  6. Reboot the machine.

You may find once setting this, other connections, such as those to NetWare volumes, gain a performance boost.

Another cause for this error is if you installed Service Pack 3 onwards before installing any network components. If this is the case then re-apply Service Pack 3 and any subsequent hotfixes. It is good practise to reapply a service pack whenever you modify/add components to the system.